G
Guest
Hello!
Our website uses Microsoft Certificate Services to accept cert requests, have them approved or denied, then installed via the the web. We use this for client validation when the user logs in.
Periodically our tech support has been getting reports of users who found their certificate would not work -- after choosing the cert from the pop-up window (on IE 5.5 or above), they would get a "Page Cannot be Displayed" error. Making a new request for a new cert and installing it seemed to alleviate this problem.
However this morning i came upon the error myself after installing WinXP Service Pack 1. The cert I had before I installed the new service pack caused the error after the install.
Previously, when trying to look for solutions for our users to this issue, I did notice this KB article: http://support.microsoft.com/?kbid=811383 and had installed the q811383.exe on my machine. After the SP1 install I do see the Q811383 in the list of "Update Versions". My IE version num is 6.0.2800.1106.xpsp2.030422-1633
Is this a known issue?
-Dan
Our website uses Microsoft Certificate Services to accept cert requests, have them approved or denied, then installed via the the web. We use this for client validation when the user logs in.
Periodically our tech support has been getting reports of users who found their certificate would not work -- after choosing the cert from the pop-up window (on IE 5.5 or above), they would get a "Page Cannot be Displayed" error. Making a new request for a new cert and installing it seemed to alleviate this problem.
However this morning i came upon the error myself after installing WinXP Service Pack 1. The cert I had before I installed the new service pack caused the error after the install.
Previously, when trying to look for solutions for our users to this issue, I did notice this KB article: http://support.microsoft.com/?kbid=811383 and had installed the q811383.exe on my machine. After the SP1 install I do see the Q811383 in the list of "Update Versions". My IE version num is 6.0.2800.1106.xpsp2.030422-1633
Is this a known issue?
-Dan