Unsolved
2 Posts
0
322
February 21st, 2023 07:00
WMS Groups & Configs wont load after restore
Hello all,
Due a server move, we wanted to move Wyse Management Standard on Prem. to this new server as well.
We backed up the databases on the old server and imported them on the new server.
Unfortunately, the problem is that only the Groups and Configs are not loading on the new server.
The new server is a Windows Server 2019.
Wyse Management Suite V4 is installed.
Is there a solution to display the Groups and Configs again?
Maria, MongoDB and Tomcat Log do not show any errors.
the following solution has also been tried
(https://www.dell.com/community/Wyse-Management-Suite/WMS-Groups-amp-Configs-fails-to-load-after-restore/m-p/7704838/highlight/true#M345) last feedback from DavidPatrickLevett
also updating the configuration UI-Package has not brought a solution
I hope you can help me here
Br
Black_Box
DELL-Scott H
Moderator
•
891 Posts
0
February 21st, 2023 12:00
If it were the memcached error as in the article you shared you would see cache timeouts in the log. Was the original server the same version of WMS, Mongo and Maria as the Target server?
Black_Box1996
2 Posts
0
February 21st, 2023 22:00
how do i enable memcached logging on Windows? Or where can i find the logs from memcached?
the old and the new server were both updated to the latest version, and it was checked if WMS, Mongo and Maria have the same version to prevent compatibility problems.
However, without success.
John harper
2 Intern
•
346 Posts
0
May 8th, 2023 02:00
If your WMS (Warehouse Management System) groups and configurations are not loading after a restore, there could be several reasons why this is happening. Here are some troubleshooting steps you can try:
Check if the WMS service is running: Make sure that the WMS service is running on the server. If it's not running, start the service and try accessing the WMS groups and configurations again.
Check the database connection: If the WMS service is running, check the database connection to ensure that it's functioning properly. Make sure that the database server is up and running and that the correct connection string is specified in the WMS configuration files.