Microsoft® Commerce Server 2002 Service Pack 4 (SP4) contains fixes made to Commerce Server 2002 since its release, and includes fixes made in Commerce Server 2002 Service Packs 1, 2, and 3.

This document provides information about the following:

Overview of Commerce Server 2002 SP4 Enhancements and Fixes

For a list of the hotfixes included in this service pack, and their related Microsoft Knowledge Base articles, see Knowledge Base article number 924899, available at http://go.microsoft.com/fwlink/?LinkID=73088.

All enhancements and fixes available in Commerce Server SP1, SP2 and SP3 are included in Commerce Server 2002 SP4.

For information about how to obtain all Commerce Server 2002 Service Packs, see http://go.microsoft.com/fwlink/?LinkID=73085.

Installation Instructions

This section contains information that you must have to install Commerce Server 2002 SP4:

Before You Install Commerce Server 2002 SP4

Before you install Commerce Server 2002 SP4, note the following requirements:

  • If you must have Commerce Server 2002 Feature Pack 1 (FP1) functionality, install FP1 before you install Commerce Server 2002 SP4. Do not install FP1 if you do not require FP1 functionality.

    Commerce Server FP1 contains a new business user experience for catalog and discount management, catalog sequencing, coupon implementation, and Microsoft Application Center-based staging. For more information about Commerce Server 2002 FP1, see http://go.microsoft.com/fwlink/?LinkID=29009.

  • Commerce Server 2002 SP4 setup requires the original Commerce Server 2002 installation .msi file.

    For example, if you installed Commerce Server 2002 from a CD, you must insert the CD into the CD drive so the Commerce Server 2002 .msi file is available to the Commerce Server 2002 SP4 installation program. The Windows installer references the .msi file.

  • Only install Commerce Server 2002 SP4 on computers already running Commerce Server 2002.

    You must install Commerce Server 2002 before you install Commerce Server 2002 SP4.

  • Commerce Server 2002 SP4 does not have an Evaluation Edition.

  • Uninstall Commerce Server 2002 SP4 before upgrading from Commerce Server 2002 Standard Edition to Enterprise Edition.

    If you upgrade from Commerce Server 2002 Standard Edition to Commerce Server 2002 Enterprise Edition, and you have already installed Commerce Server 2002 SP4, you must uninstall Commerce Server 2002 SP4 before you upgrade to Commerce Server 2002 Enterprise Edition.

    After you install the Enterprise Edition, you must then reinstall Commerce Server 2002 SP4.

  • If you maintain a Web farm on which all servers have Commerce Server 2002 installed, you must install Commerce Server 2002 SP4 on each server in the Web farm.

    You can install Commerce Server 2002 SP4 silently at the command prompt; for instructions, see Command Line Instructions for Installing Commerce Server 2002 Service Pack 4. Disable the hotfix update tool before you install the service pack silently. You only have to run the hotfix update tool (which updates your stored procedures) on one computer that is running SQL Server—and you run the tool manually. For instructions, see Running the Hotfix Update Tool Manually.

  • Do not use Commerce Server Business Desk, Commerce Server Manager, or Commerce Server Site Packager when you are installing Commerce Server 2002 SP4.

    If you install Commerce Server 2002 SP4 when one of these applications is running, Commerce Server 2002 SP4 may be unable to update the Product Catalog database, and the system will prompt you to restart your computer.

  • Before you install Commerce Server 2002 SP4, back up your Commerce Server 2002 databases.

    As with any update of a system, this step is a recommended operations procedure.

  • Commerce Server 2002 SP4 does not update the Solution Sites.

  • Close all applications and reset IIS before running Commerce Server 2002 SP4 Setup.

Platform Recommendations

You can install Commerce Server 2002 SP4 on Microsoft Windows® 2000 or Windows Server® 2003 R2 Enterprise Edition or Windows Server 2003 Enterprise Edition with Service Pack 1.

