I've been troubled with an error that had me stumped and thought I'd
share. Our company received a certificate from a trusted CA. Upon
installation, the certificate didn't work and appeared to not have a
private key. We followed all installation instructions (which really
aren't technically difficult) with no avail. Everything looked fine
when looking at the trust chain of our certificate from our private
certificate to the intermediate and then to the trusted root
authority. We just simply couldn't connect to the web server on 443
(SSL) and saw that there are an entry in the IISDiag.exe report about
not having a valid private key installed.
The solution presented itself when we investigated the (user) personal
certificate folder in the certificate manager. All the while we'd been
messing with the local machine personal folder. At some point during
testing someone installed another private key certificate to the user
personal certificate folder. When we removed this certificate, the
local machine personal certificate private key was then able to be
"seen" by the system.
Hope this may help others.
-ak