Microsoft KB Archive/255890

= PRB: DCOM Client Stops Responding When You Pass a Callback Interface Pointer =

Article ID: 255890

Article Last Modified on 10/12/2007

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Server 4.0 Enterprise Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q255890



SYMPTOMS
When a Distributed Component Object Model (DCOM) client makes a remote method call to pass a callback interface pointer to the server, and the SYSTEM account does not have access permissions on the client computer, a problem may occur. If the User Datagram Protocol (UDP) is used, the client may stop responding (hang). If the Transmission Control Protocol/Internet Protocol (TCP/IP) is used, the application may return the E_OUTOFMEMORY error.



CAUSE
By default, the SYSTEM account does not have access permissions on the client computer; as a result, DCOM cannot marshall the callback interface pointer.



RESOLUTION
To resolve this problem, give access permissions to the SYSTEM account. For DCOM to work, you must assign access permissions to the SYSTEM account.



MORE INFORMATION
To check the default access permissions, perform the following steps:
 * 1) Start Dcomcnfg.exe.
 * 2) Click the Default Security tab, and then click Edit Default for default access permissions. The list must include SYSTEM: allow access. If the list is empty, then the launching user and the SYSTEM account have access permissions.

Additional query words: SYSTEM hang

Keywords: kbdcom kbprb KB255890

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.