SSL Certificates Enrollment

  • Thread starter Thread starter Mark Campbell
  • Start date Start date
M

Mark Campbell

Hi.

I am experimenting with SSL certificates for signing e-
mails on our domain (SBS2k Machine). SSL for OWA works
fine however, when I try to get a certificate through
http://<ip_address>/certsrv, I get the following error...

Failed to create 'CertificateAuthority.Request' object.

The machine is fully patched and the IIS Lockdown has been
run configured accordingly.

Any Clues?

Mark

FYI, I have enabled another SBS machine in a similar
config and this works fine.
 
Mark Campbell said:
Hi.

I am experimenting with SSL certificates for signing e-
mails on our domain (SBS2k Machine). SSL for OWA works
fine however, when I try to get a certificate through
http://<ip_address>/certsrv, I get the following error...

Failed to create 'CertificateAuthority.Request' object.

The machine is fully patched and the IIS Lockdown has been
run configured accordingly.

Any Clues?

Mark

FYI, I have enabled another SBS machine in a similar
config and this works fine.
Click to expand...

Are both SBSW2K up to the same service pack? Can you check if the Session
State for the virtual site is enabled?

IIS, right-click site for properties, Configuration, and then click the
Options tab.
Enable the Session State check box
Restart Web
 
-----Original Message-----



Are both SBSW2K up to the same service pack? Can you check if the Session
State for the virtual site is enabled?

IIS, right-click site for properties, Configuration, and then click the
Options tab.
Enable the Session State check box
Restart Web




.
Both Machines are at the same Service Pack and Both are
Click to expand...
Fully Patched.

This being said, the System State was not Checked on the
one that was not working so I set it to the same config
however, I got he same error after the restart.

Thanks for your response.
 
Fully Patched.

This being said, the System State was not Checked on the
one that was not working so I set it to the same config
however, I got he same error after the restart.

Thanks for your response.
Click to expand...

My pleasure, have a few clients which rely on CAs too.

I'm still insisting that the problem is session state related. There is a
short script found in the following URL named SessionState.aspx that can
help in testing the session state.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspnet/ht
ml/asp12282000.asp

Check that no asp page disables the session state: <%@
EnableSessionState=False %>

finally verify this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\W3SVC\ASP\Parameters\AllowSessionState
 
-----Original Message-----


My pleasure, have a few clients which rely on CAs too.

I'm still insisting that the problem is session state related. There is a
short script found in the following URL named SessionState.aspx that can
help in testing the session state.
http://msdn.microsoft.com/library/default.asp? url=/library/en-us/dnaspnet/ht
ml/asp12282000.asp

Check that no asp page disables the session state: <%@
EnableSessionState=False %>

finally verify this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\W3SVC\ASP\Parameters\AllowSessionState





.
Got it!!
Click to expand...

Many Thanks - It was indeed the Session State that was not
working correctly.

Many thanks,

Mark
 
Back
Top