Known Issues

Information about how to migrate your Commerce Server 2002 Starter Site to Commerce Server 2006 will be available at a later date.

When you use the Upgrade Wizard on an earlier version of a Commerce Server site, you may experience the following error:

<CS2006Upgrade>: Error: Exception thrown during Analyze phase of 'Transactions' component: System.Runtime.InteropServices.COMException (0x8004E024): COM+ activation failed because the activation could not be completed in the specified time. (Exception from HRESULT: 0x8004E024)

To resolve this problem, click the Back button in the Site Packager window, repeat your choice of the resources that you want to migrate, and then click Next. The operation will then continue successfully.

If you create a new profile definition or modify the name of an existing profile definition, you must update the Profiles Web Service Authorization Manager policy file before you can access the new or renamed profile definitions. Define the scope of the new or renamed profile type in the Profiles Web Service Authorization Manager policy, and assign users to the roles that have the permissions that they must have. Additionally, when you modify profile definitions, you must restart the Profiles Web Service and any site applications that use profiles. This is required because the Profile objects cache the profile definitions at application startup and do not detect the changes until after a restart.

When modifying the profile schema, realize that the display names shown in the user interface are not based on the profile definition, but are based instead on the presentation XML. The display names are intended to be localizable and the profile definition information is not. The presentation information is not tied to changes in the database. You have to make any changes in property display names (localizable or otherwise) in the presentation file.

The Profiles adapter requires the following two Date/Time properties on a custom profile definition:

• date_last_changed
  
  
• csadapter_date_last_changed
  
  

Without these properties, the Profiles adapter will not work with the custom profile definition.

When you configure the Profiles receive adapter an error occurs because the primary key of the CreditCard profile is not marked searchable.

To configure the Profiles receive adapter when you use the CreditCard profile

1. In Commerce Server Manager, expand Commerce Server Manager, expand Global Resources, expand Profile(<server name>_<site name>_profiles), expand Profile Catalog, expand Profile Definitions, and then click Credit Card.
   
   
2. In the properties pane, expand General Information, and then click Credit Card ID.
   
   
3. In the Detailed Information pane, expand Advanced Attributes, select Searchable, and then click Apply.
   
   
4. On the toolbar, click Save Profile to save the profile definition.
   
   

To configure the Profile receive adapter if you do not use the CreditCard profile

• In the BizTalk Server Administration console, when you configure the Profile receive adapter, type a complete list of profile definition names, separated by a comma. For example: UserObject, Organization, Address.
  
  

When you configure the Profiles send adapter endpoint for queries, it will only return the number of results up to the SearchResultLimit value in the Web.config file, regardless of the actual size of the query results. For example, if you set SearchResultLimit to 500 (the default value) and your query returns 1000 results, you will only see 500 results.

The Commerce Server 2006 Profiles Web Service in this release defines encrypted properties. The Profiles system cannot create profiles that require encrypted properties until you configure the Web.config file with at least one public key and KeyIndex value. The private key value is required if you need decryption. For example, credit card information is encrypted and to be able to save the information, the Profiles Web Service requires a public/private encryption key pair. Assign both private keys a value that can be the same private key or another private key generated from another run of the Profile Key Manager tool. You must use the Profile Key Manager tool to generate the key pair.

To generate the key pair

1. Open a command prompt and navigate to the <drive>:\Program Files\Microsoft Commerce Server 2006\Tools folder.
   
   
2. Type ProfileKeyManager /kn /o KeyFile.xml at the command prompt. A new key file will be created that contains a public and private key pair.
   
   
3. Edit the Profiles Web Service Web.config file. This file is typically located at C:\inetpub\wwwroot\ProfilesWebService\Web.config.
   
   

In the Profiles Web Service Web.config file, under the <profilesWebService> tag, type the public and private key generated by Profile Key Manager, by replacing the [publicKey] and [privateKey] with the entries from the generated text file as shown in the following example:

<profilesWebService

siteName="CSharpSite"

authorizationPolicyPath="ProfilesAuthorizationStore.xml"

disableAuthorization="false"

searchResultsLimit="500"

bypassProfileCache="true"

publicKey="[PublicKey]"

privateKey1="[PrivateKey]"

privateKey2="[PrivateKey]"

keyIndex="1">

