Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 305718 - Last Review: June 4, 2003 - Revision: 2.1
PRB: Windows NT 4.0 Client Unable to Connect to CLB Component
This article was previously published under Q305718
On This Page
SYMPTOMS
If a Windows NT 4.0-based computer (that is using a COM+ proxy stub) attempts to instantiate a COM+ component that is configured to use Application Center 2000's component load balancing (CLB) feature, the following error may occur.
Runtime error -2147022986 (80070776)
Automation Error:
The object exporter specified was not found
CAUSE
By default, Windows NT 4.0-based computers will attempt to use User Datagram Protocol (UDP) to establish a Distributed Component Object Model (DCOM) connection. In most cases, this connection will fail when you are connecting to a Windows 2000-based computer because Windows 2000 computers use Transmission Control Protocol (TCP) for DCOM connections. Once the connection attempt fails, the Windows NT 4.0 client will attempt to use the next configured DCOM protocol until a DCOM connection can be established.
If the target COM+ component is configured to use CLB, then the Windows NT 4.0 client will attempt to use UDP and will fail with the error noted in the "Symptoms" section. To instantiate COM+ components configured for CLB, the DCOM client must use TCP.
NOTE: Only Windows NT 4.0-based computers are effected by this problem.
RESOLUTION
The DCOM client determines the protocol used when the client is negotiating a DCOM connection. Therefore, the default protocols of DCOM on the Windows NT 4.0 client must be modified to use TCP.
To modify the default protocols of DCOM to use TCP, use the following procedure. Perform these steps on the Windows NT 4.0-based computer only.
- Open DCOMCNFG.
- Navigate to the Default Protocols tab.
- Arrange the protocols in the following order:
Connection-oriented TCP/IP
Connection-oriented SPX
Connection-oriented NetBEUI
Connection-oriented Netbios over IPX
- Click OK on the Distributed COM Configuration Properties property sheet.
- Restart the computer to make the changes to take effect.
STATUS
This behavior is by design in DCOM.
MORE INFORMATION
Steps to Reproduce Behavior
- Create the COM+ proxy stub installation files from a CLB-enabled COM+ component.
- Using the installation files, install the COM+ proxy stub onto a Windows NT 4.0-based computer.
- Attempt to instantiate the component on the Windows NT 4.0 computer.
APPLIES TO
- Microsoft Application Center 2000 Standard Edition, when used with:
- the operating system: Microsoft Windows 2000
- Microsoft Windows NT 4.0
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please