Article ID: 842087 - Last Review: May 19, 2004 - Revision: 1.2

Known issues in Commerce Server 2002 Service Pack 3

This article discusses known issues in Microsoft Commerce Server 2002 Service Pack 3 (SP3). See the Commerce Server 2002 SP3 documentation for complete information.

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

842086 (http://support.microsoft.com/kb/842086/ ) List of bugs that are fixed in Commerce Server Service Pack 3

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:

328814 (http://support.microsoft.com/kb/328814/ ) How to obtain the latest Commerce Server 2002 service pack

Back to the top

MORE INFORMATION

Do not include a space character 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 character in the project name. If you include a space character in the project name, you cannot compile the project without errors.
Change the BDRefresh.asp script to use full paths
When you use Commerce Server Business Desk to publish campaigns, catalogs, and profiles, you may receive an error message. This problem occurs because you use a relative redirect for the page that you are publishing. To prevent this problem, change the BDRefresh.asp script 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 (SP1). 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 in Microsoft Windows 2000
To use the .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 Component supports events and statistics check box.
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 Component supports events and statistics check box.
8. Click OK to save this change.
9. Quit Component Services.
Two authentication prompts appear 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 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 if the AuthFilter filter 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 (http://support.microsoft.com/kb/830520/ ) Two authentication prompts when you use an ISAPI filter for authentication