Unable to Log On to an Upgraded IIS 3.0/SSL Server
Article ID: 187500
Article Last Modified on 6/23/2005
APPLIES TO
- Microsoft Internet Information Server 4.0
This article was previously published under Q187500
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
SYMPTOMS
After you upgrade from Internet Information Server (IIS) version 3.0 to
IIS 4.0, you may be unable to log on to your Secure Sockets Layer (SSL)
enabled sites.
CAUSE
The upgrade procedure does not check for keys stored by Setkey.exe.
Therefore, these keys are not available in IIS 4.0 after the upgrade.
NOTE: Setkey.exe and Keygen.exe are designed to work with Internet
Information Server 3.0 only.
WORKAROUND
To work around this problem, perform one of the following:
- Before you upgrade, start the Keyring.exe in IIS 3.0 at least one time
and commit changes. The SSL key will be stored to the place recognized
by the upgrade process.
-or-
- After you upgrade, reinstall the SSL key using Keyring.exe in IIS 4.0.
STATUS
Microsoft has confirmed this to be a problem in Internet Information
Server version 4.0. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
After you install an SSL key with Setkey.exe and start the Keyring.exe,
you may receive a pop-up message stating that keys were found. Keep in
mind that Keyring.exe recognizes them but did not install them. Setkey.exe
installs the SSL key to a different location in the registry than
Keyring.exe. IIS 3.0 Secure connections will work fine with keys installed
by Setkey.exe and Keyring.exe.
Additional query words: security
Keywords: kbbug kbpending KB187500