BUG: COM+ Admin SDK Does Allow Exporting Library Proxy (238014)


The information in this article applies to:

  • Microsoft COM+ 1.0
This article was previously published under Q238014

SYMPTOMS

Component Services (COM+) Explorer blocks the export of library applications as application proxies, but you can still export library applications as application proxies through the COM+ Admin SDK without getting error.

When you install this proxy on another computer using Component Services Explorer or the COM+ Admin SDK, no error message will pop up because there is no check in the SDK. The installation will be successful, but attempts to CoCreate a component in this application will result in a "Class Not Registered" error. Therefore, the application is unusable on the client computer. This is because the .dll file is not registered on the client computer.

CAUSE

There is no check in the export code of the Admin SDK to prevent exporting library applications as application proxies. There should be a check in the installation code also for when an application proxy is being installed from an .msi (Windows Installer) file. If the application being installed is indicated as a library application, the installation should fail.

RESOLUTION

Do not export a library application as an application proxy using the Admin SDK.

If you already have an "invalid" .msi file, which are generated by exporting a library application as an application proxy, either
  • Delete the application proxy using the COM+ Explorer or Admin SDK interfaces. You should also delete the .msi file in question and generate a new one, this time not specifying it as an application proxy. -or-

  • Change the application to be exported to be a server application, then re-export the application proxy.

STATUS

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

MORE INFORMATION

Steps to Reproduce this Behavior

  1. Create a new COM+ application as a library using the COM+ Explorer or the Admin SDK.
  2. Export this library to an .msi file using the SDK.
  3. Install this .msi file on a different computer.
  4. Use a client application to create a component in this library. The error message "Class not registered" appears.
Modification Type:MajorLast Reviewed:2/20/2002
Keywords:kbbug kbDCOM kbDSupport KB238014
©2002 Microsoft Corporation. All rights reserved.