Discussion Locked

Certificate Bindings

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We run IIS4 on NT Server 4 SP5-128. Recently when binding PKI certificates to individual sites, I experienced an odd phenomenon I hope someone can shed some light on. After binding the individual certificates to the sites (4 of them sequentially)I Committed the Changes, and saved the MMC 1.1 console file to disk. At that point the bindings dialogue accurately reflected the individual certificate-socket bindings. 10 minutes later, I had to revisit the MMC. When I opened the Key Manager module All the certificate socket bindings had reverted to a previous one-certificate- to-many-sockets configuration, and none of my previous changes were in evidence. Attempts to reimport the key files were repeatedly unsuccessful. Nevertheless, if accessing any of the sites in question via https, the client browser acts as if the proper certificate is present, and does not give any indication otherwise-"Cerificate matches page you are trying to view"

Does anyone have any suggestions on recovering the usability of those key pairs? I'd like to avoid having to repeat the generation, application, and installation steps I've done thus far, if at all possible?

3 replies

by loren

Chances are your protected storage in the registery is hosed. When you "delete" a certificate... it is still referenced in the registery and will cause problems. You need to clean the registry and then request and reinstall new key pairs.

This is a solution from Microsoft...

Below are the instructions for Removing and Reinstalling the Protected Storage Service.

1. Verify that pstores.exe is present in the \winnt\system32 directory.
2. Stop the Protected Storage Service through Control Panel\Services. Close the Control Panel.
3. Open Regedt32.
4. Delete the key HKLM\System\CurrentControlSet\Services\ProtectedStorage.
5. Select the key HKLM\Software\Microsoft\Protected Storage System Provider, and then open the permissions under the Security menu.
6. Add the Administrators Group (yourself) to the permissions with Full Control. Ensure that the Replace Permission on Existing Subkeys box is checked.
7. Delete the key HKLM\Software\Microsoft\Protected Storage System Provider.
8. Reboot the machine and log back on.
9. Run "pstores.exe -install" from the Start, Run, menu. You will not receive any indication that the program has run. It only takes a couple of seconds though.
10. Reboot the machine and log back on.
11. Verify that the service is present and running in Control Panel\Services.
12. Open Regedt32 and verify that the key HKLM\Software\Microsoft\Protected Storage System Provider (it should be grayed out).

by argent

I had really hoped to avoid that request and reinstallation process, but if it can't be avoided, that's that. I appreciate the dead-on guidance that will prevent having to dope out the issues that would otherwise have resulted.

This discussion is closed to new replies.