Additionally, you must configure these keys in the profiles section of your Web site's Web.config as shown in the following example:

<profiles>

<encryption>

<keys keyIndex="1">

<add type="publicKey" value="[PublicKey]"/>

<add type="privateKey1" value="[PrivateKey]"/>

<add type="privateKey2" value="[PrivateKey]"/>

</keys>

</encryption>

</profiles>

The following code demonstrates the correct syntax of the Profile Key Manager config.xml file:

<?xml version="1.0" ?>

<Configuration xmlns="http://schemas.microsoft.com/CommerceServer/2006/08/ProfileKeyManagerConfiguration">

<ProfileConnectionString>Provider=CSOLEDB;Data Source=localhost;Initial Catalog=your_database_name;Integrated Security=SSPI;</ProfileConnectionString>

<ProviderConnectionString>url=mscop://InProcConnect/Server=localhost:Database= your_database_name:Catalog=Profile Definitions:Trusted_Connection=true:</ProviderConnectionString>

<BDAOConnectionString>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog= your_database_name;Data Source=localhost</BDAOConnectionString>

</Configuration>

You may experience performance problems and unexpected failures in the Catalog Manager application if you run more than one catalog export at a time. To resolve this problem, perform catalog exports sequentially.

You may experience minimal, intermittent downtime of catalog data when you perform catalog import operations on your live Web site through either Commerce Server Staging or the BizTalk Server adapters. Schedule these operations during off-peak hours to minimize disruption.

You should manually rebuild your virtual catalogs after you make any changes, for example changing your schema or catalog data. In this release, the auto-rebuild function has issues that could cause data inconsistencies.

Because of the Microsoft SQL Server™ 2000 WHERE clause limit of 4000 characters, the SQL WHERE clause in the Commerce Server Catalog and Inventory System is also limited. This causes a limit of approximately 1400 characters for a basic catalog search when inventory query data is added to the WHERE clause text.

The WHERE clause limit does not exist in Microsoft SQL Server 2005.

When you modify the MaximumStringLength value with the FreeTextSearchable property enabled, you receive the error: "Cannot alter or drop column 'column_name' because it is enabled for Full-Text Search."

To resolve this issue, do not set the MaximumStringLength for a FreeTextSearchable property where NewMaxSize is less than OldMaxSize.

When you try to import Commerce Server 2002 catalogs to Commerce Server 2006, you receive validation errors. This behavior may occur because the Commerce Server 2002 catalog XML file contains properties that are named the same as Commerce Server 2006 properties, but that contain different schema properties (sizes, and so on). Parts of the catalog file fail to import, but the valid parts succeed.

To resolve this issue, you have to create a clean version of the catalog schema. To achieve this, delete all catalogs in Catalog Manager. Then, delete all product definitions, category definitions, and all property definitions by using the Catalog and Inventory Schema Manager.

To determine whether a catalog or inventory import failed or succeeded, you must examine the response message generated by the Catalog or Inventory send adapter in BizTalk Server that is routed according to your BizTalk Server configuration. If you have configured a BizTalk Server process to consume this message, you must add code to the process to parse the message. If you have configured your BizTalk Server to route the message to a person by using e-mail, you must visually examine the contents of the message.

If the number of errors shown in the message exceeds the error threshold configured in your Catalog or Inventory send endpoint, the import was not successful. If there are fewer errors than the configured limit, the import returns a status of CatalogOperationsStatus.CompletedWithErrors.

Orders data in the Commerce Server 2002 database (for example, the transaction database) is kept in local time. After you migrate to Commerce Server 2006, the date and time fields will remain in local time in this release.

Do not migrate more than 40,000 records using the Orders Migration Tool. Doing this could lead to an Orders Migration Tool Access Violation error.

When you use the Orders adapter and have multiple Commerce Server computers that exchange order messages through the adapter, some messages could be sent multiple times between the computers. To resolve this issue, include the Status values as an additional filter for the Orders receive endpoint.

For example, if you want all new and updated orders since the last adapter run to be exported to a separate Commerce Server computer, you can configure the Orders adapter with the following options:

• Incremental Export = True
  
  
• FromStatus= New Orders, Updated Orders
  
  
• ToStatus = Submitted
  
  

