- Knowledge Base Listing Page
- Failed to open VMDK. ESXi 5.5 and Veeam 7.0.0.764+
Failed to open VMDK. ESXi 5.5 and Veeam 7.0.0.764+
| KB ID: | 1875 |
| Product: | Veeam Backup & Replication |
| Version: | 7.0.0.764+, 8.x |
| Published: | 2014-04-21 |
| Last Modified: | 2020-08-13 |
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
After updating Veeam or VMware such that a combination of ESXi 5.5 and Veeam 7.0.0.764 or higher exist within the environment, the jobs fail with error “Failed to open VMDK” and/or “Host not licensed for this feature.” The job will successfully download the VMX, VMXF, and NVRAM, but will fail on the VMDK.
In Veeam Backup & Replication v8 this issue appears with the error “Failed to create processing task for VM <vmname> Error: Cannot access VMX file of VM ‘<vmname>’” and “Task failed Error: Cannot access VMX file of VM ‘<vmname>’”
In Veeam Backup & Replication v8 this issue appears with the error “Failed to create processing task for VM <vmname> Error: Cannot access VMX file of VM ‘<vmname>’” and “Task failed Error: Cannot access VMX file of VM ‘<vmname>’”
Cause
This has to do with a change in how VDDK was utilized after 7.0.0.764 within Veeam when interacting with ESXi 5.5.
Solution
Solution 1:
To identify if this KB is relative to the issue you are having, please perform the following.
1. Connect with a vSphere Client to the VC using the same credentials used to add the VC in Veeam.
2. Click the VC name at the top of the tree on the left side of the vSphere Client.
3. Click Permissions. If you find that the list is empty as shown below, this KB may provide resolution.
To resolve this issue, please add the account being used by Veeam as an Administrator within the permissions section at the VC level. (For granular permissions please see the more information section of this KB.)
Solution 2:
1. Connect to the vCenter server via a vSphere Client.
2. Open vCenter Server Settings…
3. Review the list of License Keys and remove any that are unused or expired.
To identify if this KB is relative to the issue you are having, please perform the following.
1. Connect with a vSphere Client to the VC using the same credentials used to add the VC in Veeam.
2. Click the VC name at the top of the tree on the left side of the vSphere Client.
3. Click Permissions. If you find that the list is empty as shown below, this KB may provide resolution.
To resolve this issue, please add the account being used by Veeam as an Administrator within the permissions section at the VC level. (For granular permissions please see the more information section of this KB.)
Solution 2:
1. Connect to the vCenter server via a vSphere Client.
2. Open vCenter Server Settings…
3. Review the list of License Keys and remove any that are unused or expired.
More information
If the “Add Permissions” option is greyed out when you attempt to add the account as an Administrator at the VC level please use a different account. (The local Administrator account of the VC will most likely work best.)
For information regarding granular permissions for the account used by Veeam with the VMware environment, please review the following document:
http://www.veeam.com/veeam_backup_7_0_permissions_pg.pdf
See VMware KB kb.vmware.com/kb/2063054 for a list of changes made to modified permissions in newer versions.
For information regarding granular permissions for the account used by Veeam with the VMware environment, please review the following document:
http://www.veeam.com/veeam_backup_7_0_permissions_pg.pdf
See VMware KB kb.vmware.com/kb/2063054 for a list of changes made to modified permissions in newer versions.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.