We currently have Dell WMS Standard Edition installed on a Windows Server 2012 Virtual Machine.
I want to install it on Windows Server 2019 on a new server.
WMS was in 1.4.1 version so I first updated it to 2.1 on the 2012 VM. Then I installed and configured WMS 2.1 on Server 2019. After that, I saved and restored the DB from one server to the other using Dell documentation (Deployment Guide).*
So on the new WMS configurations and devices are listed and it’s fine.
But then I want to change the WMS server used by a thin client : when I manually change the server path on a Wyse (Wyse 3040 ThinOS 8.6_412) the new WMS is found, the Wyse reboots, but then I get an error “7700 sub error code 172” or “7700 sub error code 115”
The “checkin” therefore works since my Wyse appears and is updated on the new WMS server. But the configuration is not loaded and we cannot send commands to the Wyse.
I noticed this error has already been encountered and tried a few solutions.
I tried a Test-NetConnection on port 1883 (MQTT) : it works, so apparently no MQTT problem.
I tried to deactivate IPV6 on the network card : it did not improve things.
I guess I’m not the only person who wants to update Windows on my server, so I guess it’s possible, and I guess it’s possible to recover the database as well, and not have to redo all policy configurations …
Do you have a lead?
Thank you in advance
* As the save/restore commands mentioned in the documentation didn’t work properly, I had to research and adapt them. If anyone is interested please tell me so that I will post the commands that worked in my case.
This topic was modified 3 weeks, 4 days ago by nico_cepo.