These error codes are listed in the SyncBack help file under the section Technical Reference -> Command Line Parameters.
When running SyncBack from the command line, a batch file, etc. then it will return an exit code that gives an indication of whether the task was completed successfully or not. As a number of tasks can be done via the command line at the same time, e.g. import a profile, run it, then delete it, the exit code relates to the last task done on the command line. Also note that if a group profile is run then the exit code is undefined. In the list below, the second column, e.g. 0xFFFFFF97, is what the Windows Task Scheduler will show in the Last Result column. Where it helps, links to articles and help topics that explain how to fix the problem are included.
0 |
| Success, no error. |
100 |
| SyncBack did not close because of user interaction or the -donotexit parameter was used |
-100 | 0xFFFFFF9C | The -countdown parameter was used and the user aborted it |
-101 | 0xFFFFFF9B | An attempt was made to import a profile from the command line and it failed See: A profile with that name already exists, Invalid Profiles, The security settings for this user do not allow for this action |
-102 | 0xFFFFFF9A | The -export parameter was used and a profile export failed See: Exporting and Importing Profiles, The security settings for this user do not allow for this action |
-103 | 0xFFFFFF99 | The -delete parameter was used and the profile failed to be deleted See: Common Errors and What They Mean ("You cannot delete the profile because it is currently running"), The security settings for this user do not allow for this action |
-104 | 0xFFFFFF98 | The user aborted the profile run |
-105 | 0xFFFFFF97 | The profile name given does not exist See: SyncBack will not run with Scheduler, Scheduled Tasks not running when using System or Service account |
-106 | 0xFFFFFF96 | The profile was not run because it is disabled See: Profiles Pop-Up Menu (Enable) |
-107 | 0xFFFFFF95 | The profile run failed (note that the result of a group profile run is unknown). Check the log for details. See: Viewing a profile log, Common Errors and What They Mean |
-108 | 0xFFFFFF94 | An attempt was made to import a script from the command line and it failed See: Scripting |
-109 | 0xFFFFFF93 | An attempt was made to synchronize with the SBM Service from the command line and it failed |
-110 | 0xFFFFFF92 | The serial number is invalid or the evaluation period has expired See: My serial number does not work, Explain the trial versions |
-111 | 0xFFFFFF91 | SyncBack is being run from an external drive and there is no write access to the folder SyncBack is being run from See: Running SyncBack from an external storage device (No Install Version) |
-112 | 0xFFFFFF90 | An encryption key is being used but it cannot be loaded or is corrupt See: Encryption overview, Global Settings (Encryption) |
-113 | 0xFFFFFF8F | The Ransomware Protection failed See: Common Errors and What They Mean ("Ransomware detection halted the backup"), Ransomware detection with SyncBack |
-114 | 0xFFFFFF8E | SyncBack is being run by the Windows Administrator Protection administrator account and cannot use your settings See: Administrator Protection, Windows Administrator Protection |
-115 | 0xFFFFFF8D | The -compilescript parameter was used and the script failed the compile (syntax) check (SyncBackPro only) See: Scripting |
-116 | 0xFFFFFF8C | The profile was not run because it can only be run as part of a group or group queue (see Profile Setup > When > Group Only). New in V12.1.26.0. See: Group Queues (Profiles That Only Run as Part of a Group) |