This exports all orders that are new, updated, and modified by the Orders System since the last adapter run. After the export, the Orders exported Status value would be changed to "Submitted".

When you run the Total pipeline you may receive an exception that indicates "The selected shipping method is not currently available. Please choose another shipping method." This error will occur if you have not specified a shipping method for one or more line items in the order form. You specify the shipping method on a LineItem object by setting its ShippingMethodId property to a GUID representing the shipping method that you want for that line item.

When repeated Staging replication and roll back operations occur, some folders may not be automatically removed. This can result in lost folders upon the next replication and roll back operation. To resolve this issue, manually delete remaining folders after you complete a rollback operation.

The Commerce Server Staging system requires that you enable Active Server Pages (ASP) on your computer to view reports. Note that ASP is disabled by default in a new Windows Server 2003 installation. If you do not enable ASP, you will receive an HTTP 404 error in the Microsoft Management Console (MMC) window when you click the reports.

Use the Deployment Wizard to create your staging project folders instead of using existing folders. Otherwise, your staging folders may not have the appropriate ownership set. You must make sure that the authentication accounts that connect to the destination server have ownership of the project folders on the destination server.

To resolve this issue, move to the folder, right-click the folder, on the Security tab, click Advanced. On the Owner tab, in the change Owner To list, select CSSAdministrators, and then click OK.

Use an account that has CSSAdministrators group membership for your destination server authentication account. If you use the Project Creation Wizard to create the project on both source and destination servers, the authentication account must be part of CSSAdministrators group because only CSSAdministrators can create projects. Otherwise, the destination server project creation will fail.

The Commerce Server Staging (CSS) service may stop unexpectedly during replication because of incorrect permissions. You may get an error dialog box that indicates "access denied". To resolve this issue, grant the CSS_SG (CSS service group) permissions as described in the Commerce Server Secure Deployment Guide in Commerce Server 2006 Help.

Because of a problem with the Prepare Reports DTS task, you must run your Data import DTS task and then perform the following steps manually for the task to complete successfully.

If you are using SQL Server 2000, click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer. In SQL Query Analyzer window, from the drop-down list, and then select the name of your Data Warehouse database from the list (the name is CSharpSite_dw by default).

If you are using SQL Server 2005, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio. In the Microsoft SQL Server Management Studio window, click New Query. From the drop-down list, select the name of your Data Warehouse database from the list (the name is CSharpSite_dw by default).

In SQL Query Analyzer window of SQL Server 2000, or the Microsoft SQL Server Management Studio window of SQL Server 2005, run the following database commands in the order listed:

Exec CSDW_MakeUserAgentData

go

Exec CSDW_MakeMVQueryStringFactTable

go

Exec CSDW_MakeSVQueryStringFactTable

go

Exec CSDW_MakeAggRequestsByUri

go

Exec CSDW_MakeProductCategoryInfo

go

Exec CSDW_MakeSalesFactTable

go

Exec CSDW_MakeBasketEventsFactTable

go

Exec CSDW_DateFill

go

Exec csdw_spDefineOLAPPartitions

go

If you are using Microsoft SQL Server 2005, after you run the commands, in the Microsoft SQL Server Management Studio window, on the File menu, click Connect Object Explorer. In the Server Type drop-down list, select Analysis Services. After you are connected, right-click the name of your Data Warehouse database, and then click Process.

Do not unpack the Data Warehouse and other site resources to the same database. This is not a supported scenario and will cause failures because of duplicate table names used in both of these databases.

Migration of your Data Warehouse from earlier versions of Commerce Server is unsupported in this release.

Rendering the "User_Visit_Trends" report may generate a query execution error when the 'All' option is selected in the Date Range report parameter (the default) in SQL Reporting Services.

To resolve this problem, use the "Custom" value as your Date Range parameter. This populates the Start Date and End Date report parameters with the first and last dates for which data is available in the mscsWebUsage cube.

Pipeline Editor will crash if you "Cut" or "Copy" a pipeline stage that has a broken or unregistered component. Instead, you must first remove the broken component from the pipeline or fix the component so that it is registered correctly before you try to cut or copy.

The Commerce Server Business Management Applications, for example Customer and Orders Manager, Catalog Manager, and Marketing Manager, are fully supported on the Microsoft Windows®°XP Professional operating system. However, these tools are not supported on the Microsoft Windows®°XP Professional x64 Edition operating system in this release.

