VMProtect 9 Backup Crash

Hi Bitbieger,

It appears that the VMware Tools were installed without the VSS components. Can you please check the 3rd solution from http://kb.acronis.com/content/31347 article. Have you tried to apply it in order to register the required COM+ components? There must be VMware Snapshot Provider COM+ component as well as the service with the same name present in the guest OS of the VM.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hallo,
alles sieht aus und läuft, siehe Screenshot, bei allen anderen Servern auf der selben ESX Maschine (5.1) funktioniert alles gut.
Habe das ganze noch einmal deinstalliert und beim Boot installieren lassen.
Leider immer noch das gleiche Problem. den Artikel http://kb.acronis.com/content/31347 habe ich schon gesehen und durchgeführt kein Erfolg
Grübel Grübel

Thanks and regards
Dirk

@OK nach einem neuen Test (jetzt geht gar nichts mehr) kann auch die VM keinen Snapshot mehr durchführen:
"Diese virtuelle Maschine kann nicht stillgelegt werden, da VMware Tools zurzeit nicht verfügbar ist." Es sieht aber so aus als ob alle Tools laufen

Hi!

First of all you should uninstall the Acronis vmProtect Backup Agent from the VM, since this agent is applicable to Windows 2008+ only (to avoid UAC limitations). The next thing to check is to verify whether the COM+ registry keys are present in Windows registry - you can check the exact GUIDs which we search for in registry in the attached screen shots (to copy-paste these GUIDs in your VM to search through registry) - these screen shots are from Win7, but the GUIDs and location of the required components is the same for Win2k3 also.

Another thing to note is that VMware Tools must be installed in Interactive mode (unattended installation will not install VSS components by default).

Can you please check the registry searching for the keys shown on the screen shot and let me know if they are discovered under HKLM\Software + HKLM\System keys?

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi,
ok i found both Keys on different Points. Under HKLM/System both Keys missing.
Deinstall vmprotect Backup Agent, and checkd the install VM VSS Looks installed
OK Snapshot from VM Client now working "Stilllegen des Gastsystems..." funktioniert wieder.
Backup Vmprotect still not work

Regards Dirk

new Error Log
Task 'server' fehlgeschlagen: 'Erstellen eines Backups fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 3
Module: 435
Zeileninfo: 555b5abba0950337
Felder:
Nachricht: Erstellen eines Backups fehlgeschlagen.
--------------------
Fehlercode: 32786
Module: 114
Zeileninfo: 28314c961de7d337
Felder:
Nachricht: Vorbereitung auf das Backup fehlgeschlagen.
--------------------
Fehlercode: 353
Module: 149
Zeileninfo: a71592046cb2c5f6
Felder:
Nachricht: Backup der Gruppe fehlgeschlagen.
--------------------
Fehlercode: 2
Module: 218
Zeileninfo: 338a407ad20e0987
Felder:
Nachricht: Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
--------------------
Fehlercode: 2002
Module: 538
Zeileninfo: 2a7f716abaaab050
Felder:
Nachricht: Beim Laden der Applikationen über den VM-Proxy ist ein Fehler aufgetreten.
--------------------
Fehlercode: 239
Module: 83
Zeileninfo: b7e5b06ccbf4eabf
Felder:
Nachricht: Ausführen des Agenten 'cscript /NoLogo GuestAgent.vbs' mit den Parametern '{ }' fehlgeschlagen.
--------------------
Fehlercode: 240
Module: 83
Zeileninfo: a83807079d0431a
Felder:
Nachricht: Ausführung des Skripts 'cd "C:\DOKUME~1\xxx~1\LOKALE~1\Temp\51BA90B0-6285-4A14-99B2-CDFD264F6466\" && cscript /NoLogo GuestAgent.vbs >3D8EBC04-F15D-4D5A-A1A9-4F0A72E1712D' fehlgeschlagen.
--------------------
Fehlercode: 139
Module: 83
Zeileninfo: 8551c5c00e774fa9
Felder:
Nachricht: Gast-API-Aufruf von 'ListProcessesInGuest' kann nicht verarbeitet werden.
--------------------
Fehlercode: 257
Module: 83
Zeileninfo: 8551c5c00e774fcc
Felder: faultTypeId : 140
Nachricht: SOAP-Fehlercode: '12', Beschreibung: 'Der Agent des Gastbetriebssystems konnte nicht kontaktiert werden.', Detail: 'Keine Details.'
--------------------'.

Hi!

Now it's a different issue which is unrelated to snapshot (which seems to work fine), but still it is related to VMware Tools functionality. The VMware Tools are failing with error http://www.vmware.com/support/developer/converter-sdk/conv50_apireferen… while trying to process the standard "ListProcessesInGuest" command from vSphere API (http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.wssdk.a…).

