PDA

View Full Version : Authorization failed: License Key conflict


Maldev
May 6th, 2020, 05:37
G'day,

D&D 4E ruleset
No extensions
Latest version

Joining myself as client.
Sometimes the client side freezes and I have to quit the client. The DM side is still running.
When I try to rejoin as client this error occurs
"Authorization failed: License Key conflict" See screenshot 34942

Tried to rejoin several times, but no change.
When I stop the DM instance of Unity and restart it the following error pops up (And I can then join as the Client normally )

[5/6/2020 1:58:11 PM] FGU v4.0.0 ULTIMATE (2020-04-28)
[5/6/2020 1:58:11 PM] Launcher scene starting.
[5/6/2020 1:58:23 PM] Starting cloud server mode. [Maldev]
[5/6/2020 1:58:26 PM] Game server started. [3.104.74.180:54811]
[5/6/2020 1:58:26 PM] Launcher scene exiting.
[5/6/2020 1:58:26 PM] Tabletop scene starting.
[5/6/2020 1:58:26 PM] Match successfully created on lobby.
[5/6/2020 1:59:58 PM] [WARNING] Lost connection to matchmaking server : Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
.
[5/6/2020 1:59:59 PM] [<color="red">ERROR</color>] Process Data File (Maps): An error occurred while parsing EntityName. Line 2897, position 22.
[5/6/2020 2:00:07 PM] Match successfully created on lobby.
[5/6/2020 2:00:08 PM] [WARNING] Frame chatbox contains out-of-range values in TopRight.
[5/6/2020 2:00:08 PM] [WARNING] Frame chatbox contains out-of-range values in Right.
[5/6/2020 2:00:08 PM] [WARNING] Frame chatbox contains out-of-range values in BottomRight.
[5/6/2020 2:00:08 PM] RULESET: 4E ruleset v3.3.11 for Fantasy Grounds
Copyright 2019 Smiteworks USA, LLC
[5/6/2020 2:00:08 PM] RULESET: CoreRPG ruleset v3.3.11 for Fantasy Grounds
Copyright 2019 Smiteworks USA, LLC
[5/6/2020 2:05:12 PM] Campaign saved.

