Select the product you need help with

FIX: You cannot connect to a remote IIS 7.0 server by using IIS Manager when Shared Configuration is enabled

Article ID: 969912 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You enable Shared Configuration in Internet Information Services (IIS) 7.0. Additionally, the configuration files are located on a network share.
You enable remote connections for the Management Service.

In this situation, you cannot connect remotely to the IIS 7.0 server by using IIS Manager together with a Windows user credential. Therefore, you cannot remotely manage the IIS 7.0 server.

Back to the top | Give Feedback

If Shared Configuration is enabled in IIS 7.0, certain information is stored in the Redirection.config file. This information includes the location of the configuration files and the credential that is required to access the configuration files. This credential includes a user name and an encrypted password.

This issue occurs because, when a remote Windows user tries to connect to the IIS 7.0 server by using IIS Manager, IIS 7.0 tries to decrypt the encrypted password in the Redirection.config file to obtain the credential. To do this, IIS 7.0 uses the user identity of the remote Windows user. However, the user account to access the configuration data differs from the user account of the remote Windows user. Therefore, the password cannot be decrypted, and the connection attempt fails.

Note By default, the Redirection.config file is located in the %WinDir%\System32\Inetsrv\Config folder of the IIS 7.0 server.

Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have IIS 7.0 installed to apply this hotfix. You must install this hotfix on a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008.

Restart requirement

You must restart your computer if IIS is running when you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.