OPC Common Questions - COM ErrorCodes
OPC Common Questions - COM ErrorCodes
OPC Common Questions - COM ErrorCodes
Page 2 of 7
Table of Contents
4 5
5 5 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6
Page 3 of 7
0x80004002 0x80004005 0x8000401a 0x800706ba 0xc0040001 0xc0040004 0xc0040005 0xc0040006 0xc0040007 0xc0040009 0xc004000a 0xc004000b 0xc004000c 0xc004000d 0xc004000e 0xc004000f
6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7
Page 4 of 7
Introduction
There are many thousands of COM/DCOM error codes. Because OPC is based on the COM/DCOM framework many of the errors you may encounter via OPC may actually be COM/DCOM errors. This document outlines just a few of the most common error codes, by translating them into a description and providing very basic information on resolving them.
Page 5 of 7
0x80040155
0x800401f3 0x80040200
0x80040202
Cannot Connect
Error typically occurs when a call is made to Advise on the connection point. This often means that OPCPROXY.DLL is not the same version on your different computers. Re-install your software.
0x80070002 0x80070005
You need to configure your DCOM Security settings. See our DCOM Tutorial: http://www.softwaretoolbox.com/dcom
Page 6 of 7
Hex Code
Resolution The OPC Server has rejected your request, indicating that the parameter(s) you specified are not valid for the type of request being made. You will need more details on the actual OPC calls being made between the Client and Server. Specific to Windows Services. The service did not start within the allowed time-frame. This indicates an initialization problem with the Windows service. This is a timeout. You may need to increase your timeout settings.
0x80070057
0x8007041d
The service did not respond to the start or control request in a timely fashion.
0x800705b4
This operation returned because the timeout period expired. A floating-point underflow occurred at the RPC server. Incompatible version of the RPC stub. Server execution failed
There is a problem with the OPC Server preventing it from being started by Windows. This may be the result of file-permissions, DCOM Security permissions, or a lack of resources. The OPC Server does not support the interface that you are trying to connect to. Examples may include Item Browsing, Asynchronous I/O or OPC DA v2.x or 3.x interfaces etc. The most common message seen, that yields the least information. In these cases you often need to check the event-logs at your OPC Server for more information. DCOM Configuration permissions. Modify the identity that the application should run under, perhaps specify a named account or choose Interactive User.
0x80004002
0x80004005
Unspecified error
0x8000401a
The server process could not be started because the configured identity is incorrect. Check the username and password. The RPC server is unavailable.
0x800706ba
The OPC Server could not be contacted. This is usually the result of a firewall blocking the application.
Page 7 of 7
Hex Code
Description
Resolution
0xc0040001 0xc0040004 0xc0040005 0xc0040006 0xc0040007 0xc0040009 0xc004000a 0xc004000b 0xc004000c 0xc004000d 0xc004000e 0xc004000f