Article ID: 180384 - View products that this article applies to.
This article was previously published under Q180384
Attempting to access a DCOM Server from a remote client application sometimes results in the following error:
Run-time error '70':
This article describes the most common scenarios in which this error is raised.
Run-time error '70' is typically the result of a security or permissions issue. The following is a list of possible causes of run-time error 70 but is by no means a complete or definitive list.
DCOM Is Not EnabledIf the Server machine does not have DCOM enabled, client machines will receive run-time error 70 when attempting to access the server. This scenario applies to Windows 2000, Windows NT, Windows 95, Windows 98, and Windows Millennium Edition (Me) servers:
The Client User Does Not Have Sufficient PermissionsIf the client user does not have the correct permissions, access to the DCOM Server can be denied. There are several steps to take in order to ensure your client has valid privileges.
If the Server is Windows 95, Windows 98, or Windows Me:
There are several group accounts you will find when you configure users and groups on Windows NT and Windows 2000. The following list is a summary of who belongs to each group:
Group Description -------------------------------------------------------------------------- Interactive Includes all users who log onto a Windows NT or Windows 2000 system locally (at the console). It does not include users who connect to NT resources across a network or are started as a server. Network Includes all users who connect to Windows NT or Windows 2000 resources across a network. It does not include those who connect through an interactive logon. Creator/Owner The Creator/Owner group is created for each sharable resource in the Windows NT or Windows 2000 system. Its membership is the set of users who either create a resource (such as a file) and who take ownership of them. Everyone All users who access the system, whether locally, remotely, or across the network. System The local operating system.
The above list includes the group accounts which are intrinsic to Windows NT and Windows 2000 systems. Your particular network may include more groups from which you may choose. In order to determine the membership of each custom group account, you must contact your network administrator.
The DCOM Server Raises Events to the ClientIf your DCOM server component raises events that are handled by the client application, you must configure DCOM security on the client computer to allow access, and you must configure DCOM security on the server computer. This allows the server to make callbacks to the client, so the event can be raised. If you do not configure DCOM security in this way, error 70 is generated whenever the client application calls the server. This results in an event being raised back to the client. If the server application does not raise events, you do not have to configure DCOM security on the client computers.
If the client computer is running Windows 95, Windows 98, or Windows Me, follow these steps:
If the client computer is running Windows NT or Windows 2000, follow these steps:
Attempting to Access DCOM Server Across Non-Trusted DomainsIf your DCOM Server resides in one Windows NT or Windows 2000 domain, and your client logs on to a second Windows NT or Windows 2000 domain that is not "trusted" by the first, you will receive run-time error '70' when attempting to access the DCOM Server.
For additional information, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/176799/EN-US/ ): INFO: Using DCOM Config (DCOMCNFG.EXE) on Windows NT
Article ID: 180384 - Last Review: September 21, 2006 - Revision: 3.1