Acronis 12.0.3689 - Installation 100% - can not be closed - not possible to add Machine (Management Server)
We installed Acronis on 8 different servers. These were physical Windows Server 2008 R2 or Windows Server 2012 R2.
On 2 servers, the installation closes at 100%, but there is no button to complete and close the window. (acronis.jpg) Even after a few minutes wait is nothing. You have to close the window using the task manager.
Only with these two servers (Windows Server 2008 R2) is after successful registration in the management:
"There are no devices to secure"
There is also no way to add it manually.
Add Devices -> Server -> Windows
Adding will eventually terminate with a timeout.
-Trick with hover when adding button - without success
-Acronis Backup 11.7/11.5: Cleanup Utility - without success
(The log file is located in the appendix) (abv64.msi_.zip)
Please support. Many Thanks.
But the option for the host name or the IP address in the installer is only for the backup agent.
Not for the first installation point with the Backup Agent and Acronis Backup Management Server.
If I want to add the IP, instead of the hostname, after installation in the Acronis Management Server, that does not work either.
Hi,
The option to specify the Acronis Management Server (AMS) registration address is available when you run installer locally on the remote machine (which needs to be protected) and install only Agent for Windows/Linux. It's indeed not available when you install both AMS and Agent on the same machine OR when you run remote installation (Devices->Add->Windows Server/workstation - for this scenario we will add a field for AMS registration address in future updates). In other words you need to run the installer executable locally on the affected servers and install only Agent for Windows there and provide the registration address for AMS.
Thank you.
Even if you try to install only the agent in conjunction with another management server, the installation fails.
1: MSIGEN:SendMessageToInstaller: message sent
1: MsiManagedMachineServiceAddMmsToAms: MMS was not added to AMS due to error: Error 0xd2020f: Failed to add the machine to the management server.
| line: 0x851efe822fcbb3fb
| file: k:\3689\enterprise\mms\install\component\custom_dll\main.cpp:779
| function: `anonymous-namespace'::AddToAmsHandler::operator ()
| $module: custom_actions_abv_vsa64_s_3689
|
| error 0xdc0001: The operation has timed out.
| line: 0xeb6e2a6f8b27672b
| file: k:\3689\enterprise\mms\install\component\custom_dll\lib\helper.cpp:91
| function: `anonymous-namespace'::GetHelperResult
| $module: custom_actions_abv_vsa64_s_3689
1: MsiManagedMachineServiceAddMmsToAms: Execution failed with error: Error 0xd2020f: Failed to add the machine to the management server.
| line: 0x851efe822fcbb3fb
| file: k:\3689\enterprise\mms\install\component\custom_dll\main.cpp:779
| function: `anonymous-namespace'::AddToAmsHandler::operator ()
| $module: custom_actions_abv_vsa64_s_3689
|
| error 0xdc0001: The operation has timed out.
| line: 0xeb6e2a6f8b27672b
| file: k:\3689\enterprise\mms\install\component\custom_dll\lib\helper.cpp:91
| function: `anonymous-namespace'::GetHelperResult
| $module: custom_actions_abv_vsa64_s_3689
1: MsiManagedMachineServiceAddMmsToAms: succeeded
Hi Hendrik,
The last symptoms indicate problems with the installation sequence - it may happen if v12 was installed, then uninstalled without checking "clean up configuration data" option and then there was 11.7 installed. This would break future installation of v12 on this machine. Still in your case the exact root cause might be different, so I'd recommended to contact our support team for thorough investigation - we'll need to check the current setup, e.g. where the agents are installed, where the AMS is running, what was the history of the setup, the current logs on AMS side, etc.
Thank you.