Unable to Activate a DCOM Server from a Terminal Server Client Session (237974)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
This article was previously published under Q237974

SYMPTOMS

When you try to activate a DCOM server on a Terminal Server computer from a Terminal Server client session, activation does not work for some components, and the Event log on the Terminal Server computer shows the following:
Unable to start a dcom server, all pipe instances are busy.

The description for Event ID ( 10000 ) in Source ( DCOM ) could not be found. It contains the following insertion string(s):

C:\FCWSCO~1\TSCOMP~1\TSNAVB~1.EXE -Embedding, 231, {8381FDF0-36C7-11D2-8EBD-00C04FD054E0}.
This error occurs when there is high thread and process usage.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Server, Terminal Server Edition, Service Pack 5.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB237974
©2004 Microsoft Corporation. All rights reserved.