Network Log
[5/6/2020 1:58:23 PM] Noble Connect [11371]: No free buffers, adding one
[5/6/2020 1:58:23 PM] Noble Connect [11376]: No free buffers, adding one
[5/6/2020 1:58:23 PM] Noble Connect [11376]: Found host candidate: HOST (192.168.1.213:64006)
[5/6/2020 1:58:23 PM] Noble Connect [11377]: Found host candidate: HOST (127.0.0.1:64007)
[5/6/2020 1:58:23 PM] Noble Connect [11383]: Sending ALLOCATE REQUEST [71ead7239f823a0bc26809b8] from 192.168.1.213:64006 to 3.104.74.180:3478
[5/6/2020 1:58:23 PM] Noble Connect [11387]: No free buffers, adding one
[5/6/2020 1:58:23 PM] Noble Connect [11408]: Sending ALLOCATE REQUEST [0218fce34a3c7ace2239c0ed] from 127.0.0.1:64007 to 3.104.74.180:3478
[5/6/2020 1:58:23 PM] Noble Connect [11408]: No free buffers, adding one
[6/05/2020 1:58:23 PM] Noble Connect [11426]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:58:23 PM] Noble Connect [11427]: Received ALLOCATE ERROR RESPONSE [71ead7239f823a0bc26809b8] (401): Unauthorized
[6/05/2020 1:58:23 PM] Noble Connect [11430]: Sending ALLOCATE REQUEST [71200c96c120eea51c041b94] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 1:58:23 PM] Noble Connect [11452]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:58:23 PM] Noble Connect [11452]: Received ALLOCATE SUCCESS RESPONSE [71200c96c120eea51c041b94] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:58:23 PM] Noble Connect [11609]: Sending ALLOCATE REQUEST [0218fce34a3c7ace2239c0ed] from 127.0.0.1:64007 to 3.104.74.180:3478
[6/05/2020 1:58:23 PM] Noble Connect [12009]: Sending ALLOCATE REQUEST [0218fce34a3c7ace2239c0ed] from 127.0.0.1:64007 to 3.104.74.180:3478
[6/05/2020 1:58:24 PM] Noble Connect [12810]: Sending ALLOCATE REQUEST [0218fce34a3c7ace2239c0ed] from 127.0.0.1:64007 to 3.104.74.180:3478
[5/6/2020 1:58:26 PM] Noble Connect [14413]: Found candidate: HOST (192.168.1.213:64006)
[5/6/2020 1:58:26 PM] Noble Connect [14413]: Found candidate: HOST (127.0.0.1:64007)
[5/6/2020 1:58:26 PM] Noble Connect [14413]: Found candidate: RELAYED (3.104.74.180:54811 => 192.168.1.213:64006)
[5/6/2020 1:58:26 PM] Noble Connect [14413]: Found candidate: SERVER_REFLEXIVE (139.218.188.196:64006 => 192.168.1.213:64006)
[6/05/2020 1:58:54 PM] Noble Connect [42094]: Sending REFRESH REQUEST [631716ef17bbeb21e51a9324] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 1:58:54 PM] Noble Connect [42116]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:58:54 PM] Noble Connect [42116]: Received REFRESH SUCCESS RESPONSE [631716ef17bbeb21e51a9324] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:59:25 PM] Noble Connect [73154]: Sending REFRESH REQUEST [e46632f4469ba044f09855b8] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 1:59:25 PM] Noble Connect [73178]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:59:25 PM] Noble Connect [73178]: Received REFRESH SUCCESS RESPONSE [e46632f4469ba044f09855b8] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:59:55 PM] Noble Connect [103154]: Sending REFRESH REQUEST [d779c2a81f91a613aad9835e] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 1:59:55 PM] Noble Connect [103177]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 1:59:55 PM] Noble Connect [103177]: Received REFRESH SUCCESS RESPONSE [d779c2a81f91a613aad9835e] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:00:20 PM] Noble Connect [128254]: Sending BIND INDICATION [73dab5c9549648ed19291100] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:00:25 PM] Noble Connect [133154]: Sending REFRESH REQUEST [1514bc491d1dfc19233d1247] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:00:25 PM] Noble Connect [133176]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:00:25 PM] Noble Connect [133176]: Received REFRESH SUCCESS RESPONSE [1514bc491d1dfc19233d1247] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:00:55 PM] Noble Connect [163154]: Sending REFRESH REQUEST [dcb4c30347878829d508f6a7] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:00:55 PM] Noble Connect [163177]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:00:55 PM] Noble Connect [163177]: Received REFRESH SUCCESS RESPONSE [dcb4c30347878829d508f6a7] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:01:25 PM] Noble Connect [193154]: Sending REFRESH REQUEST [a19e16334f9f7c5b5d1991e2] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:01:25 PM] Noble Connect [193176]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:01:25 PM] Noble Connect [193176]: Received REFRESH SUCCESS RESPONSE [a19e16334f9f7c5b5d1991e2] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:01:55 PM] Noble Connect [223154]: Sending REFRESH REQUEST [257d28aa5543d6a3293bf828] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:01:55 PM] Noble Connect [223175]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:01:55 PM] Noble Connect [223175]: Received REFRESH SUCCESS RESPONSE [257d28aa5543d6a3293bf828] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:02:17 PM] Noble Connect [245054]: Sending BIND INDICATION [b8cd2e94a8495cd095367740] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:02:25 PM] Noble Connect [253154]: Sending REFRESH REQUEST [d4f3b17c36dde192f7219079] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:02:25 PM] Noble Connect [253178]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:02:25 PM] Noble Connect [253178]: Received REFRESH SUCCESS RESPONSE [d4f3b17c36dde192f7219079] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:02:55 PM] Noble Connect [283154]: Sending REFRESH REQUEST [45d2b89f1f60c2de4c67c2ed] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:02:55 PM] Noble Connect [283175]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:02:55 PM] Noble Connect [283175]: Received REFRESH SUCCESS RESPONSE [45d2b89f1f60c2de4c67c2ed] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:03:25 PM] Noble Connect [313154]: Sending REFRESH REQUEST [fbc1ed974d103c9d609820b8] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:03:25 PM] Noble Connect [313176]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:03:25 PM] Noble Connect [313176]: Received REFRESH SUCCESS RESPONSE [fbc1ed974d103c9d609820b8] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:03:55 PM] Noble Connect [343154]: Sending REFRESH REQUEST [13823558fa68373db9859a2c] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:03:55 PM] Noble Connect [343175]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:03:55 PM] Noble Connect [343175]: Received REFRESH SUCCESS RESPONSE [13823558fa68373db9859a2c] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:04:13 PM] Noble Connect [361854]: Sending BIND INDICATION [a321044204769650e2768dfa] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:04:25 PM] Noble Connect [373155]: Sending REFRESH REQUEST [9f4d2ae168222b48b26811e2] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:04:25 PM] Noble Connect [373177]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:04:25 PM] Noble Connect [373177]: Received REFRESH SUCCESS RESPONSE [9f4d2ae168222b48b26811e2] from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:04:55 PM] Noble Connect [403155]: Sending REFRESH REQUEST [905775ac3ab7db85e4dcee84] from 192.168.1.213:64006 to 3.104.74.180:3478
[6/05/2020 2:04:55 PM] Noble Connect [403177]: Handle response from 3.104.74.180:3478 at 192.168.1.213:64006
[6/05/2020 2:04:55 PM] Noble Connect [403177]: Received REFRESH SUCCESS RESPONSE [905775ac3ab7db85e4dcee84] from 3.104.74.180:3478 at 192.168.1.213:64006
damned
May 6th, 2020, 06:57
Connect locally and not via Lobby?
Maldev
May 6th, 2020, 07:32
Connect locally and not via Lobby?

