Failed to deploy virtual appliance
Hello. When installing the virtual appliance I'm getting several errors. I've looked in the knowledge base, but couldn't find anything about them there. In the vCenter server I can see that the appliance is added, but it gets removed as the errors appear.
Code: 014712855
Line tag: 0xa20120e2d7d9ec7
Message: Failed to deploy the virtual appliance on the following ESX(i) hosts: 10.1.60.43.
Suberror
Code: 014712869
Line tag: 0xdabde4d0bc9512f5
Message: Agent initialization failed.
Suberror
Code: 05439651
Line tag: 0xbc190fbcd6b295fa
Message: Failed to resolve host
http://kb.acronis.com/errorcode/
Event Code: 0x00E08017+0x00E08025+0x005300A3

- Log in to post comments

Hello Nils,
Thank you very much for your posts.
To localize the issue, could you please check the following:
1. Is IPv6 enabled?
2. Please use another machine to deploy the virtual appliance (if possible)
3. From the machine with the issue, can you access the host through the vSphere client?
Looking forward to your reply and if you have additional questions please let me know.
Thank you.
- Log in to post comments

I have same problem. I'm using vmware 5.1
and.
1. Is IPv6 enabled? disabled
2. Please use another machine to deploy the virtual appliance (if possible) i tried another machine
3. From the machine with the issue, can you access the host through the vSphere client? i can connect with vsphere client.
Please inform
- Log in to post comments

Hello Murat,
Thank you for your post and welcome to the forum.
Currently there is no support for VMware 5.1 in vmProtect 7. We are going to address this issue in vmProtect 8, most likely in the next update after the initial release. We are very sorry for any inconvenience.
Please let me know if you have additional questions.
Thank you.
- Log in to post comments

Hello!
Same problem.
ESXi 5.1
Acronis VMProtect 8.0 (8128 Russian)
IPv6 Disabled
I can connect with vSphere client.
Log attached.
Let me know if you need additional information.
Thanks.
- Log in to post comments

The problem is solved.
The name of a virtual network in ESXi was in Russian.
Renaming on English helped.
- Log in to post comments

I didn't even know that the name itself would cause this issue. But thanks for sharing this. I'll be aware once I get this issue.
- Log in to post comments