The activity has failed due to a restart of the service.
Acronis Backup 12.5 running on Windows Server 2012 R2 with all Windows Updates.
On a clean hard drive (partitioned, formatted) backup will run maybe for 1 or 2 days and then will fail with this error. In order to get the backup working on this drive again, need to remove all backups from the drive (Format).
I have confirmed the service is running with correct permissions.
Contents of the Activity Log:
2017-07-17 23:00:08:642 6104 I0135003A: User is running command. Command=Backup plan 'KCCHOST'; User=; clientProfileID=; clientSessionID=220CD675-D350-4E78-9FEC-F3C43E061B77
2017-07-17 23:00:10:726 812 I0135003A: User is running command. Command=Backing up; User=; clientProfileID=; clientSessionID=220CD675-D350-4E78-9FEC-F3C43E061B77
2017-07-17 23:00:10:772 812 I00000000: I00000000: Backup Inclusions list:
2017-07-17 23:00:10:773 812 I00000000: I00000000: Data (D:)
2017-07-17 23:00:10:773 812 I00000000: I00000000: Windows Server 2012 R2 (C:)
2017-07-17 23:00:10:773 812 I00000000: I00000000: System Reserved
2017-07-17 23:00:10:774 812 I00000000: I00000000: Archive: F:\KCCHOST\\KCCHOST-F0C65880-3B07-462F-AAA8-A398C59D9880-5D72DC07-D629-463B-B990-A4A3FDEA9E84A
2017-07-17 23:00:11:455 812 I00000000: Using ar_io_local to open '\\?\F:\KCCHOST\' with token 0000000000000000
2017-07-17 23:00:11:483 812 I00000000: Create Full Backup From Disk '1'To file file:F:\KCCHOST\KCCHOST-F0C65880-3B07-462F-AAA8-A398C59D9880-5D72DC07-D629-463B-B990-A4A3FDEA9E84A.tibxCompression NormalExclude Files matching maskMatch criterion *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...Ask for the first media No
2017-07-17 23:00:14:613 812 I000101F8: Pending operation 162 started: 'Saving partition structure (Hard disk 1)'.
2017-07-17 23:00:14:654 812 I000101F8: Pending operation 165 started: 'Creating partition image (System Reserved ())'.
2017-07-17 23:00:25:557 812 I000101FA: Locking partition F:...
2017-07-17 23:02:44:789 812 I000101F8: Pending operation 165 started: 'Creating partition image (Windows Server 2012 R2 (C))'.
2017-07-17 23:10:39:604 812 I000101F8: Pending operation 165 started: 'Creating partition image (Data (D))'.
2017-07-17 23:24:33:792 812 E000101F6: Error 0x101f6: Operation with partition 'F:' was terminated.
|
| trace level: error
| channel: tol-activity#F881F69E-2857-410F-BA3B-C0AB5888B54D
| line: 0xa164035b3ff39298
| file: k:\7048\processor\diskadm\da_commit.cpp:338
| function: DaProcessor::CommitImpl::OnDaError
| $module: disk_bundle_vsa64_7048
|
| error 0x4000d: The file is corrupted.
| line: 0x5ed2d076c4684608
| file: k:\7048\core\resizer\archive3\archive3_api.cpp:50
| function: resizer::Archive3Error
| $module: disk_bundle_vsa64_7048
|
| error 0x70034: data is corrupted: CRC mismatch or internal data structures mismatch
| line: 0x30ba355f9fd4ff2c
| file: k:\7048\core\resizer\archive3\utils.cpp:219
| function: `anonymous-namespace'::ArchiveWriterImpl::Write
| function: archive_stream_write
| code: 0x138b
| $module: disk_bundle_vsa64_7048
2017-07-17 23:24:38:550 6104 E01350001: Error 0x1350001: The activity has failed due to a restart of the service.
| trace level: error
| channel: tol-activity#6AB41555-73DF-4A5F-A1BE-DDBECEF3BE8D
| line: 0x7564da35b0f1eaf2
| file: k:\7048\enterprise\common\tol\activity_workshop.cpp:88
| function: Tol::BaseRepairConditions::Result
| $module: mms_vsa64_7048
2017-07-17 23:24:38:551 6104 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backup workflow
| trace level: error
| channel: tol-activity#6AB41555-73DF-4A5F-A1BE-DDBECEF3BE8D
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_7048
|
| error 0x1490002: Step 'Backup' has failed.
| line: 0x8edc81ea38faba77
| file: k:\7048\enterprise\managers\gtob\backupers\backup_command\impl\backup_workflow_command.cpp:619
| function: `anonymous-namespace'::BackupWorkflowCommand::ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7048
|
| error 0x1350001: TOL: Process 'service_process.exe' has failed.
| line: 0x997a6f2085ead06d
| file: k:\7048\enterprise\common\tol\isolate_command\isolate_command.cpp:79
| function: Tol::`anonymous-namespace'::DisconnectCallback::OnDisconnected
| $module: mms_vsa64_7048
2017-07-17 23:24:38:585 6104 E0135003D: Error 0x135003d: Command has failed. Command=Backup plan 'KCCHOST';
| trace level: error
| channel: tol-activity#6AB41555-73DF-4A5F-A1BE-DDBECEF3BE8D
| line: 0x4a8728dc8a1c95a1
| file: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'KCCHOST'
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'KCCHOST'
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_vsa64_7048
|
| error 0x1330029: Failed to execute the command.
| line: 0xe6792a5ee190de2c
| file: k:\7048\enterprise\managers\gtob\protection\agent_engine\protect_command.cpp:218
| function: `anonymous-namespace'::ProtectCommand::SafeExecute
| $module: agent_protection_addon_vsa64_7048
|
| error 0x1350035: 2 activities have not succeeded. One of them is displayed.
| line: 0x2e7e9e174f1fb719
| file: k:\7048\enterprise\common\tol\replica\event_processor.cpp:110
| function: Tol::`anonymous-namespace'::CreateCumulativeError
| FailCount: 0x2
| $module: agent_protection_addon_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_7048
|
| error 0x1490002: Step 'Backup' has failed.
| line: 0x8edc81ea38faba77
| file: k:\7048\enterprise\managers\gtob\backupers\backup_command\impl\backup_workflow_command.cpp:619
| function: `anonymous-namespace'::BackupWorkflowCommand::ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7048
|
| error 0x1350001: TOL: Process 'service_process.exe' has failed.
| line: 0x997a6f2085ead06d
| file: k:\7048\enterprise\common\tol\isolate_command\isolate_command.cpp:79
| function: Tol::`anonymous-namespace'::DisconnectCallback::OnDisconnected
| $module: mms_vsa64_7048

- Log in to post comments

Has this issue been fixed in the latest update? I'm also getting this same error
- Log in to post comments

Hi Karl,
The current Update 1 (build #7970) addresses most of such problems and if you still have similar symptoms then likely there is a different root cause which needs to be investigated further with our support team involved.
Thank you.
- Log in to post comments