Able to join LAN and ran for a bit and host froze (Task manager to quit: was @ 6300 MB usage)
Restarted Host with this error
[5/6/2020 4:31:04 PM] FGU v4.0.0 ULTIMATE (2020-04-28)
[5/6/2020 4:31:04 PM] Launcher scene starting.
[5/6/2020 4:31:20 PM] [<color="red">ERROR</color>] Database restore point found. Saved as new backup file (G:/FGU/campaigns/DAZ testing/db.backup.637243794800013541.xml)
[5/6/2020 4:31:20 PM] Starting private server mode. [(192.168.1.213:1802) (fe80::15d9:998b:cc87:dd42:1802)]
[5/6/2020 4:31:20 PM] Game server started. [192.168.1.213:1802]
[5/6/2020 4:31:20 PM] Launcher scene exiting.
[5/6/2020 4:31:20 PM] Tabletop scene starting.
[5/6/2020 4:32:53 PM] [<color="red">ERROR</color>] Process Data File (Maps): An error occurred while parsing EntityName. Line 2897, position 22.
[5/6/2020 4:33:02 PM] [WARNING] Frame chatbox contains out-of-range values in TopRight.
[5/6/2020 4:33:02 PM] [WARNING] Frame chatbox contains out-of-range values in Right.
[5/6/2020 4:33:02 PM] [WARNING] Frame chatbox contains out-of-range values in BottomRight.
[5/6/2020 4:33:03 PM] RULESET: 4E ruleset v3.3.11 for Fantasy Grounds
Copyright 2019 Smiteworks USA, LLC
[5/6/2020 4:33:03 PM] RULESET: CoreRPG ruleset v3.3.11 for Fantasy Grounds
Copyright 2019 Smiteworks USA, LLC
Trenloe
May 6th, 2020, 08:03
The first error is standard when restating after having to force terminate.

The second error is telling you that your Maps module has a XML issue at line 2897. FGU is stricter on XML than FGC was, so you very often have to do some minor XML editing. Look at that line, character 22. There may be others after you fix that one - go through one error at a time.
Maldev
May 6th, 2020, 08:54
Good to know, Cheers