Unsolved
1 Rookie
•
9 Posts
0
679
Dell Thin Clients Suddenly unable to login to WMS. ERROR: Unexpected Token X in JSON..
We had seemingly been working fine with our WMS when someone tried to add a new Thin Client.
The error is:
WMS agent tries to login server
WMS: Failed to login
WMS: Failed to check-in: Failed to login Unexpected token I in JSON at position 0
It gets an IP address, sees the gateway, DHCP, and DNS servers.
I feel like I'm missing something obvious.... so I took a known good thin client that I could see from WMS. I sent a command to factory reset the known good thin client. It took the factory reset, and then could not login either.
I cannot see it from WMS, yet the other devices are manageable. I have taken a newer device, older device, etc, and non can login..... unless they are already present in WMS.
I restarted WMS, checked that no DHCP/DNS changes have been implemented by our network team. Something apparently has happened in the past 3-4 months that I can't figure out.
Any thoughts on troubleshooting this?
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
June 12th, 2023 05:00
Is this windows or ThinOS?
Is this WMS pro and your licenses have expired?
ProtMB
1 Rookie
1 Rookie
•
9 Posts
0
June 12th, 2023 06:00
It's not a pro license. It's just been working fine up until now.
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
June 12th, 2023 07:00
So,
If you manually enter WMS info including group key, the device registers to WMS and functions as expected?
ProtMB
1 Rookie
1 Rookie
•
9 Posts
0
June 12th, 2023 07:00
Further I am using ThinOS to connect to citrix sessions.
I just tested a manual key input at the Thin Client level and it will be seen on WMS as a "pre-registered" device. But it used to pick up a default key on boot up. This is a real puzzler as we've been looking at it from the network side an nothing has changed there either.
The only consistent is the "JSON error".
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
June 12th, 2023 10:00
At a certain point Case sensitivity was enforced both in the OS and in WMS, but that was a long time ago. Complexity rules were also introduced, but I cant remember when
Matching case and having a complex field seems like it will resolve your issue.
Glad you worked through it.
Cheers
ProtMB
1 Rookie
1 Rookie
•
9 Posts
0
June 12th, 2023 10:00
Yes it does.
I asked someone to look into the DNS settings and I may have found the problem.
I saw an entry for a default group entry key that was very generic. All it did was get a thin client into a group I have so it could be managed.
What I noticed was at some point this default group had an "Invalid Key" message. But I could still see the key was there, and unchanged. (IE: something like Defa-defadefa )
As mentioned though this has been working for years. And within 3-4 months we had initiated a few new thin clients without issue.
So I changed this old group key to something that was 'valid'. I added a few characters, numbers and extended it.
Next I asked the DNS to use that setting as well, entering the new key.
Upon testing this, the thin client was now accepted in the default group without requiring me to manually input the group code.
So it worked... but still is a head scratcher.
At some point (I'm guessing here) that the vanilla 'defadefa' type code stop being valid. Even though it was for months and months after our upgrade to WMS 3.5
All I can imagine is that the server took updates or something, rebooted and then WMS realized it was using an invalid code???