You can also install Commerce Server 2002 SP4 Developer Edition on Windows XP or Windows 2000 Professional.

Windows Server 2003 Platform Recommendations

For optimal performance, we recommend that you install the following software in the following order:

Important
After you install Commerce Server on Windows Server 2003 R2 Enterprise Edition or Windows Server 2003 Enterprise Edition with Service Pack 1, you must perform additional steps to configure Windows Server 2003 correctly. For instructions, see "Installing Commerce Server 2002 on Windows Server 2003" in the Commerce Server 2002 Installation Guide at http://go.microsoft.com/fwlink/?LinkID=6125.

  1. Windows Server 2003 R2 Enterprise Edition or Windows Server 2003 Enterprise Edition with Service Pack 1.

  2. All Windows Server 2003 critical updates, available at http://go.microsoft.com/fwlink/?LinkID=18673.

  3. Visual Basic® 6.0 Runtime Service Pack 6.

  4. SQL Server 2000 Enterprise Edition.

  5. SQL Server 2000 Analysis Services.

  6. SQL Server 2000 Service Pack 4.

  7. SQL Server 2000 Analysis Services Service Pack 4.

  8. Microsoft Office XP Web Components.

  9. Microsoft Visual Studio® .NET 2003 (optional).

Windows 2000 Platform Recommendations

For optimal performance, we recommend that you install the following software in the following order:

  1. Windows 2000 Server, Advanced Server, Service Pack 4

  2. All Windows Server 2000 critical updates, available at http://go.microsoft.com/fwlink/?LinkID=18673.

  3. Microsoft Visual Basic 6.0 Runtime Service Pack 6.

  4. SQL Server 2000 Enterprise Edition.

  5. SQL Server 2000 Analysis Services.

  6. SQL Server 2000 Service Pack 4.

  7. SQL Server 2000 Analysis Services Service Pack 4.

  8. Microsoft Office XP Web Components.

  9. Microsoft .NET Framework 1.0 with Service Pack 2 or .NET Framework 1.1 with Service Pack 1.1.

  10. Microsoft Visual Studio .NET 2003 (optional).

  11. MSXML 4.0 and Service Pack 2.

  12. Microsoft Data Access Components (MDAC) 2.8.

Note
For information about how to use .NET Framework 1.1 on Windows 2000 with Commerce Server 2002, see Microsoft Knowledge Base article number 842086, available at http://go.microsoft.com/fwlink/?LinkID=28963.

Installing Commerce Server 2002 SP4 on One Computer

The files for Commerce Server 2002 SP4 are in a single executable file, CS2002-SP4-<language>.exe (for example, CS2002-SP4-ENU.exe for the English version). When you run this file, Setup extracts the Commerce Server 2002 SP4 setup files to the directory you select.

Commerce Server 2002 SP4 does not update code for the Solution Sites.

Note
During installation, Commerce Server 2002 SP4 requires access to the original installation source of Commerce Server 2002 (the CD drive or network share). For example, if you installed Commerce Server 2002 from a CD, insert the CD into the CD drive so the Commerce Server 2002 .msi file is available.

To install Commerce Server 2002 SP4 on one computer

  1. Download Commerce Server 2002 SP4 from the Commerce Server Web site, available at http://go.microsoft.com/fwlink/?LinkID=70768.

  2. Double-click the downloaded file, CS2002-SP4-<language>.exe, to extract the Setup files.

  3. In the Microsoft Commerce Server 2002 Service Pack 4 dialog box, specify the directory where you want to extract the Commerce Server 2002 SP4 files.

  4. Double-click Sp4setup.exe to install Commerce Server 2002 SP4.

Installing Commerce Server 2002 SP4 in a Multiple Computer Environment

