...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)
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)