Unsolved
This post is more than 5 years old
4 Posts
0
2867
July 11th, 2019 11:00
WMS Groups & Configs fails to load after restore
We installed the latest Server 2016 cumulative update KB4507460 on the server hosting WMS 1.4
When thin clients (Wyse 3040) were restarted they failed to find the WMS server and let users login.
We then rolled back the server to a backup from a few hour ago and now the Groups & Configs panel fails to load in WMS.
The thin clients after the roll back take about 15 minutes to get to the user login screen as they get stuck at “WMS agent is retrieving full configurations” stage but the Groups & Configs panel still fails to load
How do we manually start it?
Many thanks
No Events found!
YipYipDingDing
4 Posts
0
July 12th, 2019 03:00
Quick update,
We rolled back further using our Veeam B&R. At this point we were on WMS 1.3 this seems to have booted ok and after moving some clients to other policies in WMS things do seem to be working again.
FYI last week we applied the latest MS updates to our gateway server which stopped all our 3040 clients from loading apps (others reported the same on the web) and this week the MS updates on the WMS server stopped the WMS console from working!
Moose09876
3 Posts
0
August 6th, 2019 05:00
Did you identify which update caused the issue? We're seeing the same freezing issue.
Edit: If only I could read..... Did you get WMS back up to 1.4? We don't have a backup of WMS to roll back to.
mumac
1 Rookie
•
6 Posts
0
September 24th, 2020 04:00
Hi,
any Updates here? We have this issue now after upgrading to v3.0
Groups and Configs was loading, but not the Client details, also the Tomcat crashed again and again.
So we backup the db, reinstall WMS and restore the DB. (the information how to to this is not very detailed)
Tomcat is running, Client details are loading but Groups and Configs shows the blue circle forever.
As new clients can receive the config it should be there but cannot be displayed for some reason.
Maria, MongoDB and Tomcat Log seems to have no error messages about this.
regards
DavidPatrickLevett
1 Message
2
September 30th, 2020 14:00
Details from another post and worked for us.
We did an update to 3.0 and we experienced this issue. The install was successful but when trying to Edit Policies the configuration screen would stay on the spinning wheel. Refreshing the screen and rebooting the server did not resolve. We edited the reg key HKLM\System\CurrentControlSet\Services\memcached and removed this portion of the key value = "-I SERVERNAME -U 0". After a reboot of the WMS server the Admin Console > Edit Policies came up successfully and quickly.
martin.mueller
1 Rookie
•
1 Message
0
May 8th, 2024 12:20
Thanks David, this works great with the last versions, but with the new versions it does not work anymore, someone has an idea or workaround?