You have a computer that is running a 64-bit version of Commerce Server 2009 or of Commerce Server 2007.
You open Total.pcf in the 64-bit edition of the Commerce Server Pipeline Editor. You check the properties page of the Commerce Splitter pipeline component to make sure it contains configuration data.
You insert a Commerce Scriptor, or Commerce StepwiseShipping pipeline component, or any 64-bit Commerce Server pipeline component after the Commerce Splitter pipeline component.
You save the pipeline configuration file (pcf) and then you close Pipeline Editor.
You open the Total.pcf again in Pipeline Editor.
In this scenario, you find that the configuration data for the Commerce Splitter pipeline component is missing when you check the component property.
When this problem occurs, if you execute later pipelines in Total.pcf, you receive an error message that resembles the following:
Type : System.Runtime.InteropServices.COMException, mscorlib, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : Component Execution failed for component[0x1] hr: 0x1DE4A430
Dictionary error: Value for key 'shipping_method_id' in dictionary '' missing (expected a variant of type 8)
Source : Commerce.MtsPipeline
Note You cannot resolve this issue even after you add back the configuration data back into the Commerce Splitter pipeline component.
More information about this hotfix
To resolve this issue, install this hotfix, and then, you must create a new total.pcf file. To do this, follow these steps:
To create a new Total.pcf file, you must open a Total.pcf that was never changed by using the 64-bit edition of the Commerce Server Pipeline Editor. You can add the desired 64-bit pipeline components into the Total.pcf file.
Replace the old Total.pcf files by using the newly created Total.pcf file.
Restart Internet Information Services (IIS) for the change to take effect. To restart IIS, at a command prompt, type the following command, and then press ENTER:
Note This option stops all IIS services that are running and then restarts them.
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 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:
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.
You must have Commerce Server 2007 Service Pack 2 or Commerce Server 2009 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix package.
Hotfix replacement information
This hotfix package does not replace a previously released hotfix package.
The English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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 Service Pack 2
Commerce Server 2009
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about configuring and running a pipeline in Commerce Server 2009, visit the following MSDN websites: