Windows 2003 CA 0x80092013

From: Mlynka Richard (Richard_at_discussions.microsoft.com)
Date: 06/28/05


Date: Tue, 28 Jun 2005 01:25:02 -0700

Hi,

we have SubCA on Windows 2003. This CA is unable to start because of this
error. After modifzing CA\LogLevel to 2, it is able to start, but certs are
not issued because of this error. I tested with certutil validity of RootCA
CRL, it passes. CRL of RootCA is V1 - can this be a problem. What can I do?
Thanks

Best regards,
RM



Relevant Pages

  • Re: MS CA service and publish CRL and AIA
    ... To have the windows 2000 CA automatically publish CRLs to another location, ... >>servers) as a CDP and AIA extension and check the box> for publishing the CRL ... >>checking the boxes to include the link in issued> certificate and CRL's). ...
    (microsoft.public.win2000.security)
  • CRL caching and smart card logon
    ... Windows 2003 servers, Windows XP workstations and Windows 2003 CA (for ... when CRL is not available? ... But if CRL server is down, or no domain controller is available (cached ...
    (microsoft.public.security)
  • CRL caching and smart card logon
    ... Windows 2003 servers, Windows XP workstations and Windows 2003 CA (for ... when CRL is not available? ... But if CRL server is down, or no domain controller is available (cached ...
    (microsoft.public.win2000.security)
  • Re: Root certificate authority no longer added to client machines
    ... All servers and DCs are Windows 2003 SP1. ... certutil -dspublish -f c:\rootca.crt RootCA ... We have a standalone RootCA, ... "When you install an enterprise root CA or a stand-alone root CA, ...
    (microsoft.public.security)
  • Re: Cant Get Smart Card-Based Windows Logon to Work! Need Help!
    ... You don't have all pieces in place: you do need to provide access to the CDP ... There is however a hotfix that allows to extend validity of the cached CRL: ... > For several weeks now I've been trying to get Windows Smart Card Logon to ... > see if it was attempting to connect to the revocation server and indeed it ...
    (microsoft.public.security)