AMS: Löschen der Maschine fehlgeschlagen
Liebes Forum,
ich kann die Maschine nicht löschen, weil sie wurde aus VMWARE gelöscht ?
Hintergrund:
(Eine Test Umgebung)
VMWARE 5.5 Vsphere
Server 20012 (ohne R2)
ABR 11.5 ADV Vir.
könnt ihr mir helfen ohne das ich AMS neu machen muss?
Lg Martin
------------------------------------------------------------------------------------------------------------------------------
Fehler
------------------------------------------------------------------------------------------------------------------------------
Löschen der Maschine fehlgeschlagen.
------------------------------------------------------------------------------------------------------------------------------
Details:
Code: 20.250.646(0x01350016)
<u>Zeileninfo:</u> 0x8D165E86FB8195FF;
Modul: management_server_vs_43994
Nachricht: Behandlung des Ereignisses fehlgeschlagen.
Code: 8.650.756(0x00840004)
<u>Zeileninfo:</u> 0x881FF98A29A31499;
Modul: management_server_vs_43994
Nachricht: Behandlung des Ereignisses fehlgeschlagen.
Code: 8.324.081(0x007F03F1)
<u>Zeileninfo:</u> 0xC131F5921FF77357;
Modul: management_server_vs_43994
Nachricht: Die Schlüsselspalteninformationen sind ungenügend oder inkorrekt. Es sind zu viele Zeilen vom Update betroffen.
------------------------------------------------------------------------------------------------------------------------------

- Log in to post comments

Hallo, wir haben nun das gleiche Problem mit der Version 11.7 Build 44411.
Modul: management_server_vs_44411
Nachricht: Die Schlüsselspalteninformationen sind ungenügend oder inkorrekt. Es sind zu viele Zeilen von der Aktualisierung betroffen.
Ereignis-Code: 0x01350016+0x00840004+0x007F03F1
Gibt es schon einen Lösung?
Wie kann das repariert werden?
Danke.
- Log in to post comments

Hi Sanches,
There is a solution for this problem, but it involves multiple manual querries to be executed against AMS database via MS SQL Management Studio. I'd strongly recommended doing it only with help from our support team as otherwise it may lead to database corruption.
Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager
- Log in to post comments

Vasily wrote:Hi Sanches,
There is a solution for this problem, but it involves multiple manual querries to be executed against AMS database via MS SQL Management Studio. I'd strongly recommended doing it only with help from our support team as otherwise it may lead to database corruption.
Thank you.
Thank you for pointing this out. The team of Acronis experts could repair via TeamViewer and MS SQL Management Studio my database.
But there remains a bitter aftertaste...
Is it not possible to fix this error? It is rare, but the errors should be caught already in the server.
Thank you for the fantastic support!
- Log in to post comments

Hi Sanchez,
Thank you for the update. The root cause of this issue is already fixed in the product code, but it may still appear when updating/upgrading from previous versions of Acronis Backup. It should be gone completely in the next version v12 which we're starting Beta program for during the next week (there will be an e-mail notification sent to all existing Acronis Backup customers about beta availability).
Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager
- Log in to post comments