Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The 64-bit version of Pipeline Editor displays registered custom pipeline components as "<unknown>" when you use Commerce Server 2007 on a 64-bit computer


View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows XP and Windows Vista

↑ Back to the top


Symptoms

Consider the following scenario. You use Microsoft Commerce Server 2007 on a 64-bit computer. You use the Pipeline Component Registration Wizard (Pipereg.exe) to register custom pipeline components. (This tool is included in Commerce Server 2007.) In this scenario, when you try to use the 64-bit version of Pipeline Editor to insert the registered custom pipeline components into an existing stage in the pipeline, you notice that the custom pipeline components are not displayed. Instead, Pipeline Editor displays the components as "<unknown>."

↑ Back to the top


Cause

This issue occurs because Pipereg.exe cannot recognize 64-bit architecture.

↑ Back to the top


Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, follow these steps:
  1. Use the 64-bit version of the Assembly Registration tool (Regasm.exe) to prepare the custom pipeline components for registration. (This tool is included in the latest 64-bit version of the Microsoft .NET Framework.)

    Note You can locate Regasm.exe in the default installation path for the .NET Framework. For example, if you use the .NET Framework 2.0, you can locate Regasm.exe in the following default installation folder:
    C:\Windows\Microsoft.NET\Framework64\v2.0.50727
    To use Regasm.exe, follow these steps:
    1. Open a command prompt.
    2. Change to the default installation folder for the .NET Framework.
    3. At the command prompt, type the following command, and then press ENTER to create a type library for the component:
      regasm .dll file name /tlb:.tlb file name
      Note The placeholder .dll file name represents the name of the .dll file for the custom pipeline component. The placeholder .tlb file name represents the name of the .tlb file for the type library that you want to create. For example, if the .dll file name for the custom pipeline component is MyComp.dll, you would type the following command to create the type library:
      regasm MyComp.dll /tlb:MyComp.tlb
    4. At the command prompt, type exit, and then press ENTER to close the command prompt.
  2. Use Pipereg.exe to register the type library file that you created in step 1. Make sure that you select the Export registration data option to export the registry information to a .reg file.
  3. At a command prompt, run the .reg file that you created in step 2. Or, run the .reg file directly from Windows Explorer. Notice that the custom pipeline components appear correctly in the 64-bit version of Pipeline Editor.

↑ Back to the top


References

For more information about how to use the Pipeline Component Registration Wizard (Pipereg.exe) to register pipeline components, visit the following Microsoft TechNet Web site: For more information about the Assembly Registration tool (Regasm.exe), visit the following Microsoft Developer Network (MSDN) Web site:

↑ Back to the top


Keywords: KB948776, kbprb, kbtshoot, kbexpertiseinter, kbregistry

↑ Back to the top

Article Info
Article ID : 948776
Revision : 2
Created on : 2/18/2008
Published on : 2/18/2008
Exists online : False
Views : 351