Article ID: 254133 - View products that this article applies to.
This article was previously published under Q254133
This article has been archived. It is offered "as is" and will no longer be updated.
If a component's type library has a major version number that is larger than 127, and this component is installed in a COM+ application, then when you try to export this application as an "application proxy," you may receive the following error message:
When Admin SDK is used to export this application as an "application Proxy," error "80110407" is returned.
Export Application :
Error occurred writing to the 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 file. The application was not exported.
NOTE: You can export this application as a "server Application" without any errors.
Microsoft Windows Installer (MSI) defines the type library's version as follows:
The major and minor versions are encoded in the two-byte integer with the minor version in the lower eight bits and the major version in the upper eight bits.This is too small for the actual type library version numbers, which are two-byte integers for major and minor versions.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Date Time Version Size File name Platform ----------------------------------------------------------------- 7/18/2000 08:01p 1.11.1820 1,780,496 msi.dll x86
If you do not want to install this hotfix, a workaround for this problem is to regenerate the type library with a version number that is not greater than 127.
You can change the version number of the type library in the IDL file and recompile it.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
Article ID: 254133 - Last Review: October 20, 2013 - Revision: 1.1