In order to confirm this you can check the hostd.log from the underlying ESXi host where the affected VM resides and you should find the following (or similar) entries:
--------
2013-08-07T12:25:25.207Z [FFD81B90 info 'Vimsvc.TaskManager' opID=d2e856bf-64] Task Completed : haTask--vim.vm.guest.ProcessManager.listProcesses-341703504 Status error
2013-08-07T12:25:25.208Z [FFD81B90 info 'Solo.Vmomi' opID=d2e856bf-64] Activation [N5Vmomi10ActivationE:0xb33fd88] : Invoke done [listProcesses] on [vim.vm.guest.ProcessManager:ha-guest-operations-process-manager]
2013-08-07T12:25:25.208Z [FFD81B90 verbose 'Solo.Vmomi' opID=d2e856bf-64] Arg vm:
--> 'vim.VirtualMachine:5'
2013-08-07T12:25:25.208Z [FFD81B90 verbose 'Solo.Vmomi' opID=d2e856bf-64] Arg auth:
--> (vim.vm.guest.NamePasswordAuthentication)
{ --> dynamicType = , --> interactiveSession = false, --> username = "domain\administrator", --> password = (not shown), --> }

2013-08-07T12:25:25.208Z [FFD81B90 verbose 'Solo.Vmomi' opID=d2e856bf-64] Arg pids:
--> (long) [
--> 1364
--> ]
2013-08-07T12:25:25.208Z [FFD81B90 info 'Solo.Vmomi' opID=d2e856bf-64] Throw vim.fault.GuestOperationsUnavailable
2013-08-07T12:25:25.208Z [FFD81B90 info 'Solo.Vmomi' opID=d2e856bf-64] Result:
--> (vim.fault.GuestOperationsUnavailable)
{ --> dynamicType = , --> faultCause = (vmodl.MethodFault) null, --> msg = "", --> }
--------

There was such issue in earlier builds of ESXi 5.1 and according to https://communities.vmware.com/thread/345460?start=15&tstart=0 the problem is fixed in ESXi 5.1 Update 1 .

If that doesn't help then I'd recommended contacting VMware showing the hostd.log from the ESXi host with the above quoted message to figure out why standard API request doesn't work.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Konnte nur folgenden Eintrag finden:

--> (vim.vm.guest.NamePasswordAuthentication)
{ --> dynamicType = , --> interactiveSession = false, --> username = "domain\administrator", --> password = (not shown), --> } and

vim.vm.guest.ProcessManager.listProcesses- Error
776403
2013-10-15 00:10:19.583 +0200
29CBEB90 info 'Vimsvc.TaskManager' opID=2c51d848-a0
Task Completed : haTask--vim.vm.guest.ProcessManager.listProcesses-499641003 Status error

allerdings haben mir die Infos auf Seiten VM nicht wirklich geholfen, von 8 Servern alle im gleichen ESX und einer will nicht :-(

installiert ist ESXI 5.1 Build 1157734

Hi,

There should be also "vim.fault.GuestOperationsUnavailable" entry in the hostd.log which uniquely identifies the "guest operations agent could not be contacted" error (which causes the "vim.vm.guest.ProcessManager.listProcesses" failure). It makes sense to check with VMware how to address this issue, since it's standard API request which is failing and looks like its not completely fixed even in the latest ESXi 5.1 update which you use.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hallo Vasily,

ja jetzt wird es etwas komisch found Result:
--> (vim.fault.GuestOperationsUnavailable) {
--> dynamicType = ,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
--> }
OK aber auf dem Server laufen 8VM Guests only one not working, :-(

Hallo Vasily,

ja jetzt wird es etwas komisch found Result:
--> (vim.fault.GuestOperationsUnavailable) {
--> dynamicType = ,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
--> }
OK aber auf dem Server laufen 8VM Guests only one not working, :-(

Hallo,

nach einigen Tagen Test und Mailverkehr höre ich vom VM Support bei uns ist alles OK, da ja ohne VMprotect alles fehlerfrei funktioniert auch VSS.
Tja von Acronis höre ich das gleich nun stellt sich mir die Frage wer sich diesem Problem annimmt, oder ob man hier als Kunde alleine gelassen wird.
Nach langem basteln landen wir immer bei folgendem Fehler:
--------------------
Fehlercode: 3
Module: 435
Zeileninfo: 555b5abba0950337
Felder:
Nachricht: Erstellen eines Backups fehlgeschlagen.
--------------------
Fehlercode: 32786
Module: 114
Zeileninfo: 28314c961de7d337
Felder:
Nachricht: Vorbereitung auf das Backup fehlgeschlagen.
--------------------
Fehlercode: 353
Module: 149
Zeileninfo: a71592046cb2c5f6
Felder:
Nachricht: Backup der Gruppe fehlgeschlagen.
--------------------
Fehlercode: 2
Module: 218
Zeileninfo: 338a407ad20e0987
Felder:
Nachricht: Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
--------------------'.

System VcenterServer 5.5 / Vsphere Server 5.1 letztes Build

Hi!

The quoted error is too common unfortunately and doesn't reveal the actual issue - there should be more errors higher in the log file which are causing this final one. Have you tried contacting our support team regarding the issues?

On our side we were also investigating the "vim.fault.GuestOperationsUnavailable" VMware Tools failure in the past few weeks and in one case it was solved by running Windows native backup inside the Exchange VM which truncated the logs. What happens is that the VMware Tools are performing actions which require guest OS resources inside the VM and while Exchange machines are pretty full on RAM, quite often it's consumed nearly by 100% which means that VMware Tools don't have enough resources to run. In order to confirm it you can check the memory consumption in Task Manager inside the guest OS while tyring to run application-aware backup of it.

Note however that the last quoted error should be investigated first (getting the full log will be most helpful here).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi Bitbieger, I was just looking into this. Were you able to find work around for this yet?