If you have multiple Web servers and multiple Commerce Server databases, you can use the silent installation to install Commerce Server 2002 SP4. We recommend that you install the updates as follows:

  • Install Commerce Server 2002 SP4 on each Web server by using the silent installation commands. Disable the hotfix tool so that you do not run it multiple times. For information about how to use the silent installation commands and disabling the hotfix tool, see Command Line Instructions for Installing Commerce Server Service Pack 4.

  • Run the hotfix update tool manually on one computer that is running SQL Server. The hotfix tool checks the connection strings and updates the appropriate databases on the network. For information about how to run the hotfix update tool, see Running the Hotfix Update Tool Manually.

Adding DCOM Config Settings for List Manager

This topic only applies to Microsoft Windows 2000.

Before users can run security scripts to assign permissions to the List Manager service, you must add the current user to the DCOM config settings. To do this, configure the user accounts by using one of the following options:

  • Change the List Manager service account to use the local system account, and then restart the List Manager service.

  • Use Dcomcnfg.exe to set the security configuration for the List Manager service component. The following steps explain how to do this.

To set the security configuration for List Manager

  1. Click Start, click Run, type Dcomcnfg, and then press ENTER.

  2. In the Distributed COM Configuration Properties dialog box, on the Applications tab, click Microsoft Commerce Server ListManager Service, and then click Properties.

  3. In the Application Properties dialog box, on the Security tab, click Use custom access permissions, and then click Edit.

  4. In the Registry Value Permissions dialog box, click Add.

  5. Add the Administrators group on the local computer, in the Type of Access box, select Allow Access.

    The Administrators group must have the Log on as a service right option selected.

  6. Click OK to save the changes, click OK to exit the Properties dialog box, and then click OK to exit Dcomcnfg.

  7. Restart the List Manager service.

Updating Business Desk

Commerce Server 2002 SP4 contains an updated version of the client Business Desk installation files. When you install this version of Business Desk, you download files from the Business Desk virtual directory of the Business Desk Server. Previous versions of Business Desk contained MSXML2, which has known security vulnerabilities. SP4 contains a new version of the client setup file. This new setup file does not contain MSXML2. To use the updated version of the client setup file, manually replace the file named ClientSetup.cab in the Business Desk virtual directory with the new file from the SP4 installation folder.

The Bizdesk.cab file in Commerce Server 2002 SP4 contains all Business Desk updates and fixes that were made in Commerce Server 2002 Service Packs 1, 2 and 3. If you want to update your Business Desk installation with these fixes, you must manually extract the updated file(s) from the Bizdesk.cab file, and then replace the file(s) in your existing Business Desk application installation.

If you modified any Business Desk files in your current installation, you must manually edit your existing Business Desk files and apply the Business Desk updates and fixes in Commerce Server 2002 SP4 to the existing file(s).

Removing Default Write Permissions for Business Desk

This topic applies to all operating systems.

When you unpack a new site that includes the Business Desk resource, the site is unpacked with default write permissions on the widgets virtual directory. You must remove these default write permissions, leaving the read permissions.

To remove write permissions for the default site

  1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.

  2. In Internet Services Manager, expand <server name>, and then expand Default Web Site.

  3. Right-click widgets, and then right-click Properties.

  4. In the widgets Properties dialog box, on the Virtual Directory tab, in the Local Path section, verify that the Write check box is clear, and then select Read. This is the default setting for Windows Server 2003 and Windows Server 2000.

Unpacking a Site: Do Not Replace Older Files

This topic applies to all operating systems.

After you unpack the retail site and open Business Desk for the first time, the .cab file is unpacked. When you replace files, you receive the following message asking whether you want to replace the file msxml2.dll on Windows Server 2003:

"Target file exists and is newer than the source (msxml2.dll). Overwrite the newer file (yes, no, cancel)?"

Click No. Do not replace the file.

Command Line Instructions for Installing Commerce Server 2002 SP4

After you save the Commerce Server 2002 SP4 files to the hard disk, you can run any one of the Commerce Server 2002 SP4 command line switches at a command prompt. Use command line switches when you want to use a script to install Commerce Server 2002 SP4 on multiple computers.

