INFO: Known Issues in Commerce Server 2002 Service Pack 2

This article discusses known issues in Commerce Server 2002 Service Pack 2 (SP2). See the Commerce Server 2002 SP2 Documentation for complete information.

For additional information about the problems that Commerce Server 2002 Service Pack 2 fixes, click the following article number to view the article in the Microsoft Knowledge Base: For additional information about how to obtain Commerce Server 2002 service packs, click the following article number to view the article in the Microsoft Knowledge Base:

• Do not include a space in the name of a Microsoft Visual Studio .NET 2003 project
  When you create a Commerce Server project in Visual Studio .NET 2003, do not include a space in the project name. If you include a space in the project name, you cannot compile the project without errors.
• Change BDRefresh.asp to Use Full Paths
  When you use Commerce Server Business Desk to publish campaigns, catalogs, and profiles, an error may occur. This problem occurs because you use a relative redirect for the page that you are publishing. To prevent this problem, change BDRefresh.asp to use the full paths of the pages that you publish.
  
  In BDRefresh.asp, change the following lines of code:

  Response.Redirect "BDRefresh.aspx?" $ 
  Request.ServerVariables("QUERY_STRING")

  Change to:

  Response.Redirect "http://" & Request.ServerVariables("SERVER_NAME") & ":" 
  & Request.ServerVariables("SERVER_PORT") & 
  replace(Request.ServerVariables("SCRIPT_NAME"), "BDRefresh.asp", 
  "BDRefresh.aspx") & "?" & Request.ServerVariables("QUERY_STRING")

• List Manager CreateFromSQL and ExportToSQL methods have changed
  This issue first appeared in Commerce Server 2002 Service Pack 1.
  
  The List Manager CreateFromSQL and ExportToSQL methods have been rewritten to increase accuracy. Because these methods have been rewritten, you may experience decreased performance.
• Change the Component Services settings to use the Microsoft .NET Framework 1.1 on Microsoft Windows 2000
  To use the Microsoft .NET Framework 1.1 on a computer that is running Windows 2000, you must change the Component Services settings for Commerce Server 2002. To do this, follow these steps:
  1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.
  2. Expand COM+ Applications, expand Commerce Server Pipeline, and then expand Components.
  3. Click Microsoft.CommerceServer.Interop.Orders.PrivateOrderGroupMtsHelperFreeThreaded, and then click Properties.
  4. Click the Activation tab, and then click to clear the check box for Component supports events and statistics.
  5. Click OK to save this change.
  6. Click Microsoft.CommerceServer.Interop.Orders.PrivateOrderGroupMtsTxHelperFreeThreaded, and then click Properties.
  7. Click the Activation tab, and then click to clear the check box for Component supports events and statistics.
  8. Click OK to save this change.
  9. Quit Component Services.
• Error message when you use Commerce Server Site Packager on Windows Server 2003
  When you use the Commerce Server Site Packager (PUP) on a computer that is running Windows Server 2003, and you add a server to an existing application in an existing site, you may receive the following error message from Site Packager:
  The IIS Configuration on this computer does not match the settings on the Commerce Server application, Application Name, to which you are adding a Web Server
  To resolve this problem, enable IncrementalSiteIDCreation. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
  332122� IIS 6.0: Web site identification numbers are not incremental
  After you enable IncrementalSiteIDCreation, you must re-create your Web sites on each Web server before you unpack Commerce Server sites or before you add a server to an existing Commerce Server application.
• Error message when you install Service Pack 2 on a computer that is running Microsoft Windows XP
  When you install Commerce Server SP2 on a computer that is running Windows XP, you receive the following error message:
  Commerce Server 2002 Service Pack 2: SP2Setup.exe � Application Error The instruction at �0x5ad74330� referenced memory at �0x0000000e�. The memory could not be �read�. Click on OK to terminate the program.
  To work around this problem, switch to the Windows Classic theme. After you apply the Windows Classic theme, Setup continues. To change the theme, follow these steps:
  1. Right-click the desktop, and then click Properties.
  2. In the Display Properties dialog box, click the Themes tab.
  3. Under Themes, click Windows Classic in the drop-down list box, and then click OK.
• Error message when you try to install Microsoft Commerce Server 2002 Developer Edition on a computer that is running Windows XP
  When you try to install Commerce Server 2002 Developer Edition on a computer that is running Windows XP, the installation does not succeed. During setup, Service Accounts are configured. After this operation, you receive the following error message:
  Error: Invalid Service Logon Information. The specified service logon "Domain\User Name" is invalid.
  Error code: Logon failure: unknown user name or bad password.
  This problem occurs because the computer is not a part of a domain (in a peer-to-peer network). Commerce Server 2002 Setup uses Security Support Provider Interface (SSPI) to do a network-style logon by using the provided user credentials. This type of validation does not require the current user to have any special rights. Also, this type of validation works on all versions of Microsoft Windows. However, on Windows XP, the ForceGuest registry value is set to 1.
  
  To resolve this problem, set the ForceGuest registry value to 0 in the following registry key:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
• Two authentication prompts when you use an ISAPI filter for authentication
  This behavior also accompanies an unexpected "301 redirect" response when the first URL that you request contains a slash mark (/) at the end of the URL. This behavior occurs only if you are running Microsoft Commerce Server 2002 on a computer that is running Microsoft Windows Server 2003.
  
  A supported hotfix is now available from Microsoft to correct this problem on Windows Server 2003. If you are running Commerce Server 2002 on a computer that is running Windows Server 2003, and AuthFilter is in Windows Authentication mode, you must apply this hotfix.
  
  For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
  830520� Two authentication prompts when you use an ISAPI filter for authentication

For more information, see the Commerce Server 2002 Service Pack 2 documentation.