In article <(E-Mail Removed)>,
(E-Mail Removed)
says...
>
> I am having the exact same problem. It all started because we didn't
> update the .crls once they expired. We have since renewed the .crls but
> we got the same errors. Had to do the log level switch from 3 to 2 to
> get CA services working but now I get these errors when trying to issue
> certs:
>
> The revocation function was unable to check revocation because the
> revocation server was offline. 0x80092013 (-2146885613).
>
>
> The disposition message is "Error Constructing or Publishing
> Certificate The certificate validity period will be shorter than the
> WebServer Certificate Template specifies, because the template validity
> period is longer than the maximum certificate validity period allowed by
> the CA. Consider renewing the CA certificate, reducing the template
> validity period, or increasing the registry validity period.
> Resubmitted by ENT\gcfgill".
>
> Any luck with your issues? What have you done to correct it?
>
>
>
> --
> Cooquist
> ------------------------------------------------------------------------
> Posted via http://www.mcse.ms
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message1701285.html
>
>
It sounds like you have issues with the CA certificate's remaining
validity period, and this could be an issue for the entire chain.
Certificate Services will not allow a CA to issue a certificate with a
validity period greater than the remainin validity period of the CA that
issues the certificate (remember the VeriSign issue about a year ago
<G>)
It sounds like you have several problems:
- The URLs for either the AIA or CDP extensions in the certificates are
invalid. This could be for any or all of the CAs in the CA hierarchy
For this problem, use the PKI Health Tool (pkiview.msc) from the Server
2003 resource kit. It will analyze all AIA and CDP extensions in the
certificate chain and report any errors. Every error should be
addressed.
- The validity period of the CAs may need to be revised.
For each CA in the CA path, you must alter the registry of the isssuing
CA to allow the duration that you wish for the subordinate CA
certificate (especially if using standalone CAs). This is done through
two registry settings: ValidityPeriod and ValidityPeriodUnits. For
example, if you want to issue a subordinate CA certificate with a
validity period of 10 years (assuming that the parent CA has a validity
period greater than 10 years remaining), use:
certutil -setreg CA\ValidityPeriodUnits 10
certutil -setreg CA\ValidityPeriod "Years"
HTH,
Brian
==
Brian Komar
MVP - Windows - Security
http://www.identit.ca/blogs/brian