Content Updated: August 15, 2003
Added information about obtaining Commerce Server 2002 Service Pack 2, which includes support for installing on Microsoft® Windows Server™ 2003, and support for installing Commerce Server 2002 Developer Edition on Windows XP and Windows 2000 Professional.
This document provides detailed instructions for installing Microsoft® Commerce Server 2002 (Commerce Server 2002) on a single computer. These instructions apply to all editions of Commerce Server.
These instructions are intended for single-computer installations and do not include information about securing Commerce Server 2002 services during installation. For information about securing your Commerce Server installation, see "Securing Your Site" in Commerce Server 2002 Help.
Important It is strongly recommended that you install Microsoft Commerce Server 2002 using Microsoft Windows Integrated Security, and that you secure your databases to use Windows Authentication.
For information about upgrading from Commerce Server 2000 or a pre-release version of Commerce Server 2002, see "Upgrading Commerce Server 2002 Evaluation Edition or Prerelease Versions" in the Commerce Server 2002 Upgrade Guide at http://go.microsoft.com/FWLink/?LinkID=5591.
It is recommended that you use Microsoft Windows Advanced Server or Datacenter Server because you may eventually need more than 2 gigabytes of memory. The /3 gigabyte switch is only available with Advanced Server or Datacenter Server. In addition, with Advanced Server or Datacenter Server, you can configure Network Load Balancing clusters to deliver the reliability and performance that high-volume Web servers need.
Note For Commerce Server product information such as the product version and product ID, visit the Microsoft Developer Network (MSDN®) site at http://go.microsoft.com/FWLink/?LinkID=5161. The "Platform SDK: Windows Installer" in the MSDN Library contains the MsiGetProductInfo function, which returns product information for published and installed products. You can also add Microsoft® Windows® Installer functionality to Commerce Server 2002 from the MSDN Library by using the MsiInstallProduct function.
Important After you install Commerce Server 2002, it is recommended that you install Commerce Server 2002 Service Pack 2. For information about downloading Service Pack 2, see the Microsoft Commerce Server Web page at http://go.microsoft.com/fwlink/?LinkId=18865.
It is recommended that you read through this document completely before installing Commerce Server 2002. The following topics are addressed:
This section lists the hardware requirements for Commerce Server 2002, Administration tools, and the Commerce Server Business Desk client.
Note Actual requirements will vary based on your system configuration and the applications and features you choose to install.
The hardware requirements for a Commerce Server 2002 server installation are:
In your production environment, the volume of traffic on your Web site may dictate more stringent hardware requirements for Web servers.
The hardware requirements for a Commerce Server 2002 installation with Administration tools only are:
The hardware requirements for a Commerce Server Business Desk client are:
This section lists the software requirements for Commerce Server 2002, Administration tools, and the Commerce Server 2002 Business Desk client.
For information about distributed software requirements, see "Deploying Your Site" in Commerce Server 2002 Help.
Important Microsoft Professional Support Services supports only the platforms described in this section.
Windows Server 2003 Platform
Commerce Server 2002 Service Pack 2 enables you to install on Windows Server™ 2003, and the Windows Server™ 2003 platform includes the following software.
Note Commerce Server 2002 Service Pack 2 enables support for SQL Server 64-bit.
Note SQL Server Enterprise Edition is required if you plan to install any of the Commerce Server 2002 Solution Sites.
Windows 2000 Platform
Note It is recommended that you use Microsoft Windows Advanced Server or Datacenter Server because you may eventually need more than 2 gigabytes of memory. The /3 gigabyte switch is only available with Advanced Server or Datacenter Server. In addition, with Advanced Server or Datacenter Server, you can configure Network Load Balancing clusters to deliver the reliability and performance that high-volume Web servers need.
Note You can install Commerce Server 2002 Administrative Tools, the Business Desk, and Commerce Server 2002 Help on a computer running Windows 2000 Professional or Windows XP.
Note Windows 2000 Service Pack 4 is the recommended Service Pack, which includes Windows 2000 Security Rollup Package 1.
Note Internet Explorer 6 is the recommended browser for Commerce Server 2002.
Note MDAC 2.8 is recommended. You can download it from http://go.microsoft.com/fwlink/?LinkId=18915.
Note Commerce Server 2002 Service Pack 2 enables support for SQL Server 64-bit.
Note SQL Server Enterprise Edition is required if you plan to install any of the Commerce Server 2002 Solution Sites.
Note The MSXML 3.0 Security Fix is recommended.
Note The MSXML 4.0 Security Pack 1 is recommended.
Note You do not need to install this Microsoft® Internet Information Services (IIS) patch if you installed Windows 2000 Service Pack 3 or 4.
Note You do not need to install this Rollup Package if you installed Windows 2000 Service Pack 3 or 4.
In addition to the required software, install the following software before installing Commerce Server 2002:
Note To deploy an ASP.NET-based site on a Web server, install .NET Framework 1.0 on the Web server.
Note For information about using .NET Framework 1.1 on Windows 2000 with Commerce Server 2002, see Microsoft Knowledge Base article number 825329, available at http://go.microsoft.com/fwlink/?LinkId=18841.
If you want to install only the Administration tools, you must install the following software:
Note Windows 2000 Service Pack 3 is the recommended Service Pack, which includes the Windows 2000 Security Rollup Package 1.
Note Internet Explorer 6 is the recommended browser for Commerce Server 2002.
In order for Business Desk users to use Analysis Services over HTTP or HTTPS, your Commerce Server installation must use SQL Server 2000 Enterprise Edition. You cannot connect to SQL Server 2000 Standard Edition with HTTP connectivity. For more information about enabling a Business Desk user to run dynamic reports over HTTPS, see "Accessing the Analysis Server Over HTTPS" in Commerce Server 2002 Help.
Before you install the Commerce Server Business Desk client, you must install the following software on the client computer:
Note Internet Explorer 6 is the recommended browser for Commerce Server 2002.
Important Notes
This section provides an overview of how to install the software required by Commerce Server 2002.
This section contains:
Commerce Server 2002 Service Pack 2 enables you to run Commerce Server on Microsoft® Windows Server™ 2003.
If you want to install only the Administration tools or Commerce Server 2002 Help, you can use Microsoft® Windows® 2000 Professional.
Note Commerce Server 2002 does not support upgrading from Windows NT 4.0 to Windows 2000 Server, and then installing Commerce Server 2002.
Note It is recommended that you use Microsoft Windows Advanced Server or Datacenter Server because you may eventually need more than 2 gigabytes of memory. The /3 gigabyte switch is only available with Advanced Server or Datacenter Server. In addition, with Advanced Server or Datacenter Server, you can configure Network Load Balancing clusters to deliver the reliability and performance that high-volume Web servers need.
Important If you want to install the Direct Mailer or the Predictor as highly available clustered resources, Microsoft Windows 2000 Advanced Server or Datacenter Server is required. Only Window 2000 Advanced Server and Datacenter Server include the Network Load Balancing feature so you can create Network Load Balancing clusters; Windows 2000 Server does not include that feature.
Note You can install Microsoft® Active Directory® directory service and use it with your Profiles data stores. For information about setting up your Active Directory servers, see "Setting Up Your Active Directory Servers" in Commerce Server 2002 Help. For information about adding profile data stores, see "Running the Profiles Resource" in Commerce Server 2002 Help.
The Commerce Server Business Desk client requires Internet Explorer version 5.5 Service Pack 2 or later. In a single-computer installation in which the server is also being used as the Business Desk client, you must install Internet Explorer 5.5 Service Pack 2 or later. However, in a typical multi-computer environment in which the Business Desk client and Commerce Server 2002 are on different computers, you do not need to install Internet Explorer on the computer running Commerce Server 2002.
The Windows 2000 Security Rollup Package 1 (SRP1) includes all security updates that have been delivered since Windows 2000 Service Pack 2. To download this package, navigate to the Windows 2000 Security Rollup Package Web page at http://go.microsoft.com/FWLink/?LinkID=6529. For more information about Windows 2000 SRP1, including a list of security fixes, see the Microsoft Knowledge Base article, "Windows 2000 Security Rollup Package 1 (SRP1)" at http://go.microsoft.com/FWLink/?LinkID=6537.
If Commerce Server 2002 must connect to a remote SQL Server computer, you must install Microsoft Data Access Components (MDAC) 2.7 on your Commerce Server 2002 computer, SQL Server 2000 computer, and Analysis Services computer.
Note When you install SQL Server 2000 Service Pack 3 (a step explained later in this document), you will automatically install MDAC 2.7 Service Pack 1a.
Note MDAC 2.8 is recommended. You can download it from http://go.microsoft.com/fwlink/?LinkId=18915.
Install MDAC 2.7 from the Commerce Server 2002 product CD (\Support\MDAC 2.7\mdac_typ.exe).
To obtain the latest MDAC Service Pack, see the Microsoft Knowledge Base article 820910 “How to Obtain the Latest MDAC 2.7 Service Pack,” available at http://go.microsoft.com/fwlink/?LinkId=18864.
With Commerce Server 2002 Service Pack 2, you can use Microsoft® SQL Server 2000 32 bit or 64 bit.
Commerce Server 2002 requires an installation of SQL Server 2000 on your Commerce Server 2002 computer, or an installation on a remote computer to which Commerce Server 2002 will have access.
Commerce Server 2002 does not support a Microsoft SQL Server™ 7.0 configuration.
Important It is strongly recommended that you install Commerce Server 2002 using Microsoft Windows Integrated Security, and that you secure your databases to use Windows Authentication. If you install SQL Server using Windows Authentication you must install Commerce Server using Windows Authentication.
Note If you have SQL Server running on a LAN or WAN elsewhere in your organization, you do not have to install the server components of SQL Server 2000 on the same computer as Commerce Server 2002.
Note In a distributed deployment, you must install Microsoft Data Access Components (MDAC) 2.7 and the MDAC Service Pack 1 on the Commerce Server computer, the SQL Server 2000 computer, and the Analysis Services computer.
Note If you are using the SQL Server 2000 Evaluation Edition to evaluate Commerce Server 2002, you do not need to apply SQL Server 2000 Service Pack 3.
Important If you install SQL Server using Windows Authentication mode, then you cannot unpack a Commerce Server site using SQL Authentication mode.
Note When SQL Server Setup detects that a computer is running the U.S. English locale, SQL Server Setup automatically selects the following SQL collation: Dictionary order, case-insensitive, for use with 1252 character set. Do not change this to case-sensitive. Commerce Server Setup will complete if you are using accent-sensitive, but will fail if the collation is binary or case-sensitive.
If you plan to install Commerce Server Direct Mailer, you must start SQL Server Agent.
Analysis Services must be installed on the Analysis server used by the Data Warehouse and the server used to unpack the Data Warehouse resource (if the Analysis database exists on a different computer than the one used to unpack). Perform the following steps if you have not already installed the SQL Server 2000 Analysis Services.
Note If you install Analysis Services on your computer after you install Microsoft Office XP, OLAP-based PivotTables in Excel XP are no longer able to communicate with Analysis Services. For information about reconnecting to the OLAP server, see Cannot connect to the OLAP server when unpacking a site in this document.
SQL Server 2000 Service Pack 3 (SP3) addresses specific issues discovered in SQL Server 2000 since its initial release. Because SQL Server Service Packs are cumulative, SP3 includes all fixes from previously released Service Pack 1 (SP1) and Service Pack 2 (SP2), and can be applied to either an original installation of SQL Server or to one which has already had SP1 or SP2 applied.
Note When you install SQL Server 2000 Service Pack 3, you will automatically install MDAC 2.7 Service Pack 1.
To install SQL 2000 Service Pack 3
Note If you are using the SQL Server 2000 Evaluation Edition to evaluate Commerce Server 2002, you do not need to apply SQL Server 2002 Service Pack 3.
SQL Server 2000 Analysis Services Service Pack 3 (SP3) for the Analysis Services components of SQL Server 2000 includes the following updates:
To install SQL Server 2000 Analysis Services Service Pack 3
When you install Microsoft SQL Server, by default the number of SQL Server connections is set to zero (0), indicating that you can have an unlimited number of connections. Changing this setting is not recommended.
If you choose to change the number of connections, you must allocate four connections for each computer in your Commerce Server installation.
Perform the following two procedures only if you have changed the number of SQL Server connections from zero, and you now need to determine the number of SQL Server connections currently in use and set the number of SQL Server connections you need.
To determine the number of SQL Server connections currently in use
select * from master..sysprocesses where hostname <>''where '' is two single quotes.
Query Analyzer displays the number of SQL Server connections currently in use. The number of rows equals the number of SQL Server connections.
The Microsoft Office XP Web Components are located on the Commerce Server 2002 CD in the following folder: \\Program Files\Commerce Server 2002\Widgets\OWC10\<xxxx>\owc10.exe, where xxxx is the Business Desk locale ID.
The following codes are valid Business Desk locale IDs:
To ensure full functionality of the Office Web Components, install them using one of the following setup programs:
You can also run the owc10.EXE file and install it in the <drive:>\Program Files\Commerce Server 2002\Widgets\OWC10\<xxxx>\owc10.exe folder, where xxxx is the Business Desk locale ID. The controls installed in this manner display dynamic reports; however, the downloaded controls are not licensed and do not enable full functionality of the Office Web Components.
Note If Internet Explorer 6 is installed on the computer on which you are installing Commerce Server 2002, you do not need to install MSXML 3.0 SP2.
Install MSXML 3.0 SP2 from the Commerce Server 2002 product CD (\Support\MSXML 3.0 Sp2\msxml3sp2setup.exe).
MSXML 4.0 is used when product catalogs are imported. You can install MSXML 4.0 with MSXML 3.0 SP2 on the same computer in side-by-side mode.
Install MSXML 4.0 from the Microsoft XML Core Services 4.0 Web page at http://go.microsoft.com/fwlink/?LinkId=6935.
Install this hotfix from the Commerce Server 2002 product CD (\Support\Platform Updates\VBRun60sp5.exe).
When an Active Server Pages (ASP) script uses the Server.HTMLEncode and Server.URLEncode methods, if the session codepage is set to UTF8, the data on certain strings may become corrupted. Hotfix Q294831 corrects the way IIS allocates buffer size for UTF8 characters.
This hotfix (COM+ Rollup Package 18.1) includes an accumulation of COM+ hotfixes that have been available since the release of Windows 2000 SP2. To install Hotfix Q313582 do the following:
Note It is recommended that you deploy the current security implementation best practices, including the IIS Lockdown Tool, at http://go.microsoft.com/fwlink/?LinkId=13012.
Before you install Commerce Server 2002, you must have first installed SQL Server 2000 and Analysis Services and several other applications. For a complete list of the required software and the order of installation, see Software Requirements.
Before you start the Commerce Server 2002 Setup, make sure your Windows 2000 logon account is a member of the Administrators group on the installation computer. For more information about Windows 2000 logon accounts, see the Windows 2000 online documentation.
Note To install Commerce Server 2002 from within Windows Terminal Services, you must use a Uniform Naming Convention (UNC) path rather than a mapped drive.
This section contains:
Four types of server installation are available:
| Feature | Components |
| Run-time Objects |
|
| Analysis and Data Warehouse |
|
| Predictor service (available in Enterprise and Developer Editions only) |
|
| Direct Mailer Service |
|
| SDK |
|
| Administration Tools |
|
| Online Documentation |
|
When you install Commerce Server, you must enter a domain user account and password to be used by the following Commerce Server services:
Commerce Server Setup automatically grants the logon as a service right to the account(s) you specify. The Commerce Server 2002 Direct Mailer, List Manager service, Predictor resource, and Event Logging require an account for security and network access. Event Logging must run under a local Administrator account.
Note For evaluation purposes only, it is recommended that you use the same account for each service because it is easy to do. If this account is disabled at a later date, or if the password is changed, Commerce Server will stop working. For instructions about changing a service account or password, see "Changing a Service Account or Password" in Commerce Server 2002 Help.
The Administration database is created during the first installation of Commerce Server 2002. During installation, you must specify the name of the SQL Server computer where the Administration database is created. When you install Commerce Server 2002 on additional computers, you point the computers to the Administration database during setup. By setting up all the computers to point to this central database, you can manage all of the Commerce Server 2002 computers from a central console.
If you choose to install Direct Mailer, you will be prompted for information about where its database is located.
The following procedures describe how to install Commerce Server 2002 on one computer using the Complete installation option. You must close all other applications before proceeding.
If you are installing Commerce Server on Windows Server™ 2003, after you perform the instructions in this section, you must perform the instructions explained in Installing Commerce Server 2002 on Windows Server 2003.
Important It is strongly recommended that you install Commerce Server 2002 using Microsoft Windows Integrated Security, and that you secure your databases to use Windows Authentication.
You must perform a number of steps to install Commerce Server using Windows Integrated Security. For information about how to deploy Commerce Server using Windows Authentication and how to secure your services and databases, see "Deploying Commerce Server Using Windows Authentication" in Commerce Server 2002 Help.
Note the following:
Important If you are upgrading from Commerce Server 2000, and you customized the Direct Mailer and Predictor global resources, your custom settings will not be maintained. Before you install Commerce Server 2002, you must note the Direct Mailer and Predictor custom settings, and then manually re-enter them after the upgrade.
To install Commerce Server 2002 on one computer
Note If the Autorun Menu does not start, navigate to the root directory of the Commerce Server 2002 CD, and double-click Setup.exe.
Warning Do not double-click Microsoft Commerce Server 2002.msi. You must use Setup.exe in order to install MSI 2.0 and perform the necessary checks for your Commerce Server 2002 platform.
The installation process starts.
| Use this | To do this |
| SQL Server Computer | Type the SQL Server computer name for your Administration database. If SQL Server was installed locally, the local computer name is displayed. |
| Use Windows Integrated Security | This option uses Windows user accounts to authenticate to the Administration database on SQL Server.
When you use Windows Integrated Security, you must create accounts and assign appropriate permissions in SQL Server for the necessary database roles. For detailed instructions about using Windows Integrated Security, see "Deploying Commerce Server Using Windows Authentication" in Commerce Server 2002 Help. Note It is strongly recommended that you install Commerce Server using Windows Integrated Security, and that you secure your databases to use Windows Authentication. |
| Use a Specific User Name and Password | Check this option if you want to use SQL Server authentication when connecting to the Administration database. |
| SQL Server Login Name | Type the user account for the Administration database.
Note For security purposes, do not use the sa login for access to the Administration database. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager. |
| SQL Server Login Password | Type the login password for the Administration database.
Note You should always use strong passwords when creating SQL Server login passwords. For information about strong passwords, see "Using Strong Passwords" in Commerce Server 2002 Help. |
| Use this | To do this |
| SQL Server computer | Type the local computer name. If the computer is a virtual node of a SQL Server cluster, type the name of the virtual node.
Note If the Direct Mailer Service is clustered, the server name should be a Microsoft Windows Clustering service virtual server name, not the physical node name. |
| Use Windows Integrated Security | This option uses Windows user accounts to authenticate to the DirectMailer database on SQL Server.
When you use Windows integrated security, user names and passwords are not stored in the SQL Server connection string, and are not affected by SQL Server password resets. For information about Commerce Server security, see "Securing Your Site" in Commerce Server 2002 Help. Note It is strongly recommended that you install Commerce Server using Windows Integrated Security, and that you secure your databases to use Windows Authentication. |
| Use a Specific User Name and Password | Select this option if you want to use SQL Server authentication when connecting to the DirectMailer database. |
| SQL Server Login Name | Type the user account for the DirectMailer database.
Note For security purposes, do not use the sa login for access to the DirectMailer database. To change the login information for the DirectMailer database after it is created, use SQL Server Enterprise Manager. |
| SQL Server Login Password | Type the login password for the DirectMailer database.
Note You should always use strong passwords when creating SQL Server login passwords. For information about strong passwords, see "Using Strong Passwords" in Commerce Server 2002 Help. |
If you are creating the DirectMailer database, in the SQL Server Login Name and SQL Server Login Password boxes, type a SQL Server login that has permissions on the master database to create a new database. To view the permissions for the SQL Server login for the master database, use Enterprise Manager.
Commerce Server Setup automatically grants the logon as a service right to the account(s) you specify. The Commerce Server 2002 Direct Mailer, List Manager service, Predictor resource, and Event Logging require an account for security and network access. Event Logging must run under a local Administrator account.
Note For evaluation purposes, use the same account for each service. If this account is disabled at a later date, or if the password is changed, Commerce Server will stop working. For instructions about changing a service account or password, see "Changing a Service Account or Password" in Commerce Server 2002 Help.
If you installed Commerce Server on Windows Server 2003, you must now install Commerce Server Service Pack 2 and perform the instructions explained in Installing Commerce Server 2002 on Windows Server 2003.
For information about completing the Commerce Server 2002 installation, see Post-Installation Recommendations.
Notes
The following steps apply to a new installation of Commerce Server. If you are updating an existing installation, see the Service Pack 2 Readme for instructions about protecting your customizations.
To install Commerce Server 2002 Service Pack 2
Extract the following five files to the same directory:
Extract the following two files to the same directory. They can be in the same directory as the above files, or a different directory.
"Commerce Server 2002 has a known compatibility issue with this version of Windows and might not run as expected. For more information, contact Microsoft."
Ignore this message; it is benign. At the last screen, accept the default to run the hotfix update tool.
On each computer that is running Commerce Server 2002 and Windows Server 2003, you must perform the steps in the following topics:
You can configure 1-2 using a script, EnableCS2002Settings.vbs, included in Service Pack 2, or by manually configuring the server. Detailed instructions for configuring Windows Server 2003 are provided in the following sections.
For additional information about securing your Commerce Server installation (for example, securing service accounts, databases, and Business Desk), see "Securing Your Site" in Commerce Server 2002 Help.
Service Pack 2 includes a script, EnableCS2002Settings.vbs, which you can use to automatically configure your security settings.
Run this script on all Web servers in your environment to enable the following IIS 6.0 Web Service Extensions:
EnableCS2002Settings.vbs disables the access level checks for the two Commerce Server COM+ applications: Commerce Server Event Logging and Report Manager.
To run EnableCS2002Settings.vbs
If you do not want to run the EnableCS2002Settings script, perform the following steps to enable the required IIS Web Service Extensions manually.
Perform these steps on all Web servers in your environment to enable the following IIS 6.0 Web Service Extensions:
To enable Active Server Pages and ASP.NET
To enable Server Side Includes
If you do not perform this step, when you try to import XML catalogs, you will receive the following message: "Unable to open or create file." Business Desk uses WebDAV to transfer files from the client to the server, and WebDAV is disabled by default on Windows Server 2003 for security reasons. You must enable it.
To enable Commerce Server AuthFilter ISAPI extension
If you do not want to run the EnableCS2002Settings script, perform the following steps to disable the security settings for Commerce Server Event Logging (COM+ Applications) and Report Manager.
To disable security settings for Commerce Server Event Logging and Report Manager
Perform these steps only if you are going to use List Manager and Predictor services.
To disable the security settings for the List Manager service (DCOM Config)
Note ListManager may appear as "Microsoft Commerce Server ListManager Service."
To disable the security settings for the Predictor service (DCOM Config)
You need to set the Default Application Pools so you can use the Commerce Server 2002 .NET components.
For Windows Server 2003, you need to add IIS_WPG as a SQL login because Commerce Server Auth Manager uses it. If you are not using Auth Manager, you do not need to perform this step.
By default, the parent paths property (also known as a relative path) in Internet Services Manager (IIS) 6.0 is disabled. For applications exposed to the Internet, enabling this property exposes a security risk.
When you unpack a Solution Site onto IIS 6.0, the Enable parent paths property is enabled on both the Business Desk application and the runtime application.
This configuration is a security risk for your runtime application. After unpacking your site, you must disable the parent paths property.
This is not a significant security risk for your Business Desk application because it is on a corporate intranet.
To disable the parent paths property
When you install Commerce Server 2002 on multiple computers there are specific operations that you must perform. For information and examples to follow for installing Commerce Server 2002 in a multi-computer configuration, see "Deploying Your Site" in Commerce Server 2002 Help. For information about securing your site, see "Best Practices for Security" in Commerce Server 2002 Help.
Note the following issues:
For this setup to work, the Direct Mailer service also has to be installed on Computer B. This installation is necessary for the SQL Server Agent job on Computer B to communicate with the Direct Mailer service on Computer A. The actual mail processing is performed only on Computer A.
Note You must purchase a Commerce Server license for SQL Server.
After you install Commerce Server 2002, it is recommended that you perform the following steps:
Note If you installed Commerce Server using Windows Integrated Security, see "Deploying Commerce Server Using Windows Authentication" in Commerce Server 2002 Help.
Commerce Server provides three Solution Sites — the Blank site, the Retail site, and the SupplierActiveDirectory site. These Solution Sites include all of the resources a site developer needs to build a retail site. The Solution Sites also include a Business Desk application.
To install the Retail and SupplierActiveDirectory Solution Sites, use the Microsoft Commerce Server 2002 Solution Sites.msi file located at http://go.microsoft.com/fwlink/?LinkId=6491.
For instructions about unpacking a site, see "Using Site Packager" in Commerce Server 2002 Help.
For detailed instructions about unpacking a site in a multi-computer environment, see "Deploying Your Site" in Commerce Server 2002 Help.
Commerce Server also includes an International Retail Site (Retail2002). This is a .NET-based multilingual, multicurrency, business-to-business, and business-to-consumer Web site, which is similar to the Retail Solution Site provided for Commerce Server 2002. For information about installing this site, see Installing the International Retail Site (Retail2002).
You use Commerce Server Site Packager to unpack a site (including a Business Desk application) or a subset of site features onto one or more computers. You can run Site Packager from the Start menu, from Commerce Server Manager, or from the command line. Perform the following procedures to unpack a Blank, Retail, or SupplierActiveDirectory Commerce Server Solution Site.
For information about using the International Retail Site (Retail2002), see "Deploying the International Retail Site (Retail2002)" in Commerce Server 2002 Help.
The following instructions explain how to install a Solution Site on one computer using the Quick mode of Site Packager. Before you unpack a Solution Site, note the following:
To enable the Always send URLs as UTF-8 option
Commerce Server Site Packager starts.
| Use this | To do this |
| Site name | Type a name for the site. |
| IIS Web site | Select the name of the Internet Information Services (IIS) 5.0 Web site where the applications will be installed. |
| SQL Server Computer | Type the name of the SQL Server on which you want the site databases to be created. |
| Use Windows Integrated Security | This option uses integrated Windows Authentication.
When you use Windows Integrated Security, user names and passwords are not stored in the SQL Server connection string, and are not affected by SQL Server password resets. For information about Commerce Server 2002 security, see "Securing Your Site" in Commerce Server 2002 Help. |
| Use a specific user name and password | Check this option if you want to use SQL Server authentication when connecting to the databases. |
| SQL Server Login Name | Type a SQL Server login user name that has permissions on the SQL Server on which the site databases are to be created.
Note For security purposes, do not use the sa login for access to the databases. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager. |
| SQL Server Login Password | Type the SQL Server login password for the databases. |
| Use this | To do this |
| Name | Type a name for the pointer to the global Data Warehouse resource. |
| Server | Type the name of the SQL Analysis Services computer that the Data Warehouse will use. |
| Database | Type the name of the Analysis Services database. |
Important After unpacking a site, the Csapp.ini file is generated, which is required by AuthManager. Do not delete this file. Secure the Csappi.ini file by turning off both read and anonymous access to it in IIS. Do not use NTFS permissions to secure this file, because the file must be readable under user credentials such as the IUSR account. For more information about the Csapp.ini file, see "Csapp.ini file" in Commerce Server 2002 Help.
To access Commerce Server Business Desk for the site, you must install the Business Desk client. For instructions, see Installing the Business Desk Client.
Removing Default Write Permissions for Business Desk
When you unpack a Solution Site (which includes Business Desk), or a new site that includes Business Desk, the site is unpacked with default write permissions on widgets. You must remove these default write permissions, leaving the read permissions.
To remove write permissions for the default site
The International Retail Site (Retail2002) is available in the \Program Files\Microsoft Commerce Server 2002\SDK\Samples\ASPNET\Retail2002\Retail2002.pup folder.
To use the International Retail Site, you create a new Commerce project using Microsoft® Visual Studio® .NET. If you want to base your Web applications on the International Retail Site and use Microsoft Visual Studio .NET for your development environment, use the Custom option to unpack the International Retail Site as a new Commerce Project using Visual Studio .NET. For more information about installing the International Retail Site, see ''Deploying the International Retail Site (Retail2002)'' in Commerce Server 2002 Help.
Note To use Commerce Server 2002 .NET-based developer tools, such as the .NET Assemblies, install Microsoft Visual Studio .NET Release Candidate 3 or later, .NET Framework 1.0, and .NET Framework Service Pack 2 before installing Commerce Server 2002.
To deploy an ASP.NET-based site on a Web server, install .NET Framework 1.0. You can increase the performance of Web sites using the Commerce Server .NET Framework by changing the COM threading model for Microsoft® ActiveX® Data Objects (ADO) from apartment-threaded to both-threaded. To change ADO to both-threaded, run the makfre15.bat file located in Program Files\Common Files\System\ado.
After you unpack a site, you can install the Commerce Server Business Desk client by connecting to the URL for the Business Desk application. You must perform this step for all computers from which you want to access Business Desk, including the computer running Commerce Server.
Business managers can download and install the Business Desk client. Before you install the Business Desk client, note the following requirements:
To install the Business Desk client
To install the Business Desk client
The Business Desk Client Setup begins. The Business Desk Client requires Microsoft ActiveX controls. If the Microsoft ActiveX controls have not been downloaded, troubleshooting tips are displayed in the upper section of the Business Desk Client Setup screen.
Note If you are unable to download the ActiveX controls, follow the instructions on the Business Desk Client Setup screen.
The Business Desk icon now appears as a shortcut on your desktop and on the Start menu.
Notes
Commerce Server allows automated electronic software distribution or silent installation. Silent installation is designed to install Commerce Server in an automated way on computers that have identical configurations. It is designed for system administrators who want to install Commerce Server on remote computers without user intervention. With a silent installation, there is no need for a user to monitor the installation and provide input.
To perform a silent installation, use the command line options provided to suppress all interaction and provide parameters for all options.
When you perform a silent installation, no messages are displayed. Instead, a log file captures the installation information, including whether the installation was successful. You can then review the log file and determine the results of the installation.
Notes Commerce Server 2002 does not allow silent installation for clustered resources.
Use Commerce Server Setup to remove specific features. You cannot remove features using silent installation. In addition, if you want to add or remove only the SDK, you must use Commerce Server Setup.
Before you install Commerce Server using silent installation, do the following:
To install Commerce Server using silent installation
msiexec /I <package>.msi
For example, to install Commerce Server from your CD, type:
msiexec /I "<drive letter>:\Microsoft Commerce Server 2002.msi"
where "Commerce Server 2002" is the name of the .msi package.
The following table shows the Windows 2000 command line options that are useful for a Commerce Server silent installation.
| Option | Parameters | Description |
| /I | {package} | Installs the product. |
| /q | {n|b|r|f} | Sets user interface level.
qn - No user interface. qb - Basic user interface. qr - Reduced user interface with a modal dialog box displayed at the end of the installation. qf - Full user interface with a modal dialog box displayed at the end of the installation. |
| /L | [i][w][e][a][r][u][c][m][p][v][*] | Specifies the path to the log file. The following flags indicate which information to log:
i - Status messages w - Nonfatal warnings e - All error messages a - Startup of actions r - Action-specific records u - User requests c - Initial user interface parameters m - Out-of-memory p - Terminal properties v – Verbose output * - All |
For more information about Windows 2000 command line options, see the Windows 2000 Server online documentation.
For example, to perform a Web Server installation, type INSTALLLEVEL=100.
CS_ADMIN_SERVER = <SQL Server computer name>: Use this command if the SQL Server is remote
CS_ADMIN_UID = <user ID>
CS_ADMIN_PASSWORD = <password>
CS_DML_UID = <user ID>
CS_DML_PASSWORD = <password>
CS_DML_NTLM
CS_ADMIN_NTLM
Following are the commands to add individual features:
After initial installation, ADD can be replaced by DEL in any of the above entries to remove the corresponding feature.
Notes Removing parent features results in the children features being removed. For example, deleting the parent CORE feature removes its children features, such as PREDICTOR and DIRECT_MAILER.
If you want to install only the runtime objects (ADD_RUNTIME_OBJECTS), you must also specify the parent ADD_CORE feature.
<resource abbreviation>_SERVICE_UID=<user ID>
<resource abbreviation>_SERVICE_PWD=<password>
<resource abbreviation>_SERVICE_DOM=<NT domain>
where <resource abbreviation> is:
Sample Silent Installation Command
The following is a sample command for a silent Complete installation, which installs all of the services. To customize this sample for your own use, replace <XXX> with information specific for your installation:
echo off
echo [INFO] SetupTst Start
if not exist setuplogs mkdir setuplogs
REM -- Complete Install
set InstallMode=i
set DropLoc=\\<XXX>\Microsoft Commerce Server 2002.Msi
set InstallLevel=200
set SERVICE_UID=XXX>
set SERVICE_PWD=<XXX>
set SERVICE_DOM=<XXX>
set SQL_ADMIN_UID=<XXX>
set SQL_ADMIN_PWD=<XXX>
set SQL_DML_UID=<XXX>
set SQL_DML_PWD=<XXX>
set PIDKEY=<XXXXXXXXXXXXXXXXXXXXXXXX>
Caution Do not cut and paste the following sample code. It contains breaks that may not work in your installation.
msiexec /%InstallMode% "%DropLoc%" /qb /l*v setuplogs\msiproduct.log
INSTALLLEVEL=%InstallLevel% ALL_SERVICE_UID=%SERVICE_UID%
ALL_SERVICE_PWD=%SERVICE_PWD% ALL_SERVICE_DOM=%SERVICE_DOM%
CS_ADMIN_SERVER=%COMPUTERNAME% CS_DML_SERVER=%COMPUTERNAME%
CS_ADMIN_UID=%SQL_ADMIN_UID% CS_ADMIN_PASSWORD="%SQL_ADMIN_PWD%"
CS_DML_UID=%SQL_DML_UID% CS_DML_PASSWORD="%SQL_DML_PWD%"
PIDKEY=%PIDKEY%
echo [INFO] SetupTst Done.Commerce Server 2002 uses the Windows Installer for Setup. However, it does not support the Administrative Installation feature (/a command line parameter) of Installer.
As an alternative to using the Administrative Installation feature for Commerce Server 2002 Setup, you can copy the entire Commerce Server 2002 CD-ROM to a shared folder, using Windows Explorer. Then you can run Setup on remote computers. The installation files on the CD-ROM are not compressed and no additional procedures are required.
After you have installed Commerce Server 2002 on at least one computer, you can also set up an "administration-only" console on a separate computer. An administration-only computer includes only Commerce Server Manager, and it connects to the existing Administration database.
You may want to use an administration-only computer if:
To install Administration Tools
To enable administration through a proxy server or firewall
To install Administration Tools
Note Internet Information Services (IIS) must be installed on the computer you have selected to be administration-only.
Note If you are installing the Administration Tools on a Japanese version of Windows XP, an error message may appear. You can safely skip this message to complete installation.
| Use this | To do this |
| SQL Server computer | Type the name of the SQL Server on which you want to create the Administration database. |
| SQL user name | Type a SQL Server login user name that has permissions on the SQL Server on which the Administration database is to be created. |
| SQL password | Type the SQL Server login password. |
Commerce Server Manager is installed on your computer.
Note If you use the administration-only computer to unpack a site that contains Data Warehouse resources, you must manually run the Configuration Synchronization Data Transformation Services (DTS) task from the Data Warehouse computer.
To enable administration through a proxy server or firewall
By default, SQL Server listens on port 1433. For instructions about changing the port number, see SQL Server Books Online.
Notes Although you can use Commerce Server Manager through a proxy or firewall, you cannot use the Internet Services Manager feature of Microsoft Internet Information Services (IIS) 5.0 through a proxy or firewall. To add IIS administration capability to an administration-only computer located on the far side of a firewall, you can use the browser-based IIS or Microsoft Terminal Services.
For more information about using IIS, see the IIS 5.0 documentation. For information about using Microsoft Terminal Services, see "Client Services" in the Windows 2000 documentation.
You can install Commerce Server 2002 Help without installing the rest of the product.
To install Commerce Server 2002 Help only
To uninstall Commerce Server 2002 and all of its components, you must perform the following steps in the order shown. For instructions about uninstalling individual components, such as a site, resource, Web server, or application, see "Administering Commerce Server" in Commerce Server 2002 Help.
After performing these steps, it is recommended that you restart your computer.
The following procedures provide detailed instructions for performing each of these steps.
Step 1: Remove the Commerce Server Solution Sites
Step 2: Remove the Commerce Server 2002 platform
Step 3: Delete the Commerce Server 2002 installation folder
Step 4: Delete the Commerce Server 2002 databases
Step 5: Delete the Commerce Server 2002 Analysis server databases
Step 6: Delete the Commerce Server 2002 site virtual directories
Step 7: Delete the ISAPI filter (CSAuthFilter) from IIS
Step 8: Delete the Commerce Server 2002 site folders and files
Step 9: Delete the Direct Mailer jobs in SQL Server
Step 1: Remove the Commerce Server Solution Sites
Step 2: Remove the Commerce Server 2002 platform
Step 3: Delete the Commerce Server 2002 installation folder
Step 4: Delete the Commerce Server 2002 databases
Note In SQL Server Enterprise Manager, make sure that SQL Server is running (the icon in the Enterprise Manager window displays a green light). If it is not running, right-click the name of the SQL Server computer, and then click Start.
Step 5: Delete the Commerce Server 2002 Analysis server databases
Step 6: Delete the Commerce Server 2002 site virtual directories
Step 7: Delete the ISAPI filter (CSAuthFilter) from IIS
Step 8: Delete the Commerce Server 2002 site folders and files
Step 9: Delete the Direct Mailer jobs in SQL Server
After uninstalling Commerce Server 2002, it is recommended that you restart your computer.
To uninstall the Commerce Server Business Desk client
The Business Desk client is now removed from your computer.
When you install Commerce Server, the Windows Installer creates a log file called CS2ksetup.log. If you are familiar with Windows Installer, you can read the log file and see if any errors occurred during the installation process. The log file is located in Documents and Settings\<username>\Local Settings\Temp, where username is the account you used to install Commerce Server.
For more information about Windows Installer see http://go.microsoft.com/fwlink/?LinkID=14451.
This section describes problems you might encounter while installing or uninstalling Commerce Server 2002 and offers possible solutions. Possible problems include the following:
For troubleshooting information about packaging and unpacking a Commerce Server 2002 Solution Site, see "Troubleshooting Site Packager" in Commerce Server 2002 Help.
After you install Commerce Server, you may notice the following error message in the CS2Ksetup.log file:
“DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
You must restart your system for the configuration changes made to Microsoft Commerce Server 2002 Enterprise Edition to take effect. Click Yes to restart now or No if you plan to manually restart later.”
This is a benign error message that you can safely ignore. You do not need to restart Commerce Server.
The recent security patch, “Unchecked Buffer in Gopher Protocol Handle” (at http://go.microsoft.com/FWLink/?LinkID=13085) for Microsoft Internet Explorer may cause a Commerce Server Business Desk application error.
For more information, see the Microsoft Knowledge Base article number Q328780 "MS02-047 causes Commerce Server Business Desk application error," at http://go.microsoft.com/FWLink/?LinkID=9693.
After you install Microsoft Visual Studio 6.0 Service Pack 4, you cannot access Business Desk or your applications. You may get the following message: "An error occurred while creating object g_MSCSAdminEventLog."
After you install Visual Studio 6.0 Service Pack 4, change the permissions on the \winnt\system32\msvbvm60.dll file to "Everyone."
After installing Commerce Server 2002, the following message appears: "The dynamic-link library Mscsresource.DLL could not be found in the specified path."
Restart your computer.
When running the Commerce Server 2002 Setup, you receive the error that the system cannot locate the Msmdarch.exe program on the server. The OLAP cubes will not be created.
Click Skip to choose to not install the Data Warehouse at this time. After you install Commerce Server, refer to Installing SQL Server Analysis Services Service Pack 3 to verify that your Analysis Services installation is correct, and then install the Data Warehouse.
The Administration database (MSCS_Admin) configuration screen displays an error message beginning with "Execution of the TSQL command,..." and you cannot proceed.
If you have uninstalled and reinstalled Commerce Server 2002 and cannot save Direct Mailer jobs, you may need to first delete the old Direct Mailer jobs. If you have tried to add new Direct Mailer jobs and you still have old jobs scheduled, you may receive "Job Step" error messages. These messages appear when you try to save the new Direct Mailer job.
Delete any scheduled Direct Mailer jobs from SQL Server.
To delete the Direct Mailer jobs in SQL Server
When you install the Predictor resource, you receive an error message that states: "The application failed to initialize properly (0xc0000022). Click on OK to terminate."
Verify that the account you are using for the Predictor resource has adequate privileges so that the Predictor resource can log on as a service. Do not use a GUEST account.
You may need to roll back to a previous Administration database or create a new one, but you cannot reinstall Commerce Server 2002. Running Commerce Server 2002 Setup in Repair mode does not accomplish this either.
Create a new Administration database named MSCS_Admin and then run the admin_schema.sql script on it with SQL Query Analyzer. A new Administration database is created. When you run the script, the schema of the Administration database is populated but no resources are created.
To create a new Administration database
To run the admin_schema.sql script from SQL Query Analyzer
To create a new Administration database
Your new database is created. Run the admin_schema.sql script.
To run the admin_schema.sql script from SQL Query Analyzer
You will need to unpack your sites again and reinstall Direct Mailer and the Predictor resource using Commerce Server Setup.
If you do not delete the Analysis server databases before you re-install Commerce Server 2002, you will get the following error:
The OLAP database <database name> may be in use by some other site, using this database might potentially break the reports for that site. Do you want to continue?
You must delete the Commerce Server Analysis server databases before you re-install Commerce Server 2002. Perform a complete uninstallation of Commerce Server 2002. Follow the uninstallation instructions in Uninstalling Commerce Server.
For testing purposes, you attempt to initialize a blank database with the Data Warehouse schema. This is not a supported scenario.
If Analysis Services is installed on a system after Microsoft Office XP has been installed, OLAP-based PivotTables in Excel XP are no longer able to communicate with Analysis Services. When you unpack a site, your test connection to the OLAP server fails on the Data Warehouse setup screen.
Run the Office XP or Office XP Web Components installation with the Detect and Repair error option. For more information about connection failures to Analysis Services 2000 when Office XP is installed, see Microsoft Knowledge Base article Q292295, located at http://go.microsoft.com/FWLink/?LinkID=9905.
If you install Commerce Server 2002 on a computer on which Microsoft® BizTalk® Server is installed, the following error messages appear and are logged in the Event Viewer. The error messages in the event log are safe to ignore.
| Source | EventID | Description |
| Service Control Manager | 7022 | The Commerce Server Predictor service stopped responding. |
| MsiInstaller | 1004 | Detection of product '{E39DA45E-B0E6-412D-BEDE-EFD7BC1DACA6}, feature 'fADMIN_CORE_SHARED', component '{07BE71E9-A8A0-4CE7-A761-029687C953D1}' failed |
| MsiInstaller | 1001 | Detection of product '{E39DA45E-B0E6-412D-BEDE-EFD7BC1DACA6}, feature 'fADMIN_CORE_SHARED' failed during request for component '{53A7DE7D-1340-43630BEEC-6E5A89DF5909}' |
There is a known mapped drive letter problem with Windows 2000 Terminal Server. If you install Commerce Server 2002 through Terminal Server on a cluster, an error message appears.
Connect to the share by using the Universal Naming Convention (UNC) path using the following syntax, and then start the installation:
\\servername\share
Note If you log onto the console, you do not receive the error message, even if the share is mapped to a network drive.
For information about problems installing on Windows 2000 Terminal Server, see Microsoft Knowledge Base article Q255582, located at http://go.microsoft.com/FWLink/?LinkID=9906.
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, people and events depicted herein are fictitious and no association with any real company, organization, product, person 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, Active Directory, ActiveX, BizTalk, FrontPage, MSDN, PivotTable, Visual Basic, Visual Studio, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Copyright © 2002-2003 Microsoft Corporation. All rights reserved