Hello.

Try setting EasyDAClient.SharedParameters.ClientParameters.ServerStatusCheckPeriod to Timeout.Infinite (-1), it should disable the periodic calls to GetStatus.

Note that this is a static property on EasyDAClient class, it influences connections to all servers, and it needs to be set once, before any actual instances of EasyDAClient are created.

Best regards

There might be a way to disable the periodic GetStatus check.
Let me know which programming language/tool you are using please.

There are two issues here:

1. The fact that this error appears.
2. The inability to reconnect

To the first issue: The error message is on purpose quite detailed in explaining what has happened. It is because it is a problem on the server side, and you should provide this error message to the server vendor and asked them to explain or resolve the problem. There is nothing we can do on our side (except for maybe changing the implementation to ignore the error, but that would be against the OPC specifications, and it is not clear whether the connection would be operational anyway). The fact that some other client does not show this error might be helpful in troubleshooting (on the server side), but in principle it is largely irrelevant.

To the second issue: If the client does not reconnect, it can be either because a) the server continues to return the "failed" status even after a new OPCServer object is created by the client (for a reconnection), or b) there is a bug in the client (QuickOPC). In order to figure this out, you might be able to view the event log, and check whether EasyOPC is repeatedly trying to connect (there are some settings which influence what goes to event log and where, I can help with it if you like). Also, if the server itself provides an information or logs about who is connecting to it, it may help. Based on my experience, it is more probable that the problem is on the server side as well.

Best regards

...from time to time, some of the systems connected via OPCLabs/Tunneller return errors, and one of them some times won’t reconnect.
Typically this event occurs:

EasyDAClient_ItemChanged Error: -1073442815
“Server failed. This error originates in the OPC Data Access server. A vendor specific fatal error has occurred within the server. The server is no longer functioning. The recovery procedure from this situation is vendor specific. The application will try to reconnect to the server after a configurable period. Technical information: The call to IOPCServer::GetStatus on the OPCServer object has returned OPC_STATUS_FAILED in the OPCSERVERSTATUS structure.”

There might be network problems or the problem is maybe, as indicated, the OPC DA server (Honeywell HWHsc.OPCServer in this case), but the big problem is that EasyOPC some times is not reconnecting after this event occurs, but when we are testing the same connection with Matrikon Explorer, for instance, with the same amount of items (about 2000) this has no problems, and all items appear with quality Good.
We have to restart our webserver to reinitiate easyopc, then it normally works, but some times maybe two or three restarts are required to reconnect to this “troubled” system.

Do you have any suggestions which EasyOPC options we should use in this case to make the client as “reconnectable” as possible ? (we have been a little afraid to make changes from standard, except the ones we have already sent you, and 7 OPC connections in total, from which 6 work fine, will be affected by the same changes)