DCOM errors by numeric code

0x80004002

No such interface supported.

This error occurs when the client connects to the server. It indicates that the client has connected to the server but cannot obtain a pointer to a COM interface. The OPC standards include facilities that are optional; This error is returned if an optional COM interface is not supported. However, this error is more commonly seen with servers that implement their own security, for the following reasons:

• Some OPC servers do not accept connections from third-party OPC clients and return this error if such clients attempt to use the server.

• The account used to run the client is not authorized by the OPC server security.

• The license for the OPC server is not installed correctly.

• The default authentication level for the client computer is set to None, or simple file sharing is enabled on the OPC Server computer, which results in an anonymous logon.

0x8000401a

The server process could not be started because the configured identity is incorrect.

This connection error indicates a problem with the OPC server identity settings:

• The account specified for the server identity does not exist.

• The password for the account specified for the server identity is incorrect or expired.

• The server has been configured with an identity of Interactive user, but no user is logged on to the console of the server computer.

  Check the identity specified in the DCOM configuration for the server. Verify that the account exists, and verify the password. Use of Interactive user as the server identity is discouraged because it requires that a user be logged on to the computer before the client attempts connection.

0x80040111

ClassFactory cannot supply requested class.

This connection error indicates that either the OPC is not registered correctly or the server does not accept the type of connection requested by the client. Most OPC servers accept both local and remote connections, but some may only accept one type. OSIsoft OPC clients use a local connection if the server node name is omitted or if "localhost" is used as the node name. If a server accepts only remote connections, the client can be run on the OPC server node by including the server node name in the /server parameter (for example, /server=myopcserver::some.opcserver.1).

0x80040112

Class is not licensed for use.

Not a DCOM security problem. Verify that the license for the OPC server is installed.

0x80040154

Class not registered.

This connection error can occur if the interface cannot obtain the OPC server information from the registry. In some cases, the problem is identical to that described for error 80040111 (ClassFactory cannot supply requested class).

0x80040202

Connection attempt failed.

Unable to open the access token of the current thread. (incorrect error string)

This error occurs when the client attempts to advise a group if the OPC server cannot establish a new connection to the interface. This error might be caused by DCOM security problems or by general network issues, as follows:

• Security

  Possible causes for security errors:

  • The client Limits ACL does not allow a connection from the account used as the server’s identity.

  • The server’s authentication level is set to NONE and the client computer Limits ACL does not allow a connection from ANONYMOUS LOGON.

  • Simple file sharing is enabled on the server computer.

• Network

  Possible causes for network errors:

  • A firewall prevents the server from initiating a connection to the client computer.

  • A firewall between the server and client uses network address translation (NAT).

  • The DNS server for the network is returning an incorrect IP address for the client computer.

0x8007000e

Server out of memory.

If the server is a PI OPC server, this error message can be caused by multiple OPC processes running. For instance, if there are two PI OPC DA processes, OR two PI OPC HDA processes running simultaneously, this error might occur. Stop one of the duplicate processes to fix the issue.

0x80070005

General access denied error.

The most common DCOM security error. Either the user account associated with the OPC interface does not have permission to perform the requested action, or the account cannot be authenticated by the server.

Access denied errors can occur when the client attempts to connect to the server (CoCreateInstanceEx errors) if the account running the client does not have permission to access the server, or when the client attempts to advise groups if the account associated with the server does not have permission on the client computer.

• Error on connection

  Possible causes:

  • The account running the client does not have required permissions to activate or launch the OPC server.

  • The client account does not have remote access permission in the system-wide Limits access control list (ACL).

  • The account running the client cannot be authenticated by the server computer.

  • The default authentication levels for both server and client computer is set to NONE or simple file sharing is enabled, which results in an anonymous logon.

    To troubleshoot access denied errors on connection, you must determine if the account that is being used for the connection is the one you intend, and that the account has the required permissions.

    First, check the Windows security log on the server computer (security auditing must be enabled). Logon failure audits indicate problems with the client account, due to either an unknown user or bad password. If no logon failures are recorded, check success audits to identify logons from the client computer and note the account. If the account is ANONYMOUS LOGON, the effective authentication level might be NONE, or simple file sharing might be enabled on the server computer.

    Next, check the Windows System log for DCOM errors. If the client account is not in the default of server-specific DCOM ACLs, an error is logged.

• Advise access failure

  Possible causes:

  • The account used as the server identity does not have required permissions in the system default DCOM ACL.

  • The account used as the server identity does not have remote access permission in the system-wide Limits ACL.

  • The account used as the server identity cannot be authenticated by the server computer.

  • The default authentication levels for both server and client computer is set to NONE, or simple file sharing is enabled, which results in an anonymous logon.

    Follow the same steps to troubleshoot advise access failures as for connection failures, except that you need to look at the logs for the client computer, and there are no DCOM ACLs specific to the client process, only the system default ACLs.

0x800700008

Not enough storage is available to process this command. Out of memory.

0x8007007e

The specified module could not be found.

This connection error indicates a problem with the installation of the OPC server. The executable file for the OPC server cannot be loaded.

0x800706ba

The RPC server is unavailable.

This error might be generated either on connection or advise. It indicates that a connection to the Windows Remote Procedure service (RPCSS) cannot be made, either because the service itself is not running or impaired or because a firewall prevented the connection.

• Error on connect

  Troubleshooting steps:

  • Using the Windows Services control panel, verify that the Windows Remote Procedure service is running on the server computer (the task list cannot be used in recent Windows versions because it actually runs under the svchost.exe process). To determine whether the computer is listening on port 135, issue the netstat –a command. If RPCSS is not running, verify that DCOM is enabled on the computer and, if necessary, restart the service.

  • If there are no obvious problems with the RPCSS service, it is likely that access to port 135 is blocked. If the server is using Windows Firewall, add TCP port 135 to the firewall exception list.

• Advise access failure

  Steps for troubleshooting RPC server failures on advise calls are the same as those for errors on connection, except that they will be done on the client computer rather than the server.

0x80080005

Server execution failed.

Generic failure code that occurs on connection, if the OPC server does not register with DCOM before timing out. The error is non-specific, but can be caused if the account configured as the identity for the OPC server does not have file system access to the server executable. Check the Event Viewer for the following error:

(EventID =10010, Type=Error):
"Server [X] did not register with DCOM within the required timeout"

Edit the permissions for the directory containing the executable to include the account used as the server identity with full permissions, as described previously. Consult your OPC server vendor or documentation for proper settings.