Management server data corruption after migration

After setting up a 2nd management server on a new host and migrating data from the old one, all clients, backup tasks and depots got visible on the new machine.
All clients (same subnet) are shown offline / grayed out. How-To recommends adding clients manually.
- Trying to add Client: Wizard states "Currently added to OLDMACHINE" -> Next
Error: Machine already registred. - Trying to delete Client: Error deleting the machine.
Details:Code: 20.250.646(0x01350016)
<u>Zeileninfo:</u> 0x8D165E86FB819666;
Modul: management_server_vs_50088
Nachricht: Maschine 'C537A424-1B19-4457-89D2-CE7C5A603447' ist nicht in der Synchronisationsdatenbank.Code: 10.289.161(0x009D0009)
<u>Zeileninfo:</u> 0x1E1B8813456776F5;
Modul: management_server_vs_50088
Nachricht: Maschine 'C537A424-1B19-4457-89D2-CE7C5A603447' ist nicht in der Synchronisationsdatenbank.

- Se connecter pour poster des commentaires

Hi Ekaterina,
I ran the script, which returned no errors regarding orphaned clients.
Checking number of unprocessed events > OK Checking event processing speed > OK Checking sync database size > OK Checking DML database size > OK Checking recent errors > WARNING: There are '5' error(s) in AMS log for past week. Checking withdrawn machines > OK Checking orphan machines > OK Checking orphan instance aspects > OK
Do you have an idea, why machines cannot get deleted from the Management server?
- Se connecter pour poster des commentaires

Thank you for feeding back! Looks like the old machine IDs are already in the database, but some entries are lacking and therefore the machines are neither displayed in the UI nor can be added again. In this case you can change the IDs of the machines, so that there is no conflict with the older entries in the database.
But I'd suggest better to set up a new Management Server and then add all machines and plans back. Thus we can make sure the DB is consistent and doesn't hide any issues that can show up later.
- Se connecter pour poster des commentaires