Known Issues

By default, when you first open the documentation in the Microsoft Visual Studio® 2005 interface, the SQL Server 2005 technology table of contents filter is enabled and hides the Commerce Server 2007 node. In the Visual Studio 2005 Document Explorer window, in the left pane, click the Filtered by drop-down box. Then, click unfiltered to display all available table of contents nodes. These include the Commerce Server 2007 node.

In the Commerce Server 2007 .NET Class Reference, links to Web methods do not function. Instead of using the .NET Class Reference, you can view Web methods in the Visual Studio 2005 Object Browser after you add a Web Reference to your development project.

In the Commerce Server 2007 .NET Class Reference, links to COM objects do not function. Instead of using the .NET Class Reference, you can view details about Commerce Server 2007 legacy COM objects in the "COM Object Reference" section.

After you upgrade from Commerce Server 2002 and you add an inventory resource to your site, when you try to access any virtual catalog in Catalog Manager, you receive the following error message:

"Microsoft.CommerceServer.Catalog.CatalogDatabaseException: Could not get the root products for the catalog. ---> System.Data.SqlClient.SqlException: Invalid object name 'Retail2002_productcatalog.dbo.VC1_InventoryView'. Invalid object name 'Retail2002_productcatalog.dbo.VC1_InventoryView'."

To resolve this issue, you must force a virtual catalog rebuild by adding or deleting a rule from your virtual catalog or by using the CatalogContext.RebuildAllCatalogs(true) method in your code.

When you try to view catalog expressions in the Marketing Manager user interface that you migrated from Commerce Server 2002 Service Pack 3, you receive the following error message:

"The expression cannot be opened because its format is not supported by this application."

To resolve this problem, manually change the SQL Server data and use the following example to change your data. For example, change this line:

<IMMED-VAL TYPE="string">shoes</IMMED-VAL>

To this:

<IMMED-VAL TYPE="string"><VALUE>shoes</VALUE></IMMED-VAL>

After you convert an existing ASP.NET Web site project to a Commerce Server project, the Commerce Server Project menu item will not display in the Visual Studio 2005 user interface until you restart Visual Studio 2005.

When you import a catalog, you receive the following error message:

"Line number: 1482: Incorrect syntax near '='."

This can occur when you try to import a catalog that contains a virtual catalog with name length more than 43 characters. To resolve this issue, delete the virtual catalog and use a shorter name.

You must insert a "Save" step between adding and removing child products from a category; otherwise, your final "Save" operation will fail. The following code demonstrates the correct practice to make sure that the "Save" operation succeeds:

category .RemoveProduct("AW029-03");
category .Save(); //New step added.
category .AddProduct("AW099-15");
category .Save(); //This save will succeed

You cannot add non-multilingual properties named "Name" to category definitions. Select a different name for the property.

You may experience minimal, intermittent downtime of catalog data on your live Web site through either Commerce Server Staging or the BizTalk Server adapters. This behavior may occur when you perform catalog import operations that involve full text index generation or virtual catalog rebuilds. Schedule these operations during off-peak hours to minimize disruption.

If you encounter a high rate of SQL Server logons that affect your Web site's performance and you are using Windows authentication to connect to SQL Server, the following setting can improve performance. You can change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Commerce Server 2007\Profiles\UnsafeAuthenticatedConnectionSharing to 1. If you use the 64-bit version of Commerce Server, the registry key to change is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Commerce Server 2007\Profiles instead.

You must consider your environment and security requirements before changing this default value. The default value of zero offers better security but potentially slower performance and means that a logon and logoff will occur for each Profiles System database connection. However, if your Web site uses impersonation to connect to Profiles System resources, there is a security risk when you change the default value. When you do not force new SQL Server logons for each connection to the Profiles System database from the connection pool, old connections from the connection pool are recycled. These connections keep the security permissions from the last impersonated user. The security risk is that a new Web user connects to the Profiles database under the security context of a previous user.

You receive a System.Data.EvaluateException error when you use Customer and Orders Manager to delete ShippingRates from ShippingMethods that contain values after the decimal separator. This occurs on system configurations where you use comma (,) as the decimal separator, such as French and German. To resolve this problem, delete the ShippingMethod, and then create and save a new ShippingMethod with the required ShippingRate values, omitting those ShippingRates that you intended to delete.

When you delete many purchase orders at the same time and you use the PurgeCommerceData tool, you may encounter time-out errors. To resolve this problem, do the following:

1. Increase DTC time out (default is 60 seconds).
   
   
2. Use a shorter time and run the tool more frequently so that fewer orders are deleted in each batch.
   
   

When you install and unpack CSharp.PuP, you receive the following error message:

"80131904:Violation of UNIQUE KEY constraint 'IX_RegionCodes'. Cannot

insert duplicate key in object 'dbo.RegionCodes'."

This can occur because of certain database collation settings. For example, if you use the Finnish_Swedish_CI_AI collation, the letters V and W have the same Primary weight but different ACCENT weights. This treats V and W as equivalent characters. To resolve this problem, you should use the accent-sensitive Finnish_Swedish_CI_AS collation as your database collation. This treats the W and V as different characters.

The following error message might occur in the site packager log file:

"8004E024:COM+ activation failed because the activation could not be completed in the specified amount of time. (Exception from HRESULT: 0x8004E024)"

This error message indicates that Commerce Server could not populate the AllowedStatus table in the transactionconfig database. To populate the AllowedStatus table, open SQL Server Management Studio (open SQL Query Analyzer if you are using SQL Server 2000), and run the regiondata SQL script against the transactionconfig database. The regiondata script is located at %COMMERCE_SERVER_ROOT%\SDK\Samples\SiteCreate\.

When you copy and paste a campaign item that contains an apostrophe in the name, during the paste operation you receive the following error message:

"System.Data.SyntaxErrorException: Syntax error: Missing operand after 's' operator."

To resolve this issue, remove the apostrophe or add an additional apostrophe. For example, if your campaign item was originally named john's ad, change the name to johns ad.

In the Staging system user interface, if you use a root folder as the Staging destination folder, for example C:\ or D:\, the Staging system incorrectly removes system folders and files which will corrupt your operating system installation. Do not use root folders, instead specify a subfolder for the target location.

The authentication account that you use for the staging project requires Read, Write, Delete, and Create permissions to the Staging destination folders.

Do not unpack the Data Warehouse and other site resources to the same database. This is not a supported scenario. It will cause failures because both databases use the same table names.

If you do not have at least six months worth of data, the Bandwidth Summary report will contain only data for the current week. It will not contain a six-month summary. If there is no data for the past week, the chart will not be created.

When you run the Prepare Reports DTS task with SQL Server 2000, you may receive the following error message:

"Level Directory

Processing error [Source data contains no rows] ‘Level Directory’S’"

This occurs when there is no data in the Level 5 Directory dimension. You can safely ignore this error because it does not affect functionality.