Knowledge Base

BUG: COM+ Application Proxy Export Fails with Type Library Included

Article ID: 259201

Article Last Modified on 2/21/2002

APPLIES TO

Microsoft COM+ 1.0

This article was previously published under Q259201

SYMPTOMS

When you attempt to export the application proxy for a COM+ Application, you may receive the following error message:

Export Application

Error occurred writing to application file. Either the path cannot be accessed or an existing file cannot be overwritten. Make sure you entered the full path for the application definition. The application was not exported.

CAUSE

Both a dynamic-link library (DLL) and its corresponding type library (.tlb) file have been added to the COM+ application. Both libraries are typically added so that the COM+ Application's DLLs are not deployed with the application proxies on the client computers.

RESOLUTION

Make sure that the type library for the object was not accidentally installed with the DLL in the application.

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 Behavior

Create a Microsoft Visual Basic (VB) DLL.
Copy the DLL and the associated type library (.tlb) file into COM+.
Export the application.

REFERENCES

For more information, please see "Deploying Application Proxies" at the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/library/psdk/cossdk/pgdeployment_toplevel_65gz.htm

Additional query words: Windows 2000 COM+ Export client install setup deploy MSI folder overwrite type library MTS

Keywords: kbbug KB259201

Microsoft KB Archive/259201

Contents