https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODc1IiwiaGFzaCI6IjgzODM0NGVjLTVjNDUtNDg3MC1hZTE4LWI1Yzc0ZGJkMmY0YSJ9
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 |
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.
| KB ID: | 1875 |
| Product: | Veeam Backup & Replication |
| Version: | 7.0.0.764+, 8.x |
| Published: | 2014-04-21 |
| Last Modified: | 2020-08-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
