Consider the following scenario:

• You have a computer that has Microsoft Commerce Server 2009 installed.
• You create a Commerce Server 2009 Web site that is integrated into Microsoft SharePoint by using SharePoint Commerce Services Configuration Wizard.
• You host the site data in SQL Server on another computer.
• The site uses Windows Integrated Authentication (also known as NTLM authentication).
• You try to open the site by using a Windows account.

In this scenario, you cannot open the site. Additionally, you receive an error message that resembles the following:Notes

• This problem does not occur when you use forms-based authentication on the site.
• When this problem occurs, you can still open SharePoint sites that use NTLM authentication if the sites are not Commerce Server 2009 sites.

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 this specific problem.

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, submit a request to 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: - 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 Commerce Server 2009 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart Internet Information Services (IIS) after you apply this hotfix. To restart IIS, at a command prompt, type IISRESET /RESTART, and then press ENTER.
Note This command stops and then restarts all IIS services that are running.

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.

File information forCommerceServer2007SP3-KB975603-ENU.exe

File information for CS2009-KB975603-x86.exe

Installation notes

After you download the hotfix package, you obtain the following files and a source folder that contains the SiteContext.cs file:

• CS2009-KB975603-x86.exe
• CommerceServer2007SP3-KB975603-ENU.exe
• Hotfix.txt

Use the following procedures to install the hotfix that is most appropriate for your situation.

Note You must install the hotfixes as the local administrator, or run the hotfixes by using the Run as Administrator option. If you are running Windows Vista, Windows Server 2008, or a later operating system, use the Run as Administrator option if User Account Control (UAC) is enabled.

Situation 1

No sites were deployed before this hotfix was installed.
Installation instructions for situation 1

• Install the following hotfix installers:
  • CS2009-KB975603-x86.exe
  • CommerceServer2007SP3-KB975603-ENU.exe
• Run the IISRESET command.
• Run SharePoint Commerce Services Configuration Wizard to deploy the new site by using the updated MicrosoftCommerceWebParts.WSP solution file.

Situation 2

Some sites were deployed before this hotfix was installed.
Installation instructions for situation 2

• Install the following hotfix installers:
  • CS2009-KB975603-x86.exe
  • CommerceServer2007SP3-KB975603-ENU.exe
• Deploy the updated Web solution package (WSP) file by using the following stsadm command:
  stsadm -o upgradesolution -name microsoftcommercewebparts.wsp -filename MicrosoftCommerceWebParts.WSP -immediate -allowgacdeployment
• Update the "httpmodules" section of the Web.config file to use the new httpmodules.
  
  Note When you open the Web.config file, you notice that the sections that were not updated are commented out in the source code. The following is the source code for the file:

   <add name="CommerceApplication" type="Microsoft.CommerceServer.Runtime.CommerceApplicationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
  <!--<add name="CommerceOrder" type="Microsoft.CommerceServer.Runtime.Orders.CommerceOrderModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />-->
  <add name="SharePointCommerceOrder" type="Microsoft.Commerce.Providers.SharePointCommerceOrderModule, Microsoft.Commerce.Providers, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
  <!--<add name="CommerceCatalog" type="Microsoft.CommerceServer.Runtime.Catalog.CommerceCatalogModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />-->
  <add name="SharePointCommerceCatalog" type="Microsoft.Commerce.Providers.SharePointCommerceCatalogModule, Microsoft.Commerce.Providers, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
  <!--<add name="CommerceProfile" type="Microsoft.CommerceServer.Runtime.Profiles.CommerceProfileModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />-->
  <add name="SharePointCommerceProfile" type="Microsoft.Commerce.Providers.SharePointCommerceProfileModule, Microsoft.Commerce.Providers, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
  <!--<add name="CommerceExpressionEvaluator" type="Microsoft.CommerceServer.Runtime.Targeting.CommerceExpressionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />-->
  <add name="SharePointCommerceExpressionEvaluator" type="Microsoft.Commerce.Providers.SharePointCommerceExpressionModule, Microsoft.Commerce.Providers, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
  <!--<add name="CommerceDataWarehouseAuthenticationModule" type="Microsoft.CommerceServer.Runtime.CommerceDataWarehouseAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />-->
  <add name="SharePointCommerceDataWarehouseAuthenticationModule" type="Microsoft.Commerce.Providers.SharePointCommerceDataWarehouseAuthenticationModule, Microsoft.Commerce.Providers, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
  <add name="CommerceCache" type="Microsoft.CommerceServer.Runtime.Caching.CommerceCacheModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
  <add name="CommerceContentSelection" type="Microsoft.CommerceServer.Runtime.Targeting.CommerceContentSelectionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
  

• Run the IISRESET command.

Situation 3

Web parts were customized by using the CommerceSharePointExtensibilityKit tool:
Installation instructions for situation 3

• Install the following hotfix installers:
  • CS2009-KB975603-x86.exe
  • CommerceServer2007SP3-KB975603-ENU.exe
• Locate the updated source file SiteContext.cs in the source folder that is included in the hotfix package.
• Use this source file to replace the SiteContext.cs file that is in CommerceSharePointExtensibilityKit.
• Compile the Web parts assemblies.
• Update the "httpmodules" section of the Web.config file to use the new httpmodules as in situation 2.

Notes

• There may be other custom codes that require elevated permissions on the server. For example, the external data store accessing code and the error logging code both require elevated permission. These customs codes must be elevated by using the RunWithElevatedPrivileges method. This makes sure the identity of the Application Pool (also known as SharePoint System Account) is used instead of the impersonated user identity.
• The CommerceSharePointExtensibilityKit tool is in the following location:

  %Program Files%\Microsoft Commerce Server 2007\Microsoft Commerce Server 2009\Sdk\Samples\CommerceSharePointExtensibilityKit.zip

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how to configure SharePoint Commerce Services on Web servers, visit the following Microsoft Developer Network (MSDN) Web site: For more information about how to develop Web sites by using SharePoint Commerce Services, visit the following MSDN Web site: