This document provides guidelines for hardware and software requirements, and instructions for installing Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) on a single computer.
These instructions are intended for use in single-computer installations and do not include information about securing Commerce Server 2002 FP1 services during installation. For information and examples for installing Commerce Server 2002 FP1 in a secure multi-computer configuration, download the Secure Deployment Guide from http://go.microsoft.com/fwlink/?LinkId=28329.
You can add Commerce Server 2002 Feature Pack 1 (FP1) to the following editions of Commerce Server 2002:
We strongly recommend that you read this document before installing Commerce Server 2002 FP1.
This section contains:
This section lists the minimum hardware requirements for the following:
Note Actual requirements will vary based on your system configuration and the applications and features you choose to install.
The minimum hardware requirements for a Commerce Server 2002 Feature Pack 1 (FP1) 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 your business applications are:
This section lists the minimum software requirements for the following:
Install the following prerequisite software on the computer that will run Commerce Server 2002 Feature Pack 1 (FP1):
Important You must install the following software in the order listed.
OR
Windows 2000 Server or Windows 2000 Advanced Server.
Format the partition with the NTFS file system. You must install Commerce Server 2002 FP1 to an NTFS volume; however, not every volume on your computer must be NTFS. If the existing partition is file allocation table (FAT) or FAT32, you have the option to convert to NTFS. When prompted, select NTFS.
Note Commerce Server 2002 Feature Pack 1 does not run on Commerce Server 2002 Developer Edition when the operating system is Windows 2000 Professional.
The Commerce Profile services continually retrieve data from the SQL database. The SQL OLE DB provider allocates large contiguous blocks on demand to perform these operations. These allocations are performed in the virtual memory address space of the IIS process. If this process is approaching the process limit for virtual memory, errors will occur.
Important After you install Windows 2000 Server, you must configure Microsoft Information Services (IIS) 5.0 to prevent each process from using the available virtual memory, and to optimize IIS. For recommendations to optimize IIS 5.0, see Microsoft Knowledge Base article number Q322816, available at http://go.microsoft.com/fwlink/?LinkId=44252.
OR
Windows XP Professional
Note You can install Commerce Server 2002 FP1 Help on any computer that is running Windows 2000 Professional, Windows XP Professional, Windows 2000 Server, or Windows Server 2003.
Windows 2000 Server critical updates. To install all Windows 2000 critical updates, go to http://go.microsoft.com/fwlink/?LinkId=16855.
Run the SQL Server 2000 Setup program using the Custom option, and on the Select Components page, in the Sub-Components box, select Full-Text Search.
Important Before you continue with the Commerce Server 2002 FP1 installation, you must restart the computer.
Important You must install Application Center before installing Commerce Server 2002 FP1, so that you can install the Application Center staging drivers for the Commerce Server 2002 FP1 resources. If you install Application Center after Commerce Server 2002 FP1, you can add the staging drivers by using the Add/Remove Programs option in Control Panel to change your Commerce Server 2002 FP1 installation.
Important If you want to install the Promotion Code Generator, which is required for coupon discounts, you must install Message Queuing (also known as MSMQ) on you your Domain Controller. You cannot install Message Queuing on a server until you join the server to the domain.
Commerce Server 2002 Feature Pack 1 (FP1) includes two Business Management applications, Catalog Manager and Discount Manager, which have dependencies on the following Web services:
Security If you use the Web services over the Internet, you must disable Integrated authentication and use Basic authentication in conjunction with Secure Sockets Layer (SSL). Basic authentication without SSL is not supported.
Following is the prerequisite software for the Commerce Server 2002 FP1 Business Management applications.
Note Commerce Server Business Desk remains a requirement for managing user profiles, designing catalog definitions, creating ads and direct mail, and managing your order system.
Important You must install the following software in the order listed.
You use the Authorization Manager user interface to add business users to the Catalog and Marketing Authorization policy roles. You must install either Windows XP and the Windows Server 2003 Administration Pack or you can use Windows Server 2003 to access the Authorization Manager user interface.
To use the Authorization Manager user interface on the Windows XP operating system, go to http://go.microsoft.com/fwlink/?LinkId=28442 to download the Windows Server 2003 Administration Pack.
Note Windows Server 2000 and Windows Advanced Server 2000 are supported operating systems for Commerce Server 2002 FP1. However, they do not include a user interface for Authorization Manager.
Before you install Microsoft® Commerce Server 2002 Feature Pack 1 (FP1), you must have first installed Commerce Server 2002 Service Pack 2 and several other applications. For a complete list of the required software and the order of installation, see Software Requirements.
Commerce Server 2002 FP1 provides new add-on features to Commerce Server 2002 Catalogs and Discounts. When you install Commerce Server 2002 FP1, you can choose to install only the Catalog add-on features or both the Catalog and Discount features. For information about migrating these features after you install Commerce Server 2002 FP1, see "Migrating to Feature Pack 1" in Commerce Server 2002 FP1 Help.
Security For information and examples for installing Commerce Server 2002 FP1 in a secure multi-computer configuration, download the Secure Deployment Guide from http://go.microsoft.com/fwlink/?LinkId=28329.
The following procedures describe how to install Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) on one computer. You must close all other applications before proceeding.
Important Set up a secure service account to install Commerce Server 2002 FP1.
After you install Commerce Server 2002 FP1, see the Post-Installation Requirements. We strongly recommend that you perform each step in the Post-Installation Requirements section to complete a successful Commerce Server 2002 FP1 installation.
International You must install your Commerce Server 2002 FP1 installation in the same language as your Commerce Server 2002 Service Pack 2 (SP2) installation. For example, you must install a Commerce Server 2002 FP1 Japanese (JA) installation on a Commerce Server 2002 SP2 Japanese (JA) installation.
This section contains:
Installing the Business Management applications is a separate step performed after you install Commerce Server 2002 Feature Pack 1 (FP1) and the unpack FP1 Pup pack (FP1.pup). For instructions about how to unpack FP1.pup, see Unpacking the FP1 Pup package.
Note Commerce Server 2002 FP1 uses Windows authentication to access the SQL Server databases that are created while the Setup program is running.
If you plan to install Commerce Server 2002 FP1 and SQL Server on two different computers, and you plan to use local user and group accounts, the same user account and same group account names must be used on both the local and the remote computers.
To install Commerce Server 2002 FP1 on one computer
Note The identity that is provided for the Promotion Code Generator COM+ service must be an Administrator to have access to the Promotion Code Generator public and private message queues. By default, only Administrators have this access. After installation, permissions can be granted to a specific user. You cannot do this before installation because the message queues do not exist until after installation.
The Installing Commerce Server 2002 Feature Pack 1 page appears, informing you that the selected program features are being installed.
After you install Microsoft® Commerce Server 2002 Feature Pack 1 (FP1), to use the new Commerce Server 2002 FP1 features, you must follow these steps in the order listed:
Important If you have extended your Commerce Server 2002 Business Desk or if you are installing Commerce Server FP1 on a Microsoft Solution for Internet Business (MSIB) installation, you must perform the steps in this procedure to replace your Business Desk modules.
Commerce Server 2002 Feature Pack 1 (FP1) provides an FP1 Pup package, which includes the Commerce Server 2002 Feature Pack 1 Web services (Marketing Web service and Catalog Web service). The FP1 Pup package also includes the new Marketing resource.
If you are only updating the Catalog resource, you must perform a Custom unpack to add the Catalog Web service to your existing site. If you are adding the Marketing resource, which includes the promotion code functionality for public, private, and restricted promotion codes, you must perform a Custom unpack to add the Marketing and Catalog Web services to your existing site.
For more information about unpacking a site, see "Using Site Packager" in Commerce Server 2002 Feature Pack 1 (FP1) Help. You can run Site Packager from the Start menu, from Commerce Server Manager, or from the command line.
The following instructions explain how to unpack the FP1 Pup package on one computer using the Custom unpack mode in Site Packager. Before you unpack the FP1 Pup package, note the following:
Caution Do not unpack the Web services applications to the root folder.
Note This Commerce Server 2002 FP1 release does not support managing the Marketing or Catalog Web services using multiple localized versions of the Business Management applications (Discount Manager and Catalog Manager) on a single computer. To manage the Marketing and Catalog Web services with multiple localized versions of the Business Management applications, you must install the different localized versions on multiple computers.
Commerce Server Site Packager starts.
The Unpacking is complete dialog box appears. The Marketing resource is added to the specified existing site.
To add the Marketing and Catalog Web services
Commerce Server Site Packager starts.
The Unpacking is complete dialog box appears.
The following applications are created:
Note To access Commerce Server Business Desk for the site, which is required for managing user profiles, designing catalog definitions, and managing ads and direct mail, you must continue to use the Business Desk client.
To verify the Web services are installed
After you install Commerce Server 2002 Feature Pack 1 (FP1), you must migrate your catalog and discount data. To migrate your data, Commerce Server 2002 FP1 provides a set of migration tools (CatalogMigrationTool.exe and DiscountMigrationTool.exe). For information about how to migrate your systems, see "Migrating to Feature Pack 1" in Commerce Server 2002 FP1 Help.
Important If you do not migrate your catalog data, your business users will not be able to access the Catalog Manager Business Management application. If the catalog schema is not updated from Commerce Server 2002, the business user will receive an error message stating that the Web service is unavailable. The Web service may appear accessible through Internet Explorer using the Catalog Web service URL (http://<Server name>/catalogwebservice/catalogwebservice.asmx); however, it will not be functional. A schema mismatch error appears in the event log of the Event Viewer.
If you are migrating an existing Commerce Server 2002 site to Commerce Server 2002 FP1, and your catalogs contain the same property as product and variant identifying properties, it is recommended that you change the variant identifying property to a different property. For information about how to change the variant identifying property, see "Migrating display name and variant identifying properties" in Commerce Server 2002 FP1 Help.
Note It is strongly recommended that you backup your databases before you migrate your data. When you migrate a resource, any customizations that were made to the Commerce Server 2002 Service Pack 2 resource schemas will be lost, or not propagated to the new resource.
After you migrate your catalog and discount data, verify that the migration was successful by checking the CatalogMigrationTool.log in the current working folder.
The Catalog and Marketing authorization policies have a number of predefined authorization policy roles to which you can add your business users. You must perform this step before your business users can access the Catalog or Discount Managers. For information about adding the business users to the Authorization policies, see "Assigning Users Access to the Web Service Authorization Manager Policy" in Commerce Server 2002 FP1 Help.
Note Before you assign user access to the Authorization Manager policy, it is strongly recommended that you assign the user to a Windows group, and then give the Windows group Authorization Manager permissions on both Web services.
The Internet Information Services (IIS) worker process is determined by the application pool to which the Web service application belongs. You must assign the following permissions to the appropriate Catalog or Marketing Web service IIS worker process account:
Marketing Web service
Catalog Web service
Marketing and Catalog Web services
Warning If your Web server and database are on separate computers, you must configure the IIS worker process to run under a domain account or use identical local accounts with password synchronization on the servers running IIS and SQL Server.
You must add the IIS worker process account to the mktg_marketingService_role in the <site name>_commerce database.
To assign the IIS worker process account to the mktg_marketingService_role
The mktg_marketingService_role is assigned to the IIS worker process account.
If you are using Windows authentication for the Catalog resource, you must add the IIS worker process running the Catalog Web service to the db_owner role in the database that contains your catalog data.
To assign database db_owner permissions to the ASPNET account
db_owner permissions are assigned to the appropriate IIS worker process account.
If you are using Windows authentication for the Catalog resource, you must add the IIS worker process running the Catalog Web service to the db_ddladmin, db_datawriter, and db_datareader roles in the MSCS_CatalogScratch database.
To assign database db_ddladmin permissions to the ASPNET account
db_ddladmin permissions are assigned to the appropriate IIS worker process account.
Repeat steps 4 and 5 to add the IIS worker process to the db_datawriter and db_datareader roles.
After you unpack the Catalog and Marketing Web services applications, the authorization policies are extracted as the CatalogAuthorizationStore.xml and the MarketingAZPolicy.xml, respectively. To update the catalog scopes in the policies dynamically (for example, when the user creates or deletes a catalog), you must assign the ASP.NET worker process write access to the CatalogAuthorizationStore.xml file.
To assign write permissions to the Authorization Manager policy
Write access to the Catalog Web services authorization policy is assigned to the appropriate IIS worker process account.
You must grant read access to the MSCS_Admin database for the account on which your ASP.NET process is running.
To assign read access to the MSCS_Admin database
Read access is assigned to the appropriate IIS worker process account.
In a Web farm deployment, the CatalogWebService authorization file must reside in a single location accessible to all servers in the Web farm. Individual copies of the authorization file cannot be deployed on each server in the Web farm. If you have a single-computer site, the policy is packaged with the site.
To set the authorization file location
The COM+ QC component for the Promotion Code (Coupon) Generator does not automatically start on a system restart. To start the Promotion Code Generator, you must run the following script or use the Component Services Microsoft Management Console (MMC).
To start the Promotion Code Generator using a script
To start the Promotion Code Generator using the MMC
To start the Promotion Code Generator using a script
Note We recommend that you create a scheduled task using Windows Task Scheduler or a similar service to start the Promotion Code Generator after each system restart.
On Error Resume Next
Dim objCatalog
Err.Clear
Set objCatalog = CreateObject("COMAdmin.COMAdminCatalog")
If Err.Number <> 0 Then
MsgBox "An error occured when creating the COM+ Catalog. Error # 0x" & Hex(Err.Number) & vbNewLine & Err.Description
Else
objCatalog.StartApplication("Commerce Server PromoCodeGenerator")
if Err.Number <> 0 Then
MsgBox "An error occured when starting the PromoCodeGenerator. Error # 0x" & Hex(Err.Number) & vbNewLine & Err.Description
Else
MsgBox "The PromoCodeGenerator started successfully."
End If
End If
Set objCatalog = Nothing
To start the Promotion Code Generator using the Component Services MMC
The Promotion Code Generator is starts.
After you install and configure Commerce Server 2002 Feature Pack 1 (FP1) and unpack the FP1 pup file, you install the Commerce Server 2002 FP1 Business Management applications. Installing the Business Management applications installs the Discount and Catalog Manager user interfaces, which enables your business user to manage your discounts and product catalogs. For information about the Discount Manager, see "Managing Discounts Using the Marketing Web Service" in Commerce Server 2002 FP1 Help. For information about the Catalog Manager, see "Managing Catalogs" in Commerce Server 2002 FP1 Help.
To install the Discount Manager user interface
You can now start the Discount Manager.
To install the Catalog Manager user interface
You can now start the Catalog Manager.
| Use this | To do this |
|---|---|
| Site Name | Select the site from the drop-down list.
The site and reference information are stored in the DiscountManagerConfig.xml file. Each user has a unique set of connection information relating to the login ID of the user. The user-based configuration details are stored under those connection details. |
| CampaignURL | Type the URL for your connection to the Marketing Web service (for example, type http://<server name>/MarketingWebService/MarketingWebService.asmx). |
| CatalogURL | Type the URL for your connection to the Catalog Web service (for example, type http://<server name>/CatalogWebService/CatalogWebService.asmx). |
The Microsoft Commerce Server Discount Manager appears. For information about using the Discount Manager, see "Managing Discounts using the Discount Manager" in Commerce Server 2002 FP1 Help.
| Use this | To do this |
|---|---|
| Site Name | Select the site from the drop-down list.
The site and reference information are stored in the CatalogManagerConfig.xml file. Each user has a unique set of connection information relating to the login ID of the user. The user-based configuration details are stored under those connection details. |
| CatalogURL | Type the URL for your connection to the Catalog Web service (for example, type http://<server name>/CatalogWebService/CatalogWebService.asmx). |
The Microsoft Commerce Server Catalog Manager appears. For information about using the Catalog Manager, see "Using the Catalog Manager" in Commerce Server 2002 FP1 Help.
After you install Commerce Server 2002 Feature Pack 1 (FP1), you must perform the following steps to remove the Commerce Server 2002 Business Desk modules that have been replaced in Commerce Server FP1.
Perform the following steps to update your Commerce Server 2002 Business Desk modules:
Important If you have extended your Commerce Server 2002 Business Desk or if you are installing Commerce Server FP1 on a Microsoft Solution for Internet Business (MSIB) installation, you must follow these steps to replace your Business Desk modules.
Note If you have not extended your Business Desk, or are not installing Commerce Server FP1 on MSIB, you only have to perform Step 2 in the following procedures.
Note Additionally, to back up the BizDesk.xml file, if you have extended your Commerce Server 2002 Business Desk, backup any files that you do not want replaced by the new Commerce Server FP1 Business Desk updates.
<config xmlns="x-schema:bdconfig-schema.xml"> <moduleconfigs>
Remove the following line:
<moduleconfig id="catalogs_editor.xml" category="catalogs"/>
The Catalog and CatalogAndDiscounts folders are located in the Commerce Server 2002 FP1 installation location (for example, <drive>:\Program Files\Microsoft Commerce Server 2002\FP1\BizDesk).
If you added the Marketing resource when you unpacked a Commerce Server Feature Pack 1 (FP1) site, you must edit the Web.config file to change from the Campaigns resource to the new Marketing resource.
To modify the Web.config file for the runtime site
Your Commerce Server 2002 discounts will now use the MarketingDiscount cache type.
Before moving your retail Web site to a production environment, you should modify the Web.config file to update the debug compilation mode. Running your site in debug mode may result in performance degradation.
After installing Commerce Server 2002 Feature Pack 1 (FP1), your site developer must perform several steps to implement the following:
To take advantage of the new promotion code feature in Commerce Server 2002 FP1, your site developer must perform several steps to implement the promotion codes. (Promotion codes are also referred to as coupons). For information about implementing promotion codes, see "Implementing Promotion Codes" in the Developer's Guide in Commerce Server 2002 FP1 Help.
To export a Boolean property in UPM DWA, you must merge the changes from the new FP1 profiledesigner.htc file to your current profiledesigner.htc file or manually update the profiledesigner.htc file.
To merge the changes from the new FP1 profiledesigner.htc
To manually update the profiledesigner.htc file
To merge the changes from the new FP1 profiledesigner.htc
To manually update the profiledesigner.htc file
Change:
Not (m_divPropertyAttrs.field("isMultiValued").value = "1")
To:
(m_divPropertyAttrs.field("isMultiValued").value = "1"))
You must configure your computers and set the appropriate security permissions for Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) staging. Following is the required four-computer configuration when using Integrated Authentication to SQL Server.
Source Computers
Destination Computers
The following table lists the computer configurations that you must have for Commerce Server 2002 FP1 staging.
| Source and Destination Computers | Minimum Configuration Requirements |
|---|---|
| Source SQL Computer 1 |
|
| Destination SQL Computer 2 |
|
Security Permissions
The following table lists the permissions you must set on the source databases.
| Source database | Permissions specified for the SourceACControllerComputerName$ account |
|---|---|
| Commerce Server runtime databases |
|
| MSCS_Admin database |
|
| Stored procedures in the Commerce Server runtime and MSCS_Admin databases |
|
The following table lists the permissions you must set on the destination databases.
| Destination database | Permissions specified for the DestinationACControllerComputer$ account |
|---|---|
| Commerce Server runtime databases |
|
| MSCS_Admin database |
|
| Stored procedures in the Commerce Server runtime and MSCS_Admin databases |
|
Changing the Web.config file
Edit the Web.config file on each Web server in the Commerce Server site, and add the "authorization" element under the "systWebweb" element. Add a child element named "allow" with an attribute named "users" to the authorization element. Set the child element equal to the account <domain name>\<ACDestinationClusterControllerComputerName>$.
The following is an example of the revised Web.config file:
<system.web>
....
<authorization>
<allow users=contoso\csd203$/>
</authorization>
....
</system.web>
Configuring IIS to use Kerberos
You must configure Internet Information Services (IIS) to use Kerberos as stated in Microsoft Knowledge Base article 215383, "HOW TO: Configure IIS to Support Both Kerberos and NTLM Authentication." Go to http://go.microsoft.com/fwlink/?LinkId=28446.
Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) allows automated electronic software distribution, also known as silent installation. Silent installation is designed to install Commerce Server 2002 FP1 in an automated way on computers that have identical configurations. It is designed for system administrators who want to install Commerce Server 2002 FP1 on remote computers without user intervention. With a silent installation, a user does not need 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.
Note Commerce Server 2002 FP1 does not allow silent installation for clustered resources.
Note You cannot remove features using silent installation.
Before you install Commerce Server 2002 FP1 using silent installation, do the following:
This section contains:
You must follow these steps in the order listed for a successful silent installation:
Step 1. Perform a silent installation for new Commerce Server 2002 FP1 files
Step 2. Perform a silent installation to update existing Commerce Server 2002 files
Step 1. To perform a silent installation for Commerce Server 2002 FP1 new files
The following table shows the Windows 2000 command line options that you use to install new Commerce Server 2002 FP1 files.
| Command Line Option | Description |
|---|---|
| /I <Commerce Server 2002 FP1 drop location>\cs2k2fp1.msi | Required. The path of the location where the Web download was unpacked.
|
| /qb!- | Required. Ensures that you are in silent mode: does not allow pop-ups or prompts. |
| /l*v c:\fp1msi.log | Required. The log file where error and information messages are logged. |
| ADDLOCAL=ALL | Required. Features you are installing.
The following are the valid features names:
|
| PCGN_SERVICE_UID=MyUserID | The user name of the User Account used to run the Promotion Code Generator service.
Required only if fPromocode is selected. |
| PCGN_SERVICE_PWD=MySecretPassword | Required only if fPromocode is selected. |
| PCGN_SERVICE_DOM=MyDomain | Required only if fPromocode is selected. The domain name of the user account is used to run the Promotion Code Generator service. |
| REBOOT=ReallySuppress | Suppresses restart prompts at the end of the installation. |
| CSSETUP=1 | Required. Specifies that Microsoft Commerce Server 2002 is being updated. |
For more information about Windows 2000 or Windows 2003 command line options, see the Windows 2000 Server or Windows Server 2003 online documentation.
msiexec /i c:\temp\webdrop\cs2k2fp1.msi /qb!- /l*v c:\temp\fp1msi.log ADDLOCAL=ALL PCGN_SERVICE_UID=john PCGN_SERVICE_PWD=iamjohndoe PCGN_SERVICE_DOM=redmond REBOOT=ReallySuppress CSSETUP=1
Step 2. To perform a silent installation to update existing Commerce Server 2002 files
The following table shows the Windows 2000 command line options that you use to update existing Commerce Server 2002 files.
| Command Line Option | Description |
|---|---|
| /p <Commerce Server 2002 FP1 drop location>\patch.msp | Required. The path of the location where the Web download was unpacked.
|
| /qb!- | Required. Ensures that you are in silent mode: does not allow pop-ups or prompts. |
| /l*v c:\fp1patch.log | The log file where error and information messages are logged. |
| REINSTALL=ALL | Required. The password of the user account used to run the Promotion Code Generator service. |
| REINSTALLMODE=omus | Required. Must be specified exactly as shown so that all existing files are updated to their latest versions. |
| REBOOT=ReallySuppress | Suppresses restart prompts at the end of the installation. |
msiexec /p c:\temp\webdrop\patch.msp /qb!- /l*v c:\temp\fp1patch.log REINSTALL=ALL REINSTALLMODE=omus REBOOT=ReallySuppress
For more information about Windows 2000 command line options, see the Windows 2000 Server online documentation.
To uninstall Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) and all its components, you must follow these steps in the order shown. For instructions about uninstalling individual components, such as a site, resource, Web server, or application, see "Administering Commerce Server 2002 Feature Pack 1" in Commerce Server 2002 FP1 Help:
Note After performing these steps, it is recommended that you restart your computer.
If you migrated to the Commerce Server 2002 FP1 Product Catalog System, you must run a reverse catalog migration. For information about how to reverse migrate your Product Catalog System, see "Reversing Your Catalog Migration" in Commerce Server 2002 FP1 Help.
You must perform this step if you added the new Marketing Web service when you unpacked the FP1 Pup package.
If you added the Marketing resource when you unpackaged a Commerce Server FP1 site, you must delete the Marketing resource from the site. You must also edit the Web.config file to change the MarketingDiscount cache back to the Commerce Server 2002 Discount cache.
To delete the Marketing Resource
Your Commerce Server 2002 discounts will now use the Discount cache type.
Note After uninstalling Commerce Server 2002 Feature Pack 1, it is recommended that you restart your computer.
After you uninstall Commerce Server 2002 FP1, the Message Queuing Promotion Code Generator queues will still exist; you delete them.
To delete the Message Queuing queues
The Message Queuing Promotion Code Generator queues are deleted.
This section describes problems you might experience while installing or uninstalling Microsoft® Commerce Server 2002 Feature Pack 1 (FP1) and offers possible solutions. Possible problems include the following:
For troubleshooting information about packaging and unpacking the FP1 Solution Site, see "Troubleshooting Site Packager" in Commerce Server 2002 FP1 Help.
The following unpatching error may occur while uninstalling Commerce Server 2002 Feature Pack 1 (FP1).
"You may need to run the Unpatch Process Manually. Please refer to the Installation Guide for information on manually unpatching Feature Pack."
Details about the error are located in the log file where Commerce Server 2002 is installed (for example, <drive>:\Program files\Microsoft Commerce Server 2002\CS2002FP1Patch.log.)
You must manually unpatch Commerce Server 2002 FP1.
To manually remove Commerce Server 2002 FP1 from your computer
msiexec /p %webdrop%\unpatch.msp /qb!- /l*v %temp%fp1unpatch.log REINSTALL=ALL REINSTALLMODE=amus REBOOT=ReallySuppress
where %webdrop% is the location of the uncompressed installation package for Commerce Server 2002 FP1.
After installing Commerce Server 2002 Feature Pack 1 (FP1), you receive the following message: "The dynamic-link library Mscsresource.DLL could not be found in the specified path."
Restart your computer.
If you do not install Application Center before you install Commerce Server 2002 Feature Pack 1 (FP1), the system will not register the staging DLLs.
You must manually register the staging DLLs that Commerce Server 2002 FP1 Setup copies to the installation folder.
To manually register the staging DLLS
regsvr32 accscamenm.dll
regsvr32 accscatenm.dll
regsvr32 accsinvenm.dll
regsvr32 accsproenm.dll
regsvr32 accssitesenm.dll
regsvr32 accssqlenm.dll
regsvr32 rdrvcscampaign.dll
regsvr32 rdrvcscat.dll
regsvr32 rdrvcsinv.dll
regsvr32 rdrvcsprofile.dll
regsvr32 rdrvcssites.dll
regsvr32 rdrvcssql.dll
The Administration database (MSCS_Admin) configuration screen displays an error message beginning with "Execution of the TSQL command,..." and you cannot continue.
You may have to roll back to a previous Administration database or create a new one, but you cannot reinstall Commerce Server 2002 Feature Pack 1 (FP1). Running Commerce Server 2002 FP1 Setup in Repair mode does not create a new Administration database.
Create a new Administration database named MSCS_Admin and then run the admin_schema.sql script on it with SQL Query Analyzer. The system creates a new Administration database. When you run the script, the system populates the schema of the Administration database but does not create any resources.
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. You can now run the admin_schema.sql script.
To run the admin_schema.sql script from SQL Query Analyzer
You must unpack your sites again and reinstall Direct Mailer and the Predictor resource using Commerce Server Setup. For information about unpacking a site, see "Using Site Packager" in Commerce Server 2002 FP1 Help.
If you do not delete the Analysis services databases before you re-install Commerce Server 2002 Feature Pack 1 (FP1), you will receive 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 services databases before you re-install Commerce Server 2002. Perform a complete uninstallation of Commerce Server 2002. Follow the uninstallation instructions in Uninstalling Commerce Server 2002 FP1.
For testing purposes, you try to initialize a blank database with the Data Warehouse schema.
This is not a supported scenario.
If you install Analysis Services on a system after you install Microsoft Office XP, OLAP-based PivotTables® in Microsoft Excel XP will not be able to communicate with Analysis Services. When you unpack a site, your test connection to the OLAP server will fail 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, "BUG: Unable to Connect to Analysis Services 2000 When OfficeXP is Installed." Go to http://go.microsoft.com/fwlink/?LinkId=9905.
There is a known mapped drive letter problem with Windows 2000 Terminal Server. If you install Commerce Server 2002 Feature Pack 1 (FP1) through Terminal Server on a cluster, you will receive an error message.
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 on to the console, you will not receive the error message, even if the share is mapped to a network drive.
For information about Windows 2000 Terminal Server installation problems, see Microsoft Knowledge Base article Q255582, "BUG: Error Running Windows Installer Installation on Terminal Server." Go to 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, 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.
© 2005 Microsoft Corporation. All rights reserved.
Microsoft, PivotTable, Visual Basic, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries/regions.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.