Skip to main content

The operation has been disabled by the guest operating system

Thread needs solution

Hello,

on every backup we have a warning for one specific VM (2008 R2 Domain Controller):

 

E00004E25: Fehler 0x4e25: The operation has been disabled by the guest operating system
| Ablaufverfolgungsebene: Fehler
| Channel: tol-activity#B42F2C9F-FE32-4125-95D2-81A7C55365F5
| Zeile: 0xc61573f663f5d7a4
| Datei: k:\13\enterprise\virtualware\raw\vmware\vixdisklib\vixdisklib.cpp:395
| Funktion: `anonymous-namespace'::LibHolder::PrepareForAccess
| $module: esx_srv_vsa64_7970

 

What does this message mean?

Which operation is disabled?

 

Regards

Dennis

 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dennis,

This error is returned from VMWare VDDK VixDiskLib_PrepareForAccess function which is used to prepare the virtual disks for opening them for read: see https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vddk.pg.doc_50%2FvddkFunctions.6.11.html . In our code this function is normally re-tried several times which is Ok itself (according to Vmware, it's normal to re-try this function until it succeeds), but in your case the unsuccessful attempts seems to be not hidden correctly as they should. We're currently investigating similar report with our support and development teams to figure out why the warning still appears (internal ID: TTASK-20428), so I'd recommended you to submit a support ticket in order to properly track the resolution.

Thank you.

Since two weeks I have the same Problem with Acronis Backup 12.5.
Only one VM, always the same VM. I even cloned the VM to a new one, and resetted CBT Information.

When I start a Full Backup, it starts normal. During the first minutes, the error appears but Backup runs through, apparently normal. All data (several GB seem to be transferred). But the error is still displayed.
So the overall status of the job is failed too.

Is there a fix?

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

The issue is related to particular environment and specifics of VMware VDDK libraries used. The VixDiskLib_PrepareForAccess method disables Storage vMotion operation for VM before backup and if it fails (like in your case), it usually means that the operation is already disabled on VMware vCenter level and cannot be changed - hence the warning. The clear up the warning, there must be changes made to VMware vCenter database (to clean up the flag) or the VM should be re-added to vCenter inventory - see possible solutions in https://kb.vmware.com/s/article/2008957#Manually%20remove%20entries%20from%20the%20vCenter%20Server%20SQL%20database . To properly apply the solutions it makes sense to contact our support team for further assistance with the issue.

Thank you.