Article ID: 980588 - View products that this article applies to.
When a Windows Communication Foundation (WCF) client has no service principal name (SPN) in the WCF client configuration file, the client uses the HOST SPN for the Kerberos authentication. On the computer that hosts the WCF service, the HOST SPN is registered for the computer account. This is by default. When the service is running under a custom domain account, the default SPN must be deleted, and then be registered again for the domain account. Doing this lets the client call the service successfully. However, doing this causes some services on the computer that use the deleted HOST SPN to run abnormally. The hotfix that is described in this article lets a WCF service use the default HOST SPN that is registered for the computer account.
Windows XP and Windows Server 2003
Hotfix informationA 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 this specific problem. 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.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
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=supportOr, you can download this hotfix rollup from the following Microsoft Connect Web site:
PrerequisitesYou must have the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply the hotfix if the affected files are not being used.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
For all supported x86-based versions of Windows Server 2000, of Windows Server 2003 and of Windows XP
Collapse this tableExpand this table
For all supported x64-based versions of Windows Server 2000, of Windows Server 2003 and of Windows XP
Collapse this tableExpand this table
Windows Vista and Windows Server 2008To resolve this problem in Windows Vista or in Windows Server 2008, download and apply the hotfix that is described in Microsoft Knowledge Base article 981001. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/981001/ )A hotfix rollup is available for Windows Communication Foundation in the .NET Framework 3.5 SP1 for Windows Vista SP2 and Windows Server 2008 SP2
Windows 7 and Windows Server 2008 R2To resolve this problem in Windows 7 or in Windows Server 2008 R2, download and apply the hotfix that is described in Microsoft Knowledge Base article 981002. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/981002/ )A hotfix rollup is available for Windows Communication Foundation in the .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix also contains the hotfix that is described in Microsoft Knowledge Base article 974842. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/974842/ )A hotfix is available that lets you use the Security Token Reference-Transform mechanism to reference issued tokens in a .NET Framework 3.5-based WCF application
Article ID: 980588 - Last Review: October 6, 2011 - Revision: 2.0