Back

Topic

[KB1035]Networking errors: station is launched without Networking option on the license

Tags: License, Networking

5 years ago
By LM
Options
Print
Applies to:

PcVue 12 onwards.

Summary:

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.

Simple architecture

Details:

First case, the 2 stations are launched without the Network right option coded on their license. Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of both stations:

2019/05/03,10:52:48.621,3,W,,11162,,1,Networking cannot be started: insufficient licence right

If you re-read a key with the Networking right option on the client computer, it immediately tries to connect to the server:

2019/05/03,11:39:37.099,6,I,,17082,,101,Key on, license number=44221 station owner=DATACLIENT1

2019/05/03,11:39:38.005,3,W,,3068,,101,Client->server connection OK, DATACLIENT10C -> DATASERVER10S

2019/05/03,11:39:38.005,3,W,,3192,,101,The connection DATACLIENT10C DATASERVER10S has been gracefully closed by remote station

2019/05/03,11:39:38.005,3,W,,3072,,101,Client->server connection abort, DATACLIENT10C -> DATASERVER10S

2019/05/03,11:39:38.115,6,I,,17032,,101,After key read, communication returns to standard mode

2019/05/03,11:40:08.021,3,W,,3068,,101,Client->server connection OK, DATACLIENT10C -> DATASERVER10S

2019/05/03,11:40:08.021,3,W,,3192,,101,The connection DATACLIENT10C DATASERVER10S has been gracefully closed by remote station

2019/05/03,11:40:08.021,3,W,,3072,,101,Client->server connection abort, DATACLIENT10C -> DATASERVER10S

Every 30 seconds…

Traces on the server:

2019/05/03,11:39:38.248,3,W,,11164,,1,Server->client connection DATASERVER10S -> DATACLIENT10C rejected because of insufficient licence right

2019/05/03,11:40:08.263,3,W,,11164,,1,Server->client connection DATASERVER10S -> DATACLIENT10C rejected because of insufficient licence right

2019/05/03,11:40:38.262,3,W,,11164,,1,Server->client connection DATASERVER10S -> DATACLIENT10C rejected because of insufficient licence right

Every 30 seconds…

If you re-read a key with the Networking right option on the server station, it immediately tries to connect to the client and then the next time the client tries to connect, it is done correctly. Traces on the server:

2019/05/03,11:47:47.462,6,I,,17082,,1,Key on, license number=53188 station owner=DATASERVER1

2019/05/03,11:47:48.226,3,W,,3068,,1,Client->server connection OK, DATASERVER10C -> DATACLIENT10S

2019/05/03,11:47:48.232,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

2019/05/03,11:47:48.233,3,I,,1,,1,First connection with server DATACLIENT10S

2019/05/03,11:47:49.196,6,I,,17032,,1,After key read, communication returns to standard mode

2019/05/03,11:48:08.527,3,I,,3070,,1,Server->client connection OK, DATASERVER10S -> DATACLIENT10C

2019/05/03,11:48:08.527,3,I,,1,,1,First connection with client DATACLIENT10C

2019/05/03,11:48:08.527,3,I,,9008,,1,Networking message version of station DATACLIENT1 = 120001

Here is the traces we get in the event viewer (shortcut F7) and in Trace.dat of Client station:

2019/05/03,11:47:47.989,3,I,,3070,,101,Server->client connection OK, DATACLIENT10S -> DATASERVER10C

2019/05/03,11:47:47.989,3,I,,1,,101,First connection with client DATASERVER10C

2019/05/03,11:47:47.989,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

2019/05/03,11:48:08.287,3,W,,3068,,101,Client->server connection OK, DATACLIENT10C -> DATASERVER10S

2019/05/03,11:48:08.287,3,I,,9008,,101,Networking message version of station DATASERVER1 = 120001

2019/05/03,11:48:08.287,3,I,,1,,101,First connection with server DATASERVER10S

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 11162 corresponds to Networking cannot be started: insufficient licence right

Created on: 11 Oct 2019 Last update: 30 May 2024