Article ID: 330165 - View products that this article applies to.
This article was previously published under Q330165
This article has been archived. It is offered "as is" and will no longer be updated.
When you install an application proxy on a Windows XP-based computer, if the Microsoft Installer contains dynamic-link libraries (DLLs) that see external type libraries (typelib), the installation rolls back and then you receive the following result in the Application event log, even though the proxy appears to be correctly installed: HRESULT as 0x80110802
This problem occurs because COM+ does not set the proxy install flag for type libraries in the catalog registrar code during the application proxy installation. For a proxy installation with an external type library, it is typical that class identifiers (CLSIDs) in the typelib are not in the catalog or in the registry, so do not treat their absence as an error. This worked for COM+ with Microsoft Windows 2000 because there was a second flag to avoid the ClassNotFound error.A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.