Publishing a certificate revocation list (CRL) fails with error message "The directory name is invalid. 0x8007010b (WIN32/HTTP: 267 ERROR_DIRECTORY)".

Assume the following scenario:

  • A new revocation list is created on the certification authority.
  • Publishing fails with the following error message:
The directory name is invalid. 0x8007010b (WIN32/HTTP: 267 ERROR_DIRECTORY)

Sometimes it is necessary for a certificate issued by a certification authority to be withdrawn from circulation even before its expiration date. To make this possible, a certification authority keeps a revocation list. This is a signed file with a relatively short expiration date, which is used in combination with the certificate to check its validity.

Further details can be found in the event display. The certification authority will, depending on the revocation list type, display the events 65, 66, 74 or 75 log.

Basically, various causes come into question:

  • The configured directory is not shared.
  • The configured path is not correct.

In this case, the directory was not configured correctly. To find out which directories are configured, see the Extensions tab in the Certificate Services Management Console (certsrv.msc). The option "Publish to this location" determines whether a revocation list should be published to this directory.

It is not possible to edit the entry directly in the certification authority management console. It can only be deleted and recreated. However, you can edit the configuration in the registration of the certification authority service. The setting can be found under HKLM:\CurrentControlSet\Services\CertSvc\Configuration\{name-of-certification authority}\ in the value "CRLPublicationURLs".

After changing the configuration, the certification authority service must be restarted for the changes to take effect.

Related links:

2 thoughts on “Die Veröffentlichung einer Zertifikatsperrliste (CRL) schlägt fehl mit Fehlermeldung „The directory name is invalid. 0x8007010b (WIN32/HTTP: 267 ERROR_DIRECTORY)“”

Comments are closed.

en_USEnglish