Backup client installation failed


Kaseya Backup client installation fails



  • Acronis installer may have failed to download to agent
  • The Acronis installation may have failed
  • The installation could not be verified due to Acronis disk driver issue
  • There may have been an error in the Kaseya agent procedures which manage the installation process



To isolate the exact cause and find a solution, complete the following troubleshooting steps: -

1) attempt to verify again using Backup > Install/Remove > Verify button (in some cases the initial verification, which follows reboot, fails because not all the Acronis services have started yet)
2) review the Agent Procedure log from the installation attempt. The sequence of procedures should be similar to the below screenshot. Check if any of the procedures have failed and review any error messages
3) If the procedures appear to have completed without any problems, the next step is to review the Acronis log files. The installation includes 4 Acronis modules, and the logs created in the agent working directory (c:\kworking by default).
  • Acronis Agent Core - backupAgentCoreInstallLog.txt
  • Acronis Agent for Windows - backupAgentWindowsInstallLog.txt
  • Acronis Command Line Tool - backupCommandLineToolInstallLog.txt
  • Acronis Management Console (optional component) - backupManagementConsoleInstallLog.txt

The modules are installed in the order listed above. Kaseya will report the installation as failed if the first 3 are not successfully installed.



4) Open each of the logs and check the summary at the bottom  to see if it installed successfully or not. It should look like this: -

MSI (s) (7C:20) [13:11:54:247]: Product: Acronis Backup & Recovery 11.5 Agent Core -- Installation completed successfully.

MSI (s) (7C:20) [13:11:54:247]: Windows Installer installed the product. Product Name: Acronis Backup & Recovery 11.5 Agent Core. Product Version: 11.5.37977. Product Language: 1033. Installation success or error status: 0.

=== Logging stopped: 31/01/2014 13:11:54 ===

If the install logs appear to show a successful installation, it is possible that Acronis installation completed successfully but Kaseya was unable to verify the install. In this case, proceed to step 7.
Search the log file top-down for the first instance of the string “return value 3” (please note, the string may appear several times in the log). If you do not find “return value 3”, search again for “rollback”. Review the preceding 10-20 rows of the log before “return value 3” or “rollback”, as described in this Acronis KB article -
5) Review the “Solution” section of the Acronis article and look for an example that matches the data in your log
6) If you find an example in the article which closely matches the data found in the log, gather the requested diagnostic data or follow the recommended solution and attempt the installation again
7) open services.msc and check that "Acronis Managed Machine service" is running. If not, try to start it and capture any on-screen error message.
If it fails to start due to logon failure, refer to this article -
8) run the following command from Windows command shell: -
acrocmd list disks
Capture the output (it should display a list of disks and partitions in the system).
9) ensure that Microsoft .NET Framework 3.5.1 is installed. If not, install it and then try to "verify" the installation again from Install/Remove page.
10) gather the following logs from the Kaseya Agent installation directory (usually something like C:\Program Files (x86)\Kaseya\KSAASC18937046962040): -
  • agentmon.log
  • kdllhost.log

If unable to find a solution after performing the above steps, please create a support ticket and include the following information: -

  • screenshot of the Backup > Install/Remove page showing the installation status
  • screenshot showing agent procedure log from the time the install was started to the time it failed (or the current time if it is still pending)
  • Acronis installation logs referenced in step 3 above
  • output from Acronis info tool (
  • details of any solutions attempted from the Acronis KB #1647 (as per step 4 in the "solution" section above) - if installation was retried, ensure you provide the logs from the most recent attempt
If Acronis was installed successfully, but Kaseya reports failed status: -
  • is Acronis Managed Machine service started? If not, what happens when trying to start it?
  • output from "acrocmd list disks" command (as per step 8 above)
  • Kaseya Agent logs referenced in step 9 above



Kaseya VSA (Backup module) - v6.5 and above

Have more questions?

Contact us

Was this article helpful?
0 out of 1 found this helpful

Provide feedback for the Documentation team!

Browse this section