Microsoft KB Archive/322807

= BUG: Application Proxy Exported from WinXP Pro Includes a Not Valid LocalServer Reg Key String on NT4.0 and Win98 =

Article ID: 322807

Article Last Modified on 12/21/2004

-

APPLIES TO

 Microsoft COM+ 1.0, when used with:  Microsoft Windows 98 Standard Edition

 Microsoft Windows 98 Second Edition

 Microsoft Windows Millennium Edition

 Microsoft Windows XP Professional</li></ul>

 Microsoft Windows NT 4.0</li></ul> </li> Microsoft COM+ 1.5, when used with:  Microsoft Windows 98 Standard Edition</li></ul>

 Microsoft Windows 98 Second Edition</li></ul>

 Microsoft Windows Millennium Edition</li></ul>

 Microsoft Windows XP Professional</li></ul>

 Microsoft Windows NT 4.0</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q322807

<div class="symptoms_section">

SYMPTOMS
If you try to run a COM+ client from a remote computer that is running Windows 98, Windows NT 4.0, or Windows Millennium Edition (Me), you may receive the error 429:

&quot;ActiveX component can't create object&quot; with a VB6 client.

Or, you may receive the following error message:

&quot;Server object error 'ASP 0177 : 80080005' : Server.CreateObject Failed&quot; with an ASP client.

This can occur when you use an application proxy that is generated from Windows XP Professional. The COM+ server application can be either .NET Enterprise Services components or conventional COM+ components.

<div class="cause_section">

CAUSE
This problem occurs because COM+ Application Proxy places a not valid registry key in the LocalServer key. The key appears as follows:

On a Windows NT 4.0-based computer and on a Windows 98-based computer, this causes the client to fail to create the object. This occurs because the client relies on the registry to find the remote server and not the COM+ Catalog as Windows 2000 and Windows XP both do.

<div class="resolution_section">

RESOLUTION
You can resolve this problem by either deleting this key manually on the client or by using the Orca editor to remove the key from the Microsoft Windows Installer file before you install the key on the client. When you delete this key, the remote computer is forced to look at the AppID key, where the information is located.

The bug is fixed in Windows XP Service Pack 1.

<div class="status_section">

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

<div class="references_section">