You only have to run the hotfix update tool on one computer that is running SQL Server to update your stored procedures. For more information about the tool, see Running the Hotfix Update Tool Manually.

To use command line switches to install Commerce Server 2002 SP4

  1. At the command prompt, type Sp4setup.exe </s>, and then press ENTER.

    The installation runs without messages or confirmation pages. It does not prompt you to restart your computer.

  2. Restart your computer after the installation is completed.

The following table lists the command line switches you can use for a silent installation.

Command line switch Description

/h

Runs the Help menu.

/s

Runs a silent installation. No system messages or confirmation dialog boxes appear. Automatically accepts the license agreement.

/u

Uninstalls Commerce Server 2002 SP4.

/c

Skips the installation of the Catalog Manager fixes (if applicable).

/d

Skips the installation of the Discount Manager fixes for discounts (if applicable).

/m

Skips the catalog migration tool launch. By default, after you install Commerce Server 2002 SP4, the migration tool will start and begin to apply SQL fixes to the Catalog System. If you specify this option, the tool will not start.

Uninstalling Commerce Server 2002 SP4

To uninstall Commerce Server 2002 SP4, use the Add or Remove Programs utility in Control Panel.

Important
Before you uninstall Commerce Server 2002 SP4, back up all Commerce Server 2002 databases. As with any update of a system, this step is a recommended operations procedure.

Running the Hotfix Update Tool Manually

Run the hotfix update tool to apply the hotfix updates to Commerce Server stored procedures. You can run the hotfix update tool from the computer that is running SQL Server or from the Web server. If you are running the hotfix update tool from the computer that is running SQL Server, you must specify the connection string to the computer that is running SQL Server by using the -C option. If you are running the tool from the Web server, you must specify the site name by using the -S option. You must run this tool for each site on the server.

You run the hotfix update tool from the command line. We recommend that you run the hotfix update tool manually (instead of automatically from the Service Pack user interface), in the following situations:

  • You have modified your stored procedures.

  • You will use a script to install Commerce Server 2002 on multiple computers.

The hotfix tool is included in the download package. You can run the tool from the same location as the SP4Setup.exe file.

The hotfix update tool automatically backs up the text of existing stored procedures before updating them. You can use the backup text to roll back the hotfix updates if they cause a problem in your environment.

The following table lists the executable and files included with the hotfix update tool.

Note
The system creates the log files in the same directory as the hotfix update tool.

File Description

CS2002Hotfixupdate.exe

The executable for the tool.

Update.log

The log file that stores the actions that were performed by the tool.

The actions also appear on the console.

StoredProcedureBackupText.sql

A SQL file that contains backed up versions of the stored procedures that the tool updates.

This file also contains the time that the backup started and the time that it ended.

If you apply the same hotfix multiple times you will have a separate version of the stored procedure backup text for each application of the same hotfix.

Trace.log

A log file that contains detailed tracing information that you can use to debug problems.

Every time that you run the hotfix update tool, it appends new entries to the end of the log files and the StoredProcedureBackupText file. A date and time stamp separates the new entries.

After you run the tool to install a hotfix, check the contents of the log files.

This section contains:

Command Line Instructions for the Hotfix Update Tool

Use the following command line switches to run the hotfix update tool.

Command line switch Description

-S <sitename>

Name of the site.

-C <connection string>

Connection string for the catalog database.

-R <resource name>

Specify the name of the resource to migrate. For Commerce Server 2002 Service Pack 4, this parameter is "product catalog".

-H <version to upgrade from>

Use "SP4" if you upgrade from Commerce Server Service Pack 3, and "FP1" if you upgrade from Commerce Server 2002 Feature Pack 1.

-I

Applies the hotfix to the specified site or the database specified by the connection string.

-T

Generates the Trace.log file. By default, the system does not enable tracing.

Sample Commands for the Hotfix Update Tool

The following are sample commands you can use with the hotfix update tool.

