Skip to main content

Integration with Acronis 11.7 and vSphere 6.5 error

Thread needs solution
Forum Member
Posts: 26
Comments: 44

This error occurs when working with vsphere using Acronis 11.7.

Environment
 -OS: Windows server 2016
 -Acronis version: 11.7-50230 (Updated from 50088 to July 7th)
 -vshere version: 6.5.0 23000

If Acronis tries to add a VM device, the VM will not be created with the message below.

--------------------
Log entry details
--------------------
Type: Error
Date and time: 2020-07-07 4:16:25 PM
Backup plan: [none]
Operation: [None]
Managed item type: [None]
Managed items: [None]
System: acronismgr02
Code: 14,712,855 (0xE08017)
Module: 224
owner:
message:
  Virtual appliance deployment failed on the following ESX(i) hosts: 172.20.0.97.
Additional information:
--------------------
Error code: 32791
Module: 224
Line information: a20120e20d7da23b
Field: $module: virtual_center_addon_vs_50230
Message: Deployment of the virtual appliance on the following ESX(i) host failed. 172.20.0.97.
--------------------
Error code: 32790
Module: 224
Line information: a20120e20d7da375
Field: $module: virtual_center_addon_vs_50230
Message: Failed to initialize Agent for VMware'AcronisESXAppliance-[2]'.
--------------------
Error code: 163
Module: 83
Line information: be0bf6d9d74ed67
Field: ErrorCode: 14010, ErrorText: There was an error in communication, $module: virtual_center_addon_vs_50230
message:
--------------------
Event code: 0x00E08017+0x00E08016+0x005300A3

--------------------

Exactly, the device added by the user in the VM list is created for a while and then automatically deleted, and fails.

Acronis displays a failure message during the initialization phase.

So I created a VM with acronis OVF file in vsphere.
The VM itself seems to have been created normally. (The management server's IP was also well recognized.)
However, the VM was still not recognized by the Acronis Management Server.

What is the problem and how to solve it?

(If you want, I can provide system information of Acronis management server.)

Thank you.

0 Users found this helpful
Forum Member
Posts: 26
Comments: 44

#1

Additional information.

TCP 902, 443 ports are open.
(Actual equipment and virtual equipment are in the same band, and there is no firewall or security settings.)

Thank you.

Forum Moderator
Posts: 147
Comments: 5427

#2

Hello Lemoning,

am I correct in assuming that you downloaded the Agent from https://kb.acronis.com/content/59602 ? The 64-bit Agent for VMware (Virtual Appliance) is designed for VMware vSphere 6.5 and 6.7. It is provided as a separate .msi file, and can be imported to an ESXi host as an OVF template.

Forum Member
Posts: 26
Comments: 44

#3

Hello Ekaterina.

I just updated to version 11.7_50230 of Acronis.
I have not tried the content of the site https://kb.acronis.com/content/59602.
I will tell you the result after trying it in the way you told me.

I am still working on this issue.
(I pressed the wrong resolution button.)

Thank you.

Forum Member
Posts: 26
Comments: 44

#4

Hello, Ekaterina

I tried it the way you told me, but the problem still persists with the same error.
Is there any other way to solve the problem?

Thank you.

Forum Moderator
Posts: 147
Comments: 5427

#5

Hello Lemoning,

if you have successfully imported the 64-bit appliance as OVF, but appliance registration on AMS still fails with There was an error in communication error, then the issue is likely a general VIX error indicating low-level communication problems between the agent (Acronis Agent) executing the VIX operation and the ESX(i) host (for the error description see VMware KB: Error Codes).

It is most likely caused by the network settings applied to the machine where you are running the installation from which has problems connecting to the ESX(i) host on TCP port 902 and/or 443.

Forum Member
Posts: 26
Comments: 44

#6

Hello Ekaterina.

Ports and firewalls are unrestricted.
I have also tried Acronis -> OVF and OVF -> Acronis.
In addition, I checked the following warning message in the Windows Event Log.

In application-specific permission settings, the CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
And APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
Local Activation permissions for the COM server application are running on the Application Container Not Available SID (Not Available) User at Address LocalHost (with LRPC) ACRONISMGR02\Acronis Agent User SID (S-1-5-21- 1925316828-2663048430-2258886577-1018). You can modify this security right using the Component Services administration tool.

Will this help you solve the problem you are going to tell me?