- This topic has 14 replies, 4 voices, and was last updated 3 years, 2 months ago by
.
-
Posts
-
Something is going on with WMS, it’s showing more than 100 Non-Compliant device. after looking at those devices, it’s showing that they haven’t checked in for a while, but that’s not true because everyone is using them.
I tried also to restart one of the clients via WMS, didn’t work. the logs from the device is showing this :
WMS agent failed to open HTTP server:
https://us1.wysemanagementsuite.com:443, errno: 7607
WMS agent execute http request error (cannot connect)
MQTT alert failed
any thought why it’s acting like that?
Thank you,
Looks like port 443 is not accessible.
But, you can use the WMS web GUI, can’t you?As the devices are caching the last good config, it is obvious that they are still working even they cannot access WMS.
CG
Yes I still can access the WMS web GUI, I will look into the port 443 and get back to you
Thank you
I was also thinking it may happen because of my WMS licensing, I already reached 100% of TC seats, I checked few thin clients they are showing this message:
WMS Failed to register (Server License is invalid).
any thoughts?
Do you have free licenses available? Or at least matching number?
CG
Have the same issue here, also with WMS Cloud.
Just 2 are checked-in as they are never shutdown, but all the others cant register.
did you check the logs to see what’s causing this? is it licensing or ports been blocked?
I had to open a port and re-register the non-compliant TCs.
Hi vanyouss,
The event log literally says “WMS Server License invalid”.
Port 80 and 443 are open.
And the TCs were also put into 2 different networks, still the same.Already removed some TCs and re-registered it.
It provisions for just one single time and then this messages comes up again.Same also on 9.1 which I manually updated on one device.
I am now seeing this exact issue at two of my clients. In both cases they are using the cloud WMS. You can remove the thin client from the WMS portal, reboot it so that it re-registers, and it will successfully communicate with WMS one time. After that, it will give you the “license is invalid” message in the logs and stops communicating with WMS. Happening with v8 and v9 firmware.
precisely my case too.
I didn’t hear back yet from Level 3 support.
Gonna ask what they know.
Can someone confirm what I am seeing? It looks like if I disconnect one thin client from the network and force unregister it from the WMS Cloud console, I can then go back to all of my other thin clients and click the “validate key” and everything is fine. As soon as I bring that thin client back online and it registers, all of my thin clients will fail to validate their key. So if you have 100 subscription licenses and have 99 machines registered, you are fine. As soon as you register the 100th thin client, all the machines will have issues.
- You must be logged in to reply to this topic.