Microsoft Commerce Server 2000 Readme

This readme contains important, late-breaking information about Microsoft® Commerce Server 2000.

Commerce Server 2000 Installation

Upgrading from a previous version of Commerce Server 2000

Important information about upgrading from a previous version of Commerce Server 2000 is located on the Commerce Server 2000 Evaluation page at http://www.microsoft.com/commerceserver/productinfo/evaluate.htm.

Solution Sites downloadable from the Web

The Solution Sites for Commerce Server 2000 are downloadable from the Commerce Server Web site located at http://www.microsoft.com/commerceserver/solutionsites. The Solution Sites are intended as starter sites for rapidly building e-commerce sites (Retail or Supplier portal). While the Solution Sites demonstrate a wide range of the features provided by the Commerce Server platform, not all features are built into a single Solution Site.

Commerce Server 2000 SDK

For information about the Commerce Server 2000 Software Development Kit (SDK), see the Readme_SDK.htm file located on the product CD in \Program Files\Microsoft Commerce Server or in the installation directory of Commerce Server 2000.

Known Issues

This readme contains information about the following known issues:

Analysis: Multiple Shopping Basket Events reports do not display properly

When you run multiple copies of the Shopping Basket Events report using the Analysis modules in Business Desk, the copies are opened in individual Internet Explorer windows, but they do not display any information.

Analysis: Opening dynamic SQL reports may consume large amounts of memory

Dynamic reports based on large amounts of data may consume large amounts of memory on opening. This is due to the PivotControl loading all the data into memory before displaying the report.

Analysis: Users without cookies are not identified correctly

The Business Analytics System does not correctly identify users who do not accept cookies. If cookieless shopping is enabled on your site, reports based on user type may display incorrect results. The Buyer Browse to Purchase report will not display data for users without cookies. Because all registered users without cookies are counted as guest users, the following reports may contain inaccurate numbers: Order Events, Usage Trends, and User Visit Trends. Additionally, any report or cube containing the RegisteredUser dimension is affected.

To correct this situation, a PERL script that pre-processes Web log files will be provided with the Commerce Server 2000 Resource Kit.

Business Desk: Too many concurrent users

If you open Commerce Server Business Desk several times, you may receive the message: "Too many concurrent users." To resolve this error, make sure that Transmission Control Protocol/Internet Protocol (TCP/IP) is set as the default network library to connect to the Administration database.

Data Warehouse: The interface does not support deleting all data in certain configurations

When more than one Data Warehouse is used in a Commerce Server installation, or when there is more than one site per Data Warehouse, the All option in the Select delete type list box in the Data deletion Data Transformation Services (DTS) task is disabled.

To delete all of the data in one or all of the Data Warehouses, use a script file. A script file that provides this functionality will be provided with the Commerce Server 2000 Resource Kit.

Debugging: Run SQL Profiler and DTS import tasks on separate computers

If you use Microsoft SQL Profiler for debugging, it should be run on a computer other than the computer running a Commerce Server Data Transformation Services (DTS) import task. If you run SQL Profiler and the import task on the same computer, performance may be degraded and you may have to reboot the computer.

Debugging: Stop Command inside a Scriptor does not break into Debug

If you are debugging the scriptor pipeline component (ProgID = Commerce.Scriptor) and the script engine does not break into Debug when a Stop command is encountered, Just in Time debugging may not be enabled.

To turn on dumb host Just In Time (JIT) debugging

  1. In the Registry, go to HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings.

  2. Add (or set if the key is already there) the DWORD value JITDebug = 1.

  3. Perform an IISReset.

Deployment: Supported deployment scenarios

For sites that do not require cookies, peer-to-peer and parent-child site deployment modes are supported. For sites that do require cookies, the parent-child site deployment mode is not supported.

An example of a peer-to-peer site deployment is: www.microsoft.com/msdn and www.microsoft.com/bookstore.

An example of a parent-child site deployment is: www.microsoft.com and www.microsoft.com/bookstore.

For the peer-to-peer deployment mode, an application name must not be a subset of another application name.

An example of a peer-to-peer site deployment with one application name that is a subset of the other application name is: www.microsoft.com/retail and www.microsoft.com/retail2.

Installation: Do not use localhost

When you install Microsoft Commerce Server 2000, do not use "localhost" as the computer name in the URL or when you are prompted for the SQL server name.

Installation: If OLAP is installed, an OLAP admin must install Commerce Server 2000

To install Commerce Server 2000 on a computer running Analysis (OLAP) Services, you must be a member of the OLAP (online analytical processing) administration group.

Pipelines: Access to Log Files directory is required to perform pipeline logging

To enable pipeline logging, you must set the logging flag to "on" in the Global.asa file and then grant the Everyone group read/write access to the \Inetpub\wwwroot\Pipeline\Logfiles directory.

Pipelines: Performance Monitor Counter instance is not released

When your Web site is running in Medium Isolation Mode and you restart Internet Information Services (IIS) 5.0 without first restarting Performance Monitoring, the performance monitoring counter is not released. This occurs for both pooled and non-pooled pipelines.

To release the performance monitoring counter

  1. Exit Perfmon.exe.

    You do this for both local and remote performance monitoring cases.

  2. For the remote case, stop Regsvs.exe on the computer where performance is being monitored.

  3. If you are creating performance monitoring logs or alerts, you must also stop Smlogsvc.exe

Profiles: Add TCP/IP keys for sites using Active Directory

The following Transmission Control Protocol/Internet Protocol (TCP/IP) keys need to be edited for any site using Microsoft® Active Directory™ (AD). These changes should be made to all AD servers and Web servers. The computers must be rebooted for these changes to take affect.

  1. In the Registry, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

  2. Add (or set if the key is already there) the DWORD value MaxUserPort = 0000fffe.

  3. Add (or set if the key is already there) the DWORD value TcpWindowSize = 0000ffff.

Profiles: Multi-valued properties can only map to String data types in OLE DB ANSI stores

If you map multi-valued profile properties to an OLE DB American National Standards Institute (ANSI) data store, the attributes in the data store must be of the String data type. This limitation does not apply to Lightweight Directory Access Protocol (LDAP) data stores.