BUG: Component's Friendly Name Isn't Registered When Importing *.pak Files from MTS into COM+ on Windows 2000 (260368)


The information in this article applies to:

  • Microsoft Transaction Server 2.0
  • Microsoft COM+ 1.0
  • the operating system: Microsoft Windows 2000
This article was previously published under Q260368

SYMPTOMS

In Component Services Explorer, when you try to install a prebuilt application from a *.pak file that was created on a Microsoft Windows NT 4.0-based computer, the friendly name of the component doesn't appear in the registry under the CLSID of each component. This does not affect the normal functioning of the component. This is a problem only if an application uses the friendly name explicitly.

CAUSE

This problem is caused by a bug in the InstallPackage function, which doesn't import the value of the friendly name.

RESOLUTION

The following are two workarounds for this problem:
  • Install each component manually by using Component Services instead of by using the *.pak files. -or-

  • After importing the *.pak file, change the {Default} value for each component's CLSID to the appropriate friendly name of the component.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

This bug does not affect the normal functioning of the component. This is a problem only if an application uses the friendly name of the component explicitly.

The following are examples of applications that use the friendly name:
  • The Commerce Server Pipeline Editor displays pipeline components by the component's (friendly) name from the registry.
  • The Comcnfg.exe file.

Steps to Reproduce Behavior

  1. Export an MTS package from Windows NT 4.0 as a *.pak file.
  2. Use Component Services to import the *.pak file to Windows 2000.
  3. Look in the registry for the {Default} data value under My_Computer\HKCR\CLSID\{clsid} for the components that were imported.

REFERENCES

Modification Type:MajorLast Reviewed:5/28/2003
Keywords:kbbug kbDeployment KB260368
©2002 Microsoft Corporation. All rights reserved.