Re: Certificate server

Fixed it! I had to call in a favor for help on this one. It turns out
that the machine had too little memory. IIS will not take requests if
there isn't enough memory available. This machine only had 128 MB of
ram. I want to stress that this was a working CA as of one month ago. I
assume we were right on the thresh hold of enough memory before, but
this time it was exceeded. Increased the memory to 256 and
presto...problem solved.

JEFF
Jeff wrote:
Brian wrote:
In article <1161181631.998222.67070@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Ziembic@xxxxxxxxx says...
Yes, I have installed the necessary compnents. This was a working
implementation, I have issued numerous certs from this instance via the
web utility, I just don't know why it stopped working. I even ran the
certutil that you reccomeneded to be safe, but I still get the same
error. Thanks for your help so far.


Are you able to request certificates using certreq? What are you getting
if you run certutil -ping or certutil -pingadmin?
Brian

I am getting a reply if I do the ping or pingadmin from the certificate
machine directly. I am not getting any response if I do it from any
other machine, some with existing valid certs and new machines that I
am trying to get a cert for. I can successfully request a cert from
within the IIS manager, but when I create a request from virtual
server, and then try and go to the web site, the web site does not come
up: page cannot be found. I am unfamiliar with using certreq, can you
elaborate?

JEFF

.

Relevant Pages

  • Re: how to kill EXCEL component in taskManager which is in memory
    ... for 1st example whose heading is 'Make Excel Do the Work', ... granting access rights to the resource to the ASP.NET request identity. ... Network Service on IIS 6) that is used if the application is not ... >> memory has been taken by excel objects and memory is being full. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET application hits 2GB virtual bytes
    ... We found the problem last night, we essentially had a resource/memory leak. ... the Reflection call failed but the watcher thread ... The 3GB switch limits the *virtual address space*, not the working memory set. ... your basic problem is that you're running in IIS 5.0 compatibility mode. ...
    (microsoft.public.dotnet.framework.aspnet)
  • [PATCH 0/3] ia64: Migrate data off physical pages with correctable errors v3
    ... Migrate data off physical pages with corrected memory errors ... (per Christoph Lameter's request). ... Updated for recent page flag clean-up. ... handler to the page migration code. ...
    (Linux-Kernel)
  • [PATCH 0/3] ia64: Migrate data off physical pages with correctable errors v5
    ... Migrate data off physical pages with corrected memory errors ... (per Linus Torvalds's request). ... Removed locking when calling the migration code ... If the page fails to migrate, clear the PG_memerror flag. ...
    (Linux-Kernel)
  • Re: ASP.NET application hits 2GB virtual bytes
    ... The server it is being tested on has 4GB of RAM, with the 3GB switch on boot. ... The 3GB switch limits the *virtual address space*, not the working memory set. ... your basic problem is that you're running in IIS 5.0 compatibility mode. ...
    (microsoft.public.dotnet.framework.aspnet)