Some profile definitions that were included with Commerce Server 2002 and earlier versions have properties that may not display correctly in the Customer and Orders Manager user interface. These properties fall into two categories.

1. In the first category, any profile property that has a "Type Reference" that points to a site term must have its "Type" set to Site Term. If the "Type" is anything other than "Site Term", the Customer and Orders Manager will not display this property as a combo box that contains the possible site term values. Instead, only a user-editable text box will be displayed. You may still save a value for these properties, but the user interface will not be able to validate the value you have entered.
   
   
2. In the second category, any profile property that has a "Type Reference" that points to a profile must have its "Type" set to "Profile". If the "Type" is anything other than a "Profile", the Customer and Orders Manager will not display this property with a browse button that lets you search for the possible profile value. Instead, only a user-editable text box will be displayed. You may still save a value for these properties, but the user interface will not be able to validate the value you have entered.
   
   

The following is a list of profile properties from Commerce Server 2002 that are known to have these problems:

• Address.GeneralInfo.id
  
  
• Address.GeneralInfo.user_id_changed_by
  
  
• BlanketPOs.GeneralInfo.org_id
  
  
• BlanketPOs.GeneralInfo.user_id_changed_by
  
  
• Organization.GeneralInfo.user_id_admin_contact
  
  
• Organization.GeneralInfo.user_id_receiver
  
  
• Organization.GeneralInfo.user_id_changed_by
  
  
• Organization.Purchasing.user_id_purchasing_manager
  
  
• UserObject.GeneralInfo.user_type
  
  
• UserObject.GeneralInfo.user_id_changed_by
  
  
• UserObject.AccountInfo.org_id
  
  
• UserObject.AccountInfo.account_status
  
  
• UserObject.BusinessDesk.partner_desk_role
  
  

Note   New sites created by using the Commerce Server 2006 PUP packages are not affected.

In the Marketing Manager user interface, in the Reference Tables for the Page Groups, Content Sizes, and Industry ID screens, do not click Add to add more rows. To add a new row, click your mouse in the data grid, and then type the new value.

The Commerce Server 2006 API documentation incorrectly states that the target Commerce Server 2006 development platform is Microsoft Windows XP Service Pack 2. The correct platform is Windows Server 2003 Service Pack 1 Standard and Enterprise Editions.

When you use the Commerce Server Project Creation Wizard in Visual Studio, you may experience the following issues:

1. If you have already installed the Web services on another site, you must use the Custom Unpack option in Commerce Server Site Packager and provide a unique Application and Virtual Directory name on the Select IIS Computers, Web Sites, and Paths page of the Commerce Server Site Packager Wizard.
   
   
2. If you use the Custom Unpack option in Commerce Server Site Packager, you must change the Commerce Application Name and Virtual Directory Path on "EmptySite" to be the same as the site name that you entered in Visual Studio.
   
   
3. Do not click Back on the first screen of the Commerce Server Site Packager wizard and select a different PUP package. If you click Back and select a different PUP package, naming problems will occur.
   
   

If you do not follow the previous steps, the following error will occur:

"AuthManager(CommerceServer): Error reading Commerce Server administration database. Check the AddressKeyName setting in the CSApp.ini file for the site and ensure that it refers to the name of a Commerce Server application that exists for the site. Site name: 'WebSite1' Application name: 'WebSite1' Auth resource property: 's_SecureHostname' HRESULT: 0x800A0CC1"

This error occurs because of a mismatch in the Commerce Application Name/Virtual Directory Path and the virtual directory created by Visual Studio. To resolve this problem, run the Project Creation Wizard again and follow the Custom Unpack steps described in this topic.

The Business Management Application help is functional. However, the following Commerce Server applications do not yet have user interface help available:

• Commerce Server Manager
  
  
• Configuration Wizard
  
  
• Data Warehouse Import Wizard
  
  
• Language Selection Tool
  
  
• Pipeline Component Registration Tool
  
  
• Pipeline Components
  
  
• Pipeline Editor
  
  
• Site Packager
  
  
• Upgrade Wizard
  
  

--------------------------------------------------------------------------------------------------

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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, BizTalk, MSDN, MS-DOS, Visual Basic, Visual C#, Visual Studio, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.