Skip to main content

Failed to run the task with ID '#####' (internal run). (solved)

Thread needs solution

Hello Acronis Team,
Hello Acronis Users,

since 9th February the Backups of my servers running without error. I've changed nothing (I know how it sounds) and suddenly vmProtect can't create Backups anymore (started 21. March). My support run out on 25. March, so I'm posting it in the forums. I want to solve this problem, and not recreate the tasks again. In the attachment the compressed log.xml.

My guess is (pointing in the dark) the exchange database. But the edb seems ok.

Environment:
Server SV-01-SBS
* Microsoft Small Business Server 2012 (Build 7601)
* Microsoft Exchange 2010 (14.0.100.0) / Exchange Status Log in attachment

vmProtect is a virtual application on a vSphere 5.1

Best regards

Attachment Size
log.zip 78.46 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

From what I can see the issue here is interaction with the VMware tools which is required for Exchange-aware backup processing:

C600A9D0-3A63-4089-9ED7-3F30D4D29BEE'.
--------------------
Error code: 139
Module: 83
LineInfo: 8551c5c00e774fa9
Fields:
Message: Failed to process guest api call of 'ListProcessesInGuest'.
--------------------
Error code: 257
Module: 83
LineInfo: 8551c5c00e774fcc
Fields: faultTypeId : 140
Message: SOAP fault code: '12', Description: 'The guest operations agent could not be contacted.', Detail: 'No details.'
--------------------" j="0000000E" tm="24/03/13 23:22:59.739" tp="E"/>

Note the bottom error 'The guest operations agent could not be contacted.' which is thrown by VMware API when trying to call 'ListProcessesInGuest' function. In general this issue is related to VMware Tools service state inside the backed up Exchange VM, so first of all it makes sense to restart the VMware Tools services and then see if the problem still persists.

You can check the details of this issue in this post where this problem is pretty good described: http://alpacapowered.wordpress.com/2012/12/03/invoke-vmscript-issue-the…

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

Hello Vasily,

thank you for the Support. After an update of VMWare Tools this event never triggered again after four weeks constant testing.

Thread can be closed as fixed.

Best regards.