FIX: Incremental catalog import does not update the OriginalPrice field in Commerce Server 2007 or in Commerce Server 2009

Applies to: Commerce Server 2009


Consider the following scenario:
  • You have a computer that is running Microsoft Commerce Server 2007 or Commerce Server 2009.
  • You perform an incremental catalog import to update the price of a catalog item in Catalog Manager.

    Note When the OriginalPrice field differs from the cy_list_price field, the cy_list_price field is reset to the OriginalPrice field without notification if the primary parent category of the product is changed. .
In this scenario, the value of the OriginalPrice field is not updated. Therefore, the value of the cy_list_price field does not match the value of the OriginalPrice field.

For example, consider the following scenario:
  • You create a product catalog in Commerce Server site A.
  • You add a product, and then you set the price of the product to 10. The values of the cy_list_price and OriginalPrice fields are automatically set to 10.
  • You export the catalog from site A, and then you import the catalog into Commerce Server site B.
  • You change the listed price for the product to 8 in Commerce Server site A, and then you export the catalog again.
  • You perform an incremental catalog import into Commerce Server site B.
In this scenario, the value of the cy_list_price field is 8 and the value of the OriginalPrice field is 10 in site B.


This issue occurs because of an error in the Microsoft.catalogserver.dll file.


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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, submit a request to 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: 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.


To apply this hotfix, you must have Microsoft Commerce Server 2007 Service Pack 2 (SP2) or Commerce Server 2009 installed.

Restart requirement

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, type the following commandat a command prompt, and then press ENTER:
Note This command stops and then restarts all IIS services that are running on the computer.

Hotfix 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.
Commerce Server 2007 SP2
File nameFile versionFile sizeDateTimePlatform
Commerce Server 2009 RTM
File nameFile versionFile sizeDateTimePlatform
Commerce Server 2009 TP
File nameFile versionFile sizeDateTimePlatform


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


For more information about current product price and original product price, visit the following MSDN website: