FIX: You receive a "Timeout" or "exceeds the maximum" error message when you try to import or export a product catalog in Commerce Server 2009

View products that this article applies to.

Symptoms

In Microsoft Commerce Server 2009, you encounter one of the following problems when you export or import a Commerce Server product catalog.

Scenario 1

You try to export a catalog in Catalog Manager.
The catalog contains many languages, all schemas, deleted items, blank values, catalog sets, and properties.

In this scenario, the export process fails. Additionally, you receive an error message that resembles the following:

Line 0: The number of elements in the select list exceeds the maximum allowed number of 4096 elements.

Note You may export the catalog successfully if you reduce the number of catalog languages to a smaller number, such as to less than five catalog languages.

Scenario 2

You try to import an XML file to update an existing product catalog, and the Import schema changes option is selected in Commerce Server Catalog Manager.
The catalog contains many languages.

In this scenario, the import process lasts for some time, such as for 10 minutes or longer. Then, the import fails. During this time period, the progress is not greater than zero percent (0%) completed. Additionally, you receive an error message that resembles the following:

Line 3070: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

If you remove some catalog languages and retry the import, the import may still fail, and you receive the following error message:

Line 3070: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Warning: The table "catalog_name" has been created, but its maximum row size exceeds the allowed maximum of 8060 bytes. INSERT or UPDATE to this table will fail if the resulting row exceeds the size limit.

Note You may be able to import the catalog successfully if you reduce the number of languages of the catalog to one or two languages.

↑ Back to the top

Cause

This problem occurs because Commerce Server uses a single SQL statement for the catalog import and export. If the catalog contains many languages, the process fails because the length of the SQL statement exceeds the limit of the Microsoft SQL Server.

↑ Back to the top

Resolution

To resolve this problem, apply this hotfix.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Commerce Server 2009 installed.

Restart information

You do not have to restart the computer after you apply this hotfix. However, you must restart Internet Information Services (IIS) and the Commerce Server Catalog Import Host COM+ application after you apply this hotfix. To restart IIS, open a Command Prompt window, type the following command, and then press ENTER:

iisreset /restart

Note This option stops all IIS services that are running and then restarts them.

Replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For Commerce Server 2009

File name	File version	File size	Date	Time	Platform
Cs2009hotfixhelper.exe	6.0.4171.42	13,080	17-Mar-2011	07:31	x86
Microsoft.catalogserver.dll	6.0.4171.42	764,712	17-Mar-2011	07:31	x86
Microsoft.commerceserver.runtime.dll	6.0.4171.42	850,744	17-Mar-2011	07:31	x86
Microsoft.commerceserver.catalog.dll	6.0.4171.42	961,336	17-Mar-2011	06:53	x86

For Commerce Server 2009 Template Pack for Microsoft SharePoint 2010

File name	File version	File size	Date	Time	Platform
Cspatchhelper.exe	6.0.4171.509	17,168	16-Mar-2011	14:52	x86
Microsoft.catalogserver.dll	6.0.4171.509	760,616	16-Mar-2011	14:52	x86
Microsoft.commerceserver.runtime.dll	6.0.4171.509	850,744	16-Mar-2011	14:52	x86
Microsoft.commerceserver.catalog.dll	6.0.4171.509	961,336	16-Mar-2011	14:39	x86

Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the maximum sizes and numbers of various objects that are defined in SQL Server components, visit the following Microsoft Developer Network (MSDN) website:

Maximum Capacity Specifications for SQL Server

↑ Back to the top