PRB: DCOM Client Stops Responding When You Pass a Callback Interface Pointer (255890)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Advanced Server 4.0
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0
  • Microsoft Windows NT Workstation 4.0
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.

REFERENCES

For more information on COM security, see the following MSDN Online Library help topic:

http://msdn.microsoft.com/library/psdk/com/security_0icz.htm

Modification Type:MajorLast Reviewed:6/28/2004
Keywords:kbDCOM kbprb KB255890
©2004 Microsoft Corporation. All rights reserved.