Vmware enterprise for essential

[EliandroRenato]

Hello, I changed the enterprise vmware host key to the essential kit. Veeam is sending the following message after the exchange.

"Processing 192.168.xx.xxx Error: Failed to open VDDK disk [[datastore1] WebserverLinux_1/WebserverLinux_1.vmdk] ( is read-only mode - [true] ) Logon attempt with parameters [VC/ESX: [192.168.xx.xxx];Port: 902;Login: [root];VMX Spec: [moref=51];Snapshot mor: [51-snapshot-1314];Transports: [nbd];Read Only: [true]] failed because of the following errors: Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}."


I deleted the job, the host from inventory and included again, the error continues.
I went back to the old enterprise key to test it went back to work.


Has anyone ever had this problem?

[Egor Yakovlev]

Hi Eliandro,
I have seen that behaviour with custom-made VMware keys provided from 3rd party resellers. Worth checking under "License-Licensed Features" if Essentials Kit license has "Storage APIs" listed.
Anyhow, VDDK problems can be caused by various reasons and it is best to troubleshoot with support, feel free to open a ticket and share its ID.
Thanks!

[Andreas Neufert]

Check vcenter rights, vmotion the VM to another host and reboot the host.

Work with support on this issue.

[EliandroRenato]

Unfortunately I don't have veeam paid support, I opened a case in support but it ended without response.
The case number is 03880400.
Unfortunately I can not change host machines at this time to do a test.

[wishr]

Hi Eliandro,

What ESXI version is it? I'm asking because it may be that issue.

Thanks.

[Vitaliy S.]

If you are not on maintenance (no support contract), then you can try to resolve this issue by looking through similar existing topics. Thanks!

[EliandroRenato]

Hi Eliandro,

What ESXI version is it? I'm asking because it may be that issue.

Thanks.

Hi Wishr ESXI, 5.1.0 1065491

[wishr]

Then yes, most likely this is a known issue described in the aforementioned KB article (debug logs analysis is required to confirm it). Since you do not have a maintenance contract to download the hotfix there are just two options left: you may upgrade ESXi to a more recent version (5.5, for example), or keep using the enterprise license on your host.

Thanks

[EliandroRenato]

Thank you, will update the HOST then. I'll post if it resolves.

[EliandroRenato]

Hello, I'm going to say that updating EXI to 5.5.0 has solved the problem. I just needed to rescan the host on veeam. Veeam is really the best!