Berikut adalah kumpulan error yang sering terjadi ketika anda mencoba mengkoneksikan OPC client ke OPC Server, Error-error ini biasanya muncul pada sisi client dan beberapa error yang sudah diketahui tersedia solusi untuk penyelesaiannya yang bisa jadi ada pada sisi server maupun client.
|The object invoked has disconnected from its clients.
|Re-initialize your OPC Server Connection.
|There is no connection for this connection ID
|Need to run the object to perform this operation
|Class not registered
|The OPC Server, or a component needed to make the OPC connection is not registered with Windows. This may mean that you simply need to register a DLL or OCX file.
|Interface not registered
|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.
|Invalid class string
|The GUID/CLSID of the specified OPC Server is not valid.
|-Unable to impersonate DCOM
-Unknown OLE status code
|DCOM security problem, typically on the Client side. This error typically occurs when trying to specify a callback address for Asynchronous I/O.
| 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.
|The system cannot find the file specified
|Re-install your software.
|Access is denied.
|You need to configure your DCOM Security settings. See our DCOM Tutorial:
|The parameter is incorrect.
| 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.
| The service did not respond
to the start or control request
in a timely fashion.
| Specific to Windows Services. The service did
not start within the allowed time-frame. This
indicates an initialization problem with the
| This operation returned
because the timeout period
| This is a timeout. You may need to increase
your timeout settings.
| A floating-point underflow
occurred at the RPC server.
| Incompatible version of the
|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
|No such interface supported
| 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
| 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.
| The server process could not
be started because the
configured identity is
incorrect. Check the
username and password.
|DCOM Configuration permissions. Modify the
identity that the application should run under,
perhaps specify a named account or choose
| The RPC server is
| The OPC Server could not be contacted. This
is usually the result of a firewall blocking the
Source: Indusoft Documentation
Jika anda pernah mendapatkan jenis error lain silahkan dishare di posting ini. Terimakasih