Troubleshooting Exit Code: -601

Details

Exit Code -601 occurs on backup.

— Windows Edition – log excerpt —
03/21/2018 16:20:55.230 CTrackingDriverCommunicator::SetControlCode(0) failed Level=ERROR [1]
03/21/2018 16:20:55.230 #### ERROR Stop() @ Tracking.cpp(324): -601 Level=ERROR [1]
03/21/2018 16:20:55.230 Leaving CTrackingVolume::InitTracking
03/21/2018 16:20:55.230 #### ERROR tv.InitTracking(bpEx.m_utf8AbsoluteTargetName.ToWide().c_str(), bpEx.m_SrcDisks) @ Tracking.cpp(888): -601 Level=ERROR [1]
03/21/2018 16:20:55.230 #### ERROR InitTracking(bpEx) @ Snapshot.cpp(456): -601 Level=ERROR [1]
...
03/21/2018 16:21:55.257 Call RzmDeleteAllTempCacheFiles
03/21/2018 16:21:55.614 {IDS_STRING3018}Exit Code: -601

Exit Code: -601
The sector tracking driver is not installed

Cause

Windows system doesn't restart after installing ActiveImage Protector.

Resolution

●　ActiveImage Protector 2018 or earlier
Please restart the Windows system.

●　ActiveImage Protector 2022 7.0.0.8643
The tracking driver fails to unload during ActiveImage Protector uninstallation, leading to backup task failures with Exit Code -601.

1) Install ActiveImage Protector 2022 7.0.0.8643
2) Create a task
3) Re-install ActiveImage Protector 2022
4) Restart the Windows system

This issue is fixed with the installer for ActiveImage Protector 2022 7.0.3.8919.

Reinstallation of ActiveImage Protector 2022 is not required after the above step 4).

The program behaves the same as described above when the settings are retained, which means that the first full or incremental backup task that runs will include the difference as a result of a Reconciled task, and the task after will run according to their predefined schedule.

Target Products

・Agent-based
・ActiveImage Protector 2018 ～update6 (5.10.1.6144) or earlier is used
・ActiveImage Protector 2022 7.0.0.8643 is used and Sector Tracking Driver mode is selected
・ActiveImage Protector Windows edition

(2090)

Published: 2018/08/31
Updated:  2024/02/26

(13451126881433)