Knowledge Base

PcVue 12 onwards.

This article describes two simple situations 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, the stations communicate together correctly and we stop Data Acquisition Server project. Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of Client station:

2019/04/05,14:21:41.391,3,I,,3130,,101,Server station project DATASERVER10S is stopped

2019/04/05,14:21:44.095,3,W,,3072,,101,Client->server connection abort, DATACLIENT10C -> DATASERVER10S

2019/04/05,14:21:44.095,3,I,,3188,,101,WinSock error = 10054 WSAECONNRESET

2019/04/05,14:21:44.095,3,I,,3240,,101,Connection reset by peer

Second case, we active firewall on client station and block inbound rule for SV Application. Then we restart Data Acquisition Server. Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of Data Acquisition Server station:

2019/04/05,14:23:26.270,0,T,,0,,1,SV,Starting project in LAN …

2019/04/05,14:23:26.286,3,I,,17290,,1,The station name for this instance is: DATASERVER1, station number is: 1

2019/04/05,14:23:47.330,3,W,,3072,,1,Client->server connection abort, DATASERVER10C -> DATACLIENT10S

2019/04/05,14:23:47.330,0,T,,0,,1,SV,Starting project in Eqt …

Remark:
This is the same message as if PcVue was not launched on Client station

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 3072 corresponds to Client->server connection abort