Knowledge Base

PcVue 12 onwards.

This article describes a simple issue we can encounter frequently between two PcVue stations. Note that there is a more generic article about understanding networking errors with Nmap tool, please have a look if you are not confident with the subject by clicking here. We will use this simple architecture so it is easier to understand.

First case, there is an issue with the network card of the Data Acquisition Server station. It can be broken, deactivated, mis configured… Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of Client station:

2019/04/05,17:30:26.679,3,W,,3174,,101,Time out (20 s) on server connection DATASERVER10S on watchdog message acknowledgment 

2019/04/05,17:30:26.679,3,W,,3180,,101,Ask deconnection of DATASERVER10S server connection

2019/04/05,17:30:26.679,3,W,,3072,,101,Client->server connection abort, DATACLIENT10C -> DATASERVER10S

2019/04/05,17:30:26.679,3,I,,3188,,101,WinSock error = 10053 WSAECONNABORTED

2019/04/05,17:30:26.679,3,I,,3238,,101,Software caused connection abort

2019/04/05,17:30:26.710,3,W,,3074,,101,Server->client connection abort, DATACLIENT10S -> DATASERVER10C

2019/04/05,17:30:26.710,3,I,,3188,,101,WinSock error = 10060 WSAETIMEDOUT

2019/04/05,17:30:26.710,3,I,,3250,,101,Connection time out

And the traces of Data Acquisition Server:

2019/04/05,17:30:24.904,3,W,,3072,,1,Client->server connection abort, DATASERVER10C -> DATACLIENT10S

2019/04/05,17:30:24.904,3,I,,3188,,1,WinSock error = 10060 WSAETIMEDOUT

2019/04/05,17:30:24.904,3,I,,3250,,1,Connection time out

2019/04/05,17:30:24.919,3,W,,3074,,1,Server->client connection abort, DATASERVER10S -> DATACLIENT10C

2019/04/05,17:30:24.919,3,I,,3188,,1,WinSock error = 10060 WSAETIMEDOUT

2019/04/05,17:30:24.919,3,I,,3250,,1,Connection time out

If the issue is solved and the network communication works again, here is the traces we get on Client station:

2019/04/05,17:34:20.898,3,W,,3068,,101,Client->server connection OK, DATACLIENT10C -> DATASERVER10S

2019/04/05,17:34:20.898,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

2019/04/05,17:34:25.585,3,I,,3070,,101,Server->client connection OK, DATACLIENT10S -> DATASERVER10C

2019/04/05,17:34:25.694,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

And the traces of Data Acquisition Server:

2019/04/05,17:34:20.449,3,I,,3070,,1,Server->client connection OK, DATASERVER10S -> DATACLIENT10C

2019/04/05,17:34:20.511,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

2019/04/05,17:34:25.129,3,W,,3068,,1,Client->server connection OK, DATASERVER10C -> DATACLIENT10S

2019/04/05,17:34:25.129,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

Second case, there is an issue with the network card of the Client station. Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of Client station:

2019/04/05,17:36:54.819,3,W,,3074,,101,Server->client connection abort, DATACLIENT10S -> DATASERVER10C

2019/04/05,17:36:54.819,3,I,,3188,,101,WinSock error = 10053 WSAECONNABORTED

2019/04/05,17:36:54.819,3,I,,3238,,101,Software caused connection abort

2019/04/05,17:37:15.662,3,W,,3174,,101,Time out (20 s) on server connection DATASERVER10S on watchdog message acknowledgment 

2019/04/05,17:37:15.662,3,W,,3180,,101,Ask deconnection of DATASERVER10S server connection

2019/04/05,17:37:15.662,3,W,,3072,,101,Client->server connection abort, DATACLIENT10C -> DATASERVER10S

2019/04/05,17:37:15.662,3,I,,3188,,101,WinSock error = 10053 WSAECONNABORTED

2019/04/05,17:37:15.662,3,I,,3238,,101,Software caused connection abort

And the traces of Data Acquisition Server:

2019/04/05,17:37:14.171,3,W,,3174,,1,Time out (20 s) on server connection DATACLIENT10S on watchdog message acknowledgment 

2019/04/05,17:37:14.171,3,W,,3180,,1,Ask deconnection of DATACLIENT10S server connection

2019/04/05,17:37:14.171,3,W,,3072,,1,Client->server connection abort, DATASERVER10C -> DATACLIENT10S

2019/04/05,17:37:15.450,3,W,,3074,,1,Server->client connection abort, DATASERVER10S -> DATACLIENT10C

2019/04/05,17:37:15.450,3,I,,3188,,1,WinSock error = 10054 WSAECONNRESET

2019/04/05,17:37:15.450,3,I,,3240,,1,Connection reset by peer

If the issue is solved and the network communication works again, here is the traces we get on Client station:

2019/04/05,17:41:45.896,3,W,,3068,,101,Client->server connection OK, DATACLIENT10C -> DATASERVER10S

2019/04/05,17:41:45.896,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

2019/04/05,17:42:00.208,3,I,,3070,,101,Server->client connection OK, DATACLIENT10S -> DATASERVER10C

2019/04/05,17:42:00.318,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

And the traces of Data Acquisition Server:

2019/04/05,17:41:45.439,3,I,,3070,,1,Server->client connection OK, DATASERVER10S -> DATACLIENT10C

2019/04/05,17:41:45.486,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

2019/04/05,17:41:59.760,3,W,,3068,,1,Client->server connection OK, DATASERVER10C -> DATACLIENT10S

2019/04/05,17:41:59.760,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

Remark:
Messages of type 9008 (Networking message version) do not appear in the event viewer but are well saved in Trace.log file.

Trick:
When you are searching error messages in Trace.log, MacroTrace.log or in the knowledge base, it is better searching for the error code instead of the text message itself. The message can change regarding the language used, the code will still be the same. Here for instance, error code 3188 corresponds to WinSock error = 10053 WSAECONNABORTED