Error message when you import a catalog in Commerce Server 2007 on a Windows XP-based computer: "The product catalog was not imported successfully"

When you use Microsoft Commerce Server 2007 Catalog Manager to import a catalog on a Microsoft Windows XP-based computer, you may receive the following error message in the Import Product Catalog dialog box:Additionally, the following event is logged in the Application log:

Event Type: Error
Event Source: Commerce Server Web Services
Event Category: None
Event ID: 1
Date:
Time:
User:
Computer:
Description:
An exception occurred in the 'CatalogWebService' Web service. Exception details follow:

System.ArgumentException: Value does not fall within the expected range.

Server stack trace:
at Microsoft.CommerceServer.Catalog.ICatalogImport.WebServiceImport(String siteName, Guid token, Boolean inventoryImport, String importOptionsXml, Boolean ignoreInventorySystem, String userName, String authorizationPolicyPath)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.CommerceServer.Catalog.ICatalogImport.WebServiceImport(String siteName, Guid token, Boolean inventoryImport, String importOptionsXmsl, Boolean ignoreInventorySystem, String userName, String authorizationPolicyPath)
at Microsoft.CommerceServer.Catalog.Internal.CatalogServerContextBase.Import(Guid token, ImportOptions importOptions)

For more information, see Help and Support Center at http://support.microsoft.com.

This problem occurs because of an impersonation problem in Windows XP.

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. 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 Web site: 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

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

For more information about the terms that are used in this article, click the following article number to view the article in the Microsoft Knowledge Base: