Ask the Community
Groups
Backup process was interrupted and did not complete - Connect IT Community | Kaseya
<main> <article class="userContent"> <h3 data-id="problem">Problem</h3> <p>Backup fails - "Backup process was interrupted and did not complete"</p> <h3 data-id="cause">Cause</h3> <p>The error may be caused by either of the following: -</p> <ul><li>the backup process was killed by a user or another application</li> </ul><p>OR</p> <ul><li>Kaseya monitor set failed due to WMI error (in this case the backup is falsely reported as "failed" when it is actually still running)</li> </ul><h3 data-id="solution">Solution</h3> <p>Use the following steps to troubleshoot the issue: -</p> <p>1) check if <em>kaseyabackupcmd.exe</em> process is running on the Backup agent machine</p> <p>2) capture the Acronis log from the Kaseya agent working directory (by default, c:\kworking): -</p> <ul><li> <strong>volBackupLog.XML</strong> for volume backups</li> <li> <strong>folderBackupLog.XML</strong> for folder backups</li> </ul><p>3) open the XML file using a <em>text editor</em> (e.g. notepad++) - scroll to the bottom and check the progress.</p> <p>Depending, on the process status and log content, proceed as follows: -</p> <h4 data-id="the-process-is-not-running-and-log-appears-to-be-incomplete-does-not-show-completion-status">The process is not running and log appears to be incomplete (does not show completion status)</h4> <p>A user or another program killed the backup before it had completed.</p> <h4 data-id="the-process-is-still-running-or-the-log-shows-that-it-completed-whether-successful-or-failed">The process is still running, or the log shows that it completed (whether successful or failed)</h4> <p>Continue troubleshooting using these addtional steps: -</p> <p>4) open the Kaseya Agent service log, which can be found in the agent installation directory (by default, C:\Program Files (x86)\Kaseya\<serverID>\agentmon.log)</p> <p>5) look for an error like this at the time that Kaseya reported the backup as failed: -</p> <p> </p> <blockquote class="blockquote"> <p><em>2015/02/16 03:03:31.143 [4890]: Failed to connect to WMI server with error 0x8004100e. </em><br><em>2015/02/16 03:03:34.462 [4b90]: Remove monitor set: \KPROC$1.xml: Process ID=1, ProcessName=KaseyaBackupCmd.exe, AlarmOp=2, AlarmThreshold=0, AlarmDuration=0, Rearm=0</em></p> </blockquote> <p> </p> <p>6) if error refers to WMI (a Windows component), address the problem to Microsoft support team or reinstall the operating system</p> <ul><li>in some cases, <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fblogs.technet.com%2Fb%2Faskperf%2Farchive%2F2009%2F04%2F13%2Fwmi-rebuilding-the-wmi-repository.aspx">rebuilding WMI repository</a> will resolve such errors</li> </ul><h3 data-id="related-articles">Related articles</h3> <p><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.zendesk.com%2Fentries%2F93837968-WMI-error-0x80041013-causes-monitoring-of-backups-to-fail">WMI error 0x80041013 causes monitoring of backups to fail</a></p> <h3 data-id="applies-to">Applies to</h3> <p>Kaseya VSA (Backup module) - all versions</p> </article> </main>