Last updated March 28, 2008
This Readme contains important updates and information in addition to what is available in the current Microsoft® Commerce Server 2007 documentation release. For detailed information about how to install Commerce Server 2007, see the Installation and Configuration Guide at
The following are known issues in this release:
Upgrading from Previous Commerce Server Releases
Extending Existing ASP.NET Sites in Microsoft Visual Studio® 2005 to use with Commerce Server 2007
Commerce Server Staging
Data Warehouse System
Windows Server 2008 Logo Certification Issues
Some Commerce Server 2007 features in this release require special consideration as described in the following list:
This release does not support coexistence with Microsoft BizTalk® Server 2004.
All editions of this release support Microsoft Windows Server® 2003 with Service Pack 1, and Windows Server 2003 R2.
Additionally, Commerce Server 2007 Developer Edition and Business Management Applications support Microsoft Windows XP Professional with Service Pack 2.
Commerce Server documentation obscured by Microsoft SQL Server™ 2005 filter
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.
Links to Web methods topics in the .NET Class Reference
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.
Links to COM object topics in the .NET Class Reference
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.
Upgrading from Previous Commerce Server Releases
Rebuild of virtual catalog fails after you upgrade from Commerce Server 2002 when you add the inventory resource
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.
Cannot view catalog expression migrated from Commerce Server 2002 Service Pack 3 in the Marketing Manager user interface
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:
Extending Existing ASP.NET Sites in Visual Studio 2005 to use with Commerce Server 2007
Restart Visual Studio 2005 after you convert ASP.NET Web site projects to Commerce Server projects
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.
Cannot import any catalog after you create a virtual catalog with a name length more than 43 characters
When you import a catalog, you receive the following error message:
"Line number: 1482: Incorrect syntax near '='."
|The line number in the error message may vary.|
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.
Cannot add and remove child products from a category in one step
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
Error: "Name" property already is in the SKU metadata
You cannot add non-multilingual properties named "Name" to category definitions. Select a different name for the property.
Downtime when you make catalog changes to your live Web site
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.
Performance issue with Profiles System database connections when you use Windows authentication
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.
System.Data.EvaluateException error when you delete ShippingRates
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.
Deleting lots of purchase orders can cause time-out
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:
Increase DTC time out (default is 60 seconds).
Use a shorter time and run the tool more frequently so that fewer orders are deleted in each batch.
UNIQUE KEY constraint error during install and unpacking CSharp.PuP
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.
Unpacking a site might not populate the AllowedStatus table
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\.
Marketing Manager fails with an error when you copy and paste a campaign item that contains an apostrophe in the name
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."
|The character reported in the error may vary.|
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.
Commerce Server Staging
Staging UI incorrectly allows root destination folders
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.
Folder permissions for Staging authentication accounts
The authentication account that you use for the staging project requires Read, Write, Delete, and Create permissions to the Staging destination folders.
Data Warehouse System
Do not unpack the Data Warehouse and other resources to the same database
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.
Bandwidth Summary report requires 6 months of data
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.
Prepare Reports failure with SQL Server 2000
When you run the Prepare Reports DTS task with SQL Server 2000, you may receive the following error message:
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.
Windows Server 2008 Logo Certification Issues
Commerce Server 2007 is now certified for and supported on Microsoft Windows Server 2008. The release version of Commerce Server 2007 and Commerce Server 2007 Service Pack 1 (SP1) can be run on Windows Server 2008, with Internet Information Service (IIS) 7 configured to Classic mode.
The following Microsoft Knowledge Base articles identify Windows Server 2008 Logo Certification issues with Commerce Server 2007 and Commerce Server 2007 SP1. None of the Windows Server 2008 Certification issues cause operational problems or failures in Commerce Server 2007:
KB948538: Some Starter Site DLLs delivered in the PUP files with the release version of Commerce Server 2007 are not signed. Note that this KB article pertains only if you downloaded the Starter Site. See
KB948539: Manifest files compliant with Windows Server 2008 Certification requirements are missing after installing the release version of Commerce Server 2007. See
KB948540: Some files remain on the computer after you uninstall Commerce Server 2007. See
KB948541: The release version of the Commerce Server 2007 installer puts files in the Windows System folder instead of a program folder. See
KB948542: You notice that the company information is missing from some Commerce Server 2007 .DLL files after you install the release version of Commerce Server 2007 on a Windows Server 2008-based computer. See
KB948543: The release version of the Commerce Server 2007 installer does not include a Windows Server 2008 UAC-compliant manifest. See
KB948544: The CSConfig.exe file that launches after installation of the release version of Commerce Server 2007 does not have an embedded manifest supporting the User Account Control (UAC) control for Windows Server 2008. See
KB948545: No upgrade table is included in the installation after you install the release version of Commerce Server 2007 on a Windows Server 2008-based computer. See
KB948773: Describes the custom actions that are used in the Commerce Server 2007 installation program. See
KB949745: You receive an error message when Commerce Server 2007 is installed on a computer that is running Windows Vista or Windows Server 2008. This error occurs because the Commerce Server 2007 installer adds a dependency for the Windows Management Instrumentation (WMI) service in the DependOnService registry value. See
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, Commerce Server, BizTalk, Visual Studio, Windows, Windows Vista, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.