Installing hotfixes: You use the –I option to apply the hotfix to a specific site or database by using the connection string.

  • To apply the hotfixes in Commerce Server 2002 SP4 by using the connection string, type:

    CS2002HotFixUpdate.exe –I –R "Product Catalog" –C "connection string" –H "SP4"
  • To apply the hotfixes in Commerce Server 2002 FP1 by using the connection string, type:

    CS2002HotFixUpdate.exe -I -R "Product Catalog" -C "connection string" -H "FP1"
Note
Always review the log files after you install a hotfix.

Known Issues in Commerce Server SP4

This section describes known issues that you may encounter after you install Commerce Server 2002 SP4.

This section contains:

Internet Explorer 7 and future Windows Updates

In order to run Business Desk applications with Microsoft Internet Explorer 7 and future Microsoft Windows Updates, you will need to update your Business Desk site code to replace explicit references to MSXML2.XMLHTTP.2.6 with MSXML2.XMLHTTP. Follow the instructions in Microsoft Knowledge Base article 926509 located at http://go.microsoft.com/fwlink/?LinkID=75046, to update your Business Desk site code.

Error occurs when browsing to variants on a runtime site built from Retail.pup

After you apply Commerce Server 2002 SP4, the following error occurs when you browse to variants on a runtime site built from Retail.pup:

Microsoft VBScript runtime (0x800A01A8)Object required: 'MSCSCatalogAttribs.Value(...)'/retail/product.asp, line 356

Use the following steps to resolve this error.

To resolve the error

  1. Open product.asp in Notepad.

  2. Change line 356 from:

    If (fldProp.Name <> "TimeStamp") And (fldProp.Name <> "cy_list_price") And (fldProp.Name <> "VariantID") Then

    - to -

    If (fldProp.Name <> "DisplayName") And (fldProp.Name <> "TimeStamp") And (fldProp.Name <> "cy_list_price") And (fldProp.Name <> "VariantID") Then

SP4 uninstall does not revert Commerce Server project .vsz files correctly

When you try to create a Commerce Server project by using Visual Studio after you have uninstalled SP4, Visual Studio returns an error.

This error occurs because the uninstallation process replaces the path string "C:\Program Files\Microsoft Commerce Server 2002" with "%CS2002PATH%", which is an environment variable that does not exist.

To fix this behavior, all .vsz files under drive:\Program Files\Microsoft Commerce Server 2002\VS2003\CommerceProjects (if you are working with Visual Studio 2003)

- or -

drive:\Program Files\Microsoft Commerce Server 2002\VS\CommerceProjects (if are working with Visual Studio 2002)

must be updated according to the steps outlined in KB article 831134. located at http://go.microsoft.com/fwlink/?LinkID=73872.

Do not include a space in the name of Visual Studio 2003 projects

When you create Commerce Server projects with Microsoft Visual Studio® .NET 2003, do not include a space in the project name. If you include a space in the project name, you will be unable to compile the project without errors.

Modify BDRefresh.asp to use full paths

When you use Business Desk to publish campaigns, catalogs, and profiles, an error may occur.

This problem is the result of using a relative redirect for the page that you are publishing. To prevent this problem, modify the file BDRefresh.asp to use the full paths for the pages you want to publish.

In the file BDRefresh.asp, change these lines:

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

To the following lines:

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 originated in Commerce Server 2002 Service Pack 1.

The List Manager CreateFromSQL and ExportToSQL methods increase accuracy. This change may cause decreased performance because of the rewriting of these methods.

Additional Information

For more information about Microsoft Commerce Server 2002, see the following Web sites and newsgroups:

About Product Support

If you have technical questions about Commerce Server 2002 SP4 that are not answered in this Readme or in the Microsoft Knowledge Base articles, Microsoft offers technical support and services that range from free, to pay-per-incident, to annual support plans. Some of these plans may be available 24 hours a day, seven days a week. Microsoft offers the following support:

______________________________________________

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, MSDN, Visual Basic, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.