AOMEI Backupper Error Code
General Error Codes
Q: Information code 4098: Invalid parameter.
Solution: Please try to recreate the backup task to run again.
Q: Information code 4099: Uninitialized component or function cell.
Solution: Please try to rerun AOMEI Backupper and do the operation again. If you are restoring from DVDs with the error, please copy image files from DVDs to a local folder, and then select backup from the local folder to restore again.
Q: Information code 4101: Failed to create file.
Solution:
1) Please first check if ABCore.exe is prevented by your antivirus software. You can run ABcore.exe (under the installation directory of AOMEI Backupper) as an administrator to check if it can run successfully. Or, antivirus software(such as Windows Defender) will prompt that the program is prevented (please allow it).
2) If the destination is a local path, please check if the destination path has "System" permission. If not, please add "System" permission for your destination path and retry. Right-click the destination partition, and select "Properties"-"Security" tab to add "System" permission.
3) If the destination is a shared path, please also check and add the "System" permission for the shared location on the target computer. And, please also check if the number of users shared simultaneously in the shared folder has reached the limit. We suggest that you set the number of users shared simultaneously to 20(default).
4) If the destination is a NAS device, please confirm the account that is used to access the NAS Path has read/write permission. You can press Win+R， and then type into the NAS path to open, and check if you can open and copy files to the destination NAS folder. And, we suggest that you add the NAS or shared network path under Tools--Storage Management of AOMEI Backupper and select the added path as the destination.
If the login credentials or IP address of the network path have been changed, please delete NAS.xml under C:\ProgramData\AomeiBR, and re-add the NAS via the IP address way under Storage Management.
5) If the destination is an external drive, please check if the external drive is disconnected or its' drive letter is changed when you do the backup. Please reconnect the external drive with the same drive letter as the target path of the backup task, then back up again.
Click here to learn more details.
Q: Information code 4102: Failed to read file.
Solution:
1) If you get this error when performing a system/partition/disk backup with the “Check Image” option selected, please do not worry. Because the error is not related to the backup process, the backup actually is completed. The error is shown during the checking image process, it might be that the backup image file failed to be immediately released after backup is completed. You can separately check the image file via Tools--Check Image.
2) If you get the error during the file backup process, it might be that our program can't access some source files due to permission, program occupation, or some unknown reasons. Please close all running applications and then run the backup again.
Note: If you are backing up Onedrive files or other cloud files, please confirm that these files are synced to the local cloud folder via the cloud desktop app. AOMEI Backupper currently can access the local cloud folder. It can't read files from online cloud space.
Q: Information code 4103: Failed to write file.
Solution:
1) Please check if the destination location has enough free space to save the backup.
2) Please check if you have enough permission to read/write the destination location. You can check if you can copy files to the destination path via Windows.
3) Please check if the destination drive is damaged, such as bad sectors.
4) If you are backing to an external drive, please make sure that you hook your external disks up. And, if you are using a USB case to connect the target drive, please check if it is in good condition and has sufficient power supply.
5) If you are backing to a network path, please make sure that your network is stable and in good condition.
6) In addition, when you are doing the backup operation, we suggest that you close other threads that are accessing this destination.
Q: Information code 4104: Invalid image file.
Solution:
1) If you get this error during checking backup after the backup is completed, please separately check the image file via Tools-->Check Image. Or, you can explore the image to check the backup content. Generally, when the image can be explored successfully, it is able to be restored.
2) If you get the error when you restore an incremental backup file, please try to restore previous incremental or original full backup versions.
Q: Information code 4105/21: Not enough memory to process this command.
Solution:
1) Please check if there is enough memory to run the backup.
2) If you are performing an incremental backup and there are too many incremental backup versions, please perform one full backup regularly, and then continue to do incremental backups based on the new full one.
Q: Information code 4107: Failed to complete the operation/element not found or the image file not found.
Solution:
1) If you get the error message during the backup process, please reinstall the software and then rerun the backup.
2) If you get the error message during the restore process under reboot mode, please select the image manually to restore it again under the reboot environment. Note: If the reboot environment fails to recognize the drive that saves the backup image file, please reboot into computer, then try to create a WinPE bootable media via Tools-->Create Bootable Media, then boot the computer from WinPE media to do the restore.
Q: Information code 4110: Failed to decode the backup data.
Solution: The error generally appears when checking an image. You can try to explore the image to check the backup content. Generally, when the image can be explored successfully, it is able to be restored. If you also get the error when you explore the image, please try to re-create the backup.
Q: Information code 4118: Find no unused space to store temporary files.
Solution:
1) For backup, this error occurs when you run a sector-by-sector backup of the disk and the computer only has this one disk. In this situation, AOMEI Backupper will backup all sectors whether used or not, so there is no space to save temporary cache files, please change the backup mode to "Intelligent Mode", or you can connect another disk to the computer. Please change the backup mode to "Intelligent Mode" under Backup Options, or you can try to temporarily connect a USB drive so the program will save temporary cache files to another drive so that the backup will be finished successfully.
2) For clone, this error usually occurs when you clone a disk to a same-sized disk with the sector-by-sector mode, and there is no third disk on the computer. It is the same situation: there is no space to save temporary cache files. Please do not tick the "Sector by sector clone" option when cloning, or you can try to temporarily add a USB drive to save temporary cache files to another drive so that the clone will be finished successfully.
Q: Information code 4119: The source partition or volume can not be backed up sector by sector.
Solution: Generally, the error occurs when you use the sector-by-sector backup way to do system/partition/disk backup and you also select a backup source partition as the destination to save backup. Please select another location as the destination, or select "Intelligent Mode" under Backup Options. Note: when you back up Bitlocker encrypted partitions (uncrypted state) or no-NTFS/FAT32 partitions, AOMEI Backupper will use the sector-by-sector backup way by default, even though you select "Intelligent Mode", in this case, please select another location as the destination to save backup.
Q: Information code 4120: Failed to adjust partition size.
Solution:
1) Please check if you tick the “SSD alignment” option in Operation Summary before starting restore/clone. If yes, please do not tick the option and try again.
2) If you are cloning or restoring from a big disk to a small one, you can choose the “Edit partitions” option in Operation Summary before starting the restore/clone, then select “Manually adjust partition size” to adjust the partition size manually.
Q: Information code 4121: unknown system.
Solution:
1) It might be caused by the file system read error during backup. Please restart the program and then retry the backup.
2) It might also be caused by partition errors. We advise you to first run chkdsk /r to check and fix the partitions you want to back up, and then retry the backup.
3) If the source partitions are encrypted by Bitlocker, please try to disable Bitlocker and then do the backup again.
Q: Information code 4122: Failed to get bitmap.
Solution: Please reinstall the software and then recreate the backup to run. We suggest that you use sector-by-sector mode configured in the Backup Options. And, please use chkdsk /r command to check and fix the partitions you would like to back up before backing up them.
Q: Information code 4123: All partitions that need to be backed up have not been found.
Solution: When the source partitions have changed, for example, the starting sector, partition’s size, or/and some other physical configuration has been changed, the program can’t detect the same source with the record of the backup task, then you will get the error. Please try to recreate the backup task. Note: If all disks fail to be listed after you do an automatic update for AOMEI Backupper and then cause the error, please try to reinstall AOMEI Backupper manually.
Q: Information code 4125: Failed to explore or preview the image.
Solution: This might be that the related drivers fail to load. Please uninstall AOMEI Backupper, and then reboot the computer to install again.
If you still get the error, please check if you enable “Ransomware Protection” and check if it blocks AOMEI apps. If yes, please allow all AOMEI applications to run: Select Start--> Settings--> Update&Security--> Windows Security --> Virus & threat protection. Under "Ransomware protection," click the “Manage ransomware protection option”. Click the “Allow an app through Controlled folder access option”. Click the “Add an allowed app” button, then select the “Recently blocked apps” option. Check and click the “+” button for AOMEI apps to allow them. Or, directly switch the Controlled folder access setting to Off.
Q: Information code 4130: Missing image files.
Solution: The error generally appears in checking the image after the backup is completed or directly clicking the backup task to restore. Please select backup files manually to check or restore.
Q: Information code 4138: There is not enough space on the disk.
Solution:
1) Please check if there is enough space in your destination location. If there is not enough space, please delete or remove some files to free up more space for the destination. Or, please modify the destination to a bigger drive.
Note: If you enable the backup cleanup plan to delete old backup versions, but it fails to work which causes the destination to be filled, please contact our AOMEI Support Team to check the problem further.
Q: Information code 4140: The backup driver works improperly, you could restart the computer to solve the problem.
Solution:
As for the error, please check the following items:
1) Please uninstall the program manually via the Control Panel, then reboot the computer to reinstall it.
2) Please select Start-->Settings-->Update&Security-->Windows Security to open Windows Security Center (or search and open Windows Defender). Then select “Virus&threat protection”, and click "Manage Settings" under Virus&threat protection settings to add the install directory of AOMEI Backupper to exclusion. And, continue to click "Manage Ransomware Protection" under Ransomware Protection, then click “Allow an app through Controlled folder access” to add ABCore.exe, ABService.exe, and Backupper.exe of the install directory of AOMEI Backupperas as allowed apps.
3) Please type into “cmd” at Start Menu, run Command Prompt as administrator to open Command Prompt window, then run “net start ambakdrv” to check if the drivers can be started.
4) If the above solutions do not work, please change the backup mode to "Use Microsoft VSS" to run the backup.
Q: Information code 4141: Failed to add boot configuration, cannot enter Restart Mode.
Solution: Some operations need to be performed under reboot mode (WinPE). However, the program failed to add boot configuration for reboot mode, so reboot failed. You can directly create WinPE bootable USB/CD by clicking Tools-->Create Bootable Media, and then boot the computer from WinPE media to do operations again.
Q: Information code 4143: Failed to create the Windows PE bootable ISO Image, the operation cannot proceed......
Solution: The restore process needs to be performed under reboot mode(WinPE). However, the program can't create WinPE automatically based on your environment. You can create WinPE iso (ampe.iso) via Tools-->Create Bootable Media and then put the iso to the installation directory of AOMEI Backupper. After that, please try to restore it again. Or, you can directly create a WinPE bootable USB/CD, and then boot the computer from WinPE media to do restore.
Q: Information code 4160: Failed to open the file.
Solution: This error occurs mainly in File backup or File sync. It is usually caused by file access permissions and nonexistent files. Please check if you have enough permissions to access source files/folders. And, if some source files/folders missing, please recreate the backup to run again.
Q: Information code 4161: The destination path is not writable, please select a new path.
Solution: Generally, the error appears in the file sync process.
1) If you are syncing files to NAS, please reconnect NAS under Tools--Storage Management and sync again.
2) If you are syncing files to an external drive, please check if the external disk is hooked up.
3) In addition, please check if the destination folder has read/write permission with System and Administartor account.You can right-click the destination folder, and check Permission-->Security.
Q: Information code 4162: Single file is too big. The target file system does not support, please change other location and try again. (Because FAT12 supports single file up to 32MB, FAT16 and FAT32 support up to 4GB, maybe this cause the error. So we suggest you restore to NTFS, EXFAT or other file system that support much bigger single file.)
Solution:
1) Please check if the destination partition is a FAT32 partition. If yes, the FAT32 partition does not support saving a single file larger than 4GB. It is recommended to change the target location to NTFS or exFAT partition. Or please convert the destination FAT32 partition to NTFS.
2) Please check if the destination location is encrypted by Bitlocker. If yes, please disable BitLocker and restore/sync again.
25. Information code 4163: There’s no need to backup the file or directory.
Solution: Generally, the error appears in the file sync or file backup process. If you run the backup or sync for the first time, please check if the account you login has enough permission to access the source you want to back up/sync. If the error appears in the scheduled backup, please run the backup once manually.
Q: Information code 4164: The destination path is too long, please restore to the original location or change to a shorter path and try again.
Solution: Generally, the error appears when you do the file sync or file restore. Please check if the destination is greater than 256 bytes. If yes, please restore the original location or change to a shorter path. Please note that the program counts the path bytes which include the bytes of the source path you backup/sync and the destination path.
Q: Information code 4169: Unknown Error
Solution: It is an unknown error, please attach the log folder to AOMEI Support Team to further analyze the problem.
Q: Information code 4177: The destination path is too long, please change to a shorter path and try again.
Solution: Generally, the error appears when you do the file sync or file restore. Please check if the destination is greater than 256 bytes. If yes, please change to a shorter path. Please note that the program counts the path bytes which include the bytes of the source path you backup/sync and the destination path.
Q: Information code 4184: Unknown Error.
Solution:
1) If you backup to an external drive, please make sure the destination drive (especially drive letter and path) is exactly the same as the one configured in the existing bakup task.
2) If you back up to NAS, please check if the destination NAS is well connected and you can access the NAS successfully from your computer. And, please check if the NAS permissions have been changed. If yes, please enter the NAS admin settings and change the password, and then re-add the NAS in AOMEI Backupper. If you have mapped the NAS as a mapped drive, please make sure the mapped drive letter is the same as the one configured in the existing backup task.
Q: Information code 4189：Command execution failed before backup.
Solution: This error occurs after you configure a pre-command in a task. The task may fail if the command is executed unsuccessfully.
Please first manually run the command or script to check if it can be executed successfully. If the command runs without any problem, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software to check the error further.
Q: Information code 4196: Failed to get free space on the target location or the target path does not exist/Unknown Error.
Solution:
1) If you sync files to an external disk, please check if the drive letter has been changed. If changed, please manually change it back to the original then restart the AOMEI Backupper to sync again. You can also recreate a new task and then re-select the external disk. And please ensure the external disk won’t disconnect when syncing files.
2) If you sync files to NAS, please make sure the network is smooth. If you use the computer name as the NAS address, please change the computer name to its IP address and sync again.
Q: Information Code 4197: Command execution failed after backup.
Solution: This error occurs after you configure a command in a task. The task may fail if the command is executed unsuccessfully.
Please first manually run the command or script to check if it can be executed successfully. If the command runs without any problem, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software to check the error further.
Q: Information Code 4198: File backup failed to read file content.
Solution: If the backup image is stored on NAS or removable devices, the connection might be broken before reading the image file. To fix this, you can copy the image file to the local disk.
If the backup image is stored on a local disk, it indicates that some programs may have prevented Backupper from reading the image file. In this case, you can close these programs and try again. If you cannot find the programs, you can make a bootable media to do the backup again.
Q: Information Code 4199: The source sync path does not exist.
Solution: This error occurs when sync is running. In most cases, it is mainly caused when you choose a NAS, USB, or removable drive as the sync source. Please make sure the internet is well-connected during sync and the source path is valid and accessible. Also, the source path should remain unchanged once you configure the sync. You can also try to choose a local folder as the source of sync.
Q: Information Code 4200: The source backup path does not exist.
Solution: In most cases, it is mainly caused when you choose a NAS, USB, or removable drive as the source location.
Please make sure the internet is well-connected during backup and the source path is valid and accessible.
Also, the source path should remain unchanged once you configure the backup. You can also try to choose a local folder as the source backup location.
Q: Information Code 4201: Exceeds the maximum 2TB partition size of the MBR disk.
Solution: When you clone/restore from GPT to MBR disk, but the total size of the source partition exceeds 2TB space. However, MBR disk only supports 2TB of space. Please first convert the destination disk to GPT, and then perform cloning or restore again.
Q: Information Code 4209: Abnormal exit during backup/synchronization.
Solution: This error usually occurs when a backup/sync is running. Please restart Backupper and recreate a new task to run again.
If the problem remains, please check if your computer has a crash. If yes, please contact our AOMEI Support Team and attach the Minidump file under C:\ Windows\Minidump and log folder of the installation directory of AOMEI Backupper so we can further analyze the problem and help you find solutions.
Q: Information Code 4210: The target path does not exist! Please check its validity and try again.
Solution: This error occurs when sync is running. In most cases, it is mainly caused when you choose a NAS, USB, or removable drive as the target location.
Please make sure the internet is well-connected during sync and the destination path is valid and accessible. Also, the destination path should remain unchanged once you configure the sync. You can also try to choose a local folder as the destination sync location.
Q: Information Code 4211: Failed to connect to the network address. It may be caused by a network error. Please check your network connection and try again.
Solution: This error usually occurs if a network file fails to connect in a file backup/sync. Please make sure the network is well-connected and there is no network fluctuation during the backup/sync.
Q: Information code 2: Failed to assign the drive letter.
Solution: Generally, the error appears during a disk clone. Please delete the partitions on target disk, and then clone again. It is recommended to select the "Sector-by-Sector Clone" way.
If it still does not work, you can also create a bootable media and boot your PC into WinPE to run a disk clone.
If the problem persists, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software so that we can further analyze the problem and help you find solutions.
Q: Information code 3: Dismount the volume fails, the program cannot process the volume, please reboot and retry.
Solution: Generally, this code occurs when other programs are running on the volume or the volume has been locked by other programs.
You can restart the PC and execute the operation again. Or you can create a boot disk with AOMEI Backupper and operate under WinPE mode.
Q: Information code 5: Failed to unlock the volume, please reboot to access the volume by Explorer.
Solution: This error usually occurs when you run a sync to NAS. Please restart your PC and check you can access the NAS normally. And, please try to delete the "NAS.xml" files under path C:\ProgramData\AomeiBR. After that, please re-connect your NAS by using another username or typing into the IP address.
Q: Information code 6: The partition table on the disk failed to update as other programs locked the partition table, please close other programs and retry.
Solution:
1) Please first do defragment and run chkdsk/r or chkdsk/f command to fix the source drive.
2) Delete all partitions on the target disk, then and then retry the clone.
3) If it still can't work, please try to do the clone again with the sector-by-sector clone way. In addition, please also try to run a disk clone with Partition Assistant.
4) You can also try to create a bootable media and boot the PC into WinPE to clone the drive.
Q: Information code 8: Partition table overlap & the following operations will stop. Reboot computer is recommended.
Solution: This error usually occurs when you restore a system image. You can just try the following solutions: 1. You can try to manually adjust the size of partitions before restoring and then retry to restore. 2. You can try to first delete partitions on the destination drive and then retry to restore.
Q: Information code 10: Update registry failed. Allow writing to the registry when antivirus software blocked.
Solution: This error usually occurs when you restore a backup image. If you encounter such a problem, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software so that we can further analyze the problem.
Q: Information code 16: Inconsistent file system error upon initial reboot to enter the boot restore software.
Solution: This error usually occurs when you restore a backup image file. In this case, you can try to create a bootable media and boot your PC into WinPE to restore the backup image.
Q: Information code 22: Failed to open disk.
Solution: We advise you to restart the PC and execute the operation again. Or you can create a boot disk with AOMEI Backupper and operate under WinPE mode.
Q: Information code 23: The operation has been canceled.
Solution: Please try to manually run the backup task and check if it will require an interaction operation. When you don't respond to the interaction operation during a schedule backup, it will cancel the backup.
Q: Information code 31: Please convert to NTFS separately in Windows GUI.
Solution: Generally, the code occurs when you back up to an external device or to NAS.
1) If you back up to an external drive, please check if you can access the external drive successfully. You can just re-plug the drive or connect it via another slot.
2) If you run a backup to NAS, please first check if the NAS connection is fine. Also, some antivirus programs may block the NAS. We advise you to temporarily close the antivirus program and reconnect the NAS.
Q: Information code 33: Failed to read sector (with bad sector)
Solution:
1) When you get the error during backup, please reboot the computer and then recreate the backup task to run. When you create the task, please click "Options"-->"Backup Mode", then select "Use AOMEI Backup Service" under Backup Service. And, before creating task, please also click the three-line on the upper right corner, click Settings-->"Backup Mode", then select "Use AOMEI Backup Service" under Backup Service. In addition, please close other running applications when you do the backup.
2) When you get the error during clone, please try to delete partitions on the target disk, and then do the system or disk clone again. Before cloning, please try the following things:
a. Please press Win+R, then run "cmd" to open Command Prompt, then run chkdsk /r to check and repair C: drive.
b. Please defrag for C: drive.
c. Please press Win+R, then run "services.msc" to open the service manager, then check if the "Volume Shadow Copy" is using the "Automatic" type.
d. Please Win+R, then run "cmd" to open Command Prompt, then run the following commands to restart Vss service. net stop vss net start vss
e. Close all running other applications, and then do the clone.
Q: Information code 34: Failed to write sector (with bad sector).
Solution: Please delete all partitions on the target disk via Windows Disk Management and then do the clone again.
Q: Information code 53: Network path not found. Please check if the network connection is normal and the network path is correct.
Solution: Please check if the network connection is normal and the network path is correct. Please try to delete the "NAS.xml" files under path C:\ProgramData\AomeiBR. After that, please re-connect your NAS under Tools--Storage Management, then recreate the backup to run.
Q: Information code 59: Unknown error
Solution: The error means an unexpected network error. Please try to run the sync task again.
Q: Information code 71: The maximum number of connections to the computer has been reached and cannot be connected to this remote computer again.
Solution: It may be that there are too many devices connected to the target NAS device or shared location, reaching the limit. Please remove some devices connected to NAS or shares or increase the number of allowed devices before running AOMEI Backuper to add this network path again.
Q: Information code 110: System cannot open the specified device or file
Solution: It may be due to a device disconnection. If you are backing up to an external disk, please check if this USB device is disconnected. Please reconnect it and try the operation again.
Q: Information code 200: Unknown error
Solution: Unknown error situation. Please contact our AOMEI Support Team and attach the log folder under the installation directory of the software to check the error further.
Q: Information Code 208: Failed to initialize $MFT file due to the error in file system. Please amend it by using CHKDSK.EXE in CMD to retry.
Solution:
1) If you get the error when you do a clone, please use chkdsk /r to check and fix the source partitions you want to clone, and then do the clone again.
2) If you get the error when you do a restore, it is caused by the source partition having some File System error. Generally, if the source partition you backed up still exists, you need to use chkdsk /r to check and fix the source partitions and then recreate the backup. But, if the source partition doesn't exist, sorry that the backup can't be restored further. Ps. If it is a disk backup, you can try to restore partitions one by one.
Q: Information code 209: Failed to initialize NTFS file system bitmap
Solution: Generally, the error occurs when you do a backup. Please run the Command Prompt as the administrator then run the command chkdsk /r to fix the partition you would like to back up. And then please retry the operation.
Q: Information Code 210: Failed to read the file record, there are some physical bad clusters on the disk
Solution: Please try to create a bootable media of AOMEI Backupper via Tools-->Create Bootable Media, and then boot the computer from WinPE media to run the operation.
Q: Information code 214: Not enough reserve space. Please make big enough available space for target partition. If you have checked the "Align partition to optimize for SSD" option, uncheck it please and try again because this option will adjust the partition accordingly and may cause this error.
Solution:
1) Please check if you choose the “Manually adjust partition size” option under “Edit Partitions” in Operation Summary. If yes, we advise you to select the “Copy without resizing partitions” option.
2) Please check if you choose the “SSD Alignment” option in Operation Summary. If yes, please untick the option.
3) If the above method still can't work, we advise you to choose a larger disk as the destination location.
Q: Information Code 215: Too many fragment files on the volume need to be defragmented.
Solution: Please first do a defragment on all source partitions that you want to back up or clone. And, please also run chkdsk/r or chkdsk/f command to fix the source partitions and then retry backup or clone.
If the problem remains, you can also try to create a bootable media and boot the PC into WinPE to backup/clone the drive.
Note: Generally, SSDs do not need to be defragmented because fragmentation does not affect SSD read and write speed. However, the operation of the software might be affected by fragmentation (get code 215 error). Therefore, you still need to defragment the SSD. You can use AOMEI Partition Assistant to defrag it.
Q: Information code 218: The file record is invalid in MFT, please try to use chkdsk.exe in command prompt to fix and retry.
Solution:
1) If you get the error when you do a clone, please use chkdsk /r to check and fix the source partitions you want to clone, and then do the clone again.
2) If you get the error when you do a restore, it is caused by the source partition having some File System error. Generally, if the source partition you backed up still exists, you need to use chkdsk /r to check and fix the source partitions and then recreate the backup. But, if the source partition doesn't exist, sorry that the backup can't be restored further. Ps. If it is a disk backup, you can try to restore partitions one by one.
Q: Information Code 220: The feature on the NTFS cannot be supported by the program yet.
Solution: Please first do a defragment on all source partitions that you want to back up or clone. And, please also run chkdsk/r or chkdsk/f command to fix the source partitions and then retry backup or clone. Also, we advise you to run the backup or clone with the sector-by-sector mode.
Q: Information code 303: Invalid network path.
Solution:
1) If you select the mapped NAS drive as the destination when you do the backup or sync, and then get the error when you run backup/sync for the first time, please try to directly add the NAS path under Tools-->Storage Management, and then recreate the task with selecting the added path as the destination.
2) If you get the error when you run the existing backup or sync task, please delete NAS.xml file under C:\ProgramData\AomeiBRm and then re-add the network path under Tools-->Storage Management.
Q: Information Code 308/312: Unknown Error.
Solution: This error usually occurs when you select a NAS as the source or destination of sync/backup. It should be caused by a network connection error. Please make sure your network is well-connected and you have enough permissions and access to the NAS.
If it still does not work, you can try to delete the NAS.xml file under C:\ProgramData\AomeiBR, and then reconnect the NAS with the IP address way.
Q: Information code 1208: Unknown Error.
Solution: This error usually occurs in a backup if you configure NAS as the backup destination. Please make sure the network is well-connected and the file sharing support is enabled in Windows.
Q: Information code 1909: Unknown Error.
Solution: This error usually occurs in file sync. Please check your internet connection and if you can normally access the network location on your machine.
Q: Information code 1920: Unknown Error.
Solution: This error usually occurs in a backup/sync if you select NAS/share as the destination location. Please make sure the network is well-connected and if you can normally access the network location on your machine.
Outlook Backup/Restore Error Codes
Q: Information code 36869: No Outlook information detected. Please confirm that the Outlook client has been installed and try again..
Solution: Please try to reinstall your Outlook client and add your Outlook account, then try again.
Q: Information code 36876/36890/36894/36897/36898/36900: Initialization failed, please try again later.
Solution:
1) Please try to reinstall your Outlook client and add your Outlook account, then try again.
2) These errors (36890/36894/36897/36898/36900) might be the internal error of the program. Please restart AOMEI Backupper to try again.
Q: Information code 36887/36889/36893/36905: Failed to obtain Outlook data. Please start the Outlook client to confirm whether the data is normal, and try to back up again if there is no exception.
Solution: Please open the Outlook Client and check if you can access email data. If it is normal, please rerun AOMEI Backupper to do the operation.
Q: Information code 36901/36902: Cannot find the backup email. Please confirm whether the backup source exists.
Solution: Please check if the backup source has disappeared or changed. If the backup source isn't changed, please run the task again. If it has been changed, please try to recreate the backup and select the correct backup source to back up again.
Q: Information code 36903/36906: Unknown Error.
Solution: Please restart AOMEI Backupper to try backup or restore again. If you continue to get the error, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software so that we can further analyze the problem.
Q: Information code 36907: Restoring email failed.
Solution: It might be that the original folder directory has been deleted. Please select "Restore to a new location" to manually select the destination to restore.
Q: Information code 36908/36909: Restoring email failed.
Solution: The Outlook directory creation failed. It may be due to some folders do not have "write" permission. Please open the Outlook client and check the permissions under account settings. Please add the write permissions for the relevant directories.
Email Backup/Restore Error Codes
Q: Information code 38146: %s email backup failed. Please try again later.
s% is the corresponding email address.
Solution: Please restart AOMEI Backupper to run the task again.
Q: Information code 38152: %s backup failed. Failed to retrieve email information.
Solution: Parameter error. Please restart AOMEI Backupper to run the task again.
Q: Information code 38153: The backup mailbox directory %s cannot be found. Please check if the backup source exists.
Solution: For example, if you create the backup task for directory A, then directory A is deleted, so you will get the error when performing the incremental backup. Please log in to your mailbox to check if the source directory has been removed.
If the source directory still exists, please try to recreate the backup task to run again.
Q: Information code 38154: The configuration information for the %s email is missing. Please add the email account again.
Solution: The configuration information of the source mailbox is missing. Please re-add the mailbox account, then back up again.
Q: Information code 38155: The backup mailbox %s cannot be found. Please check if the backup source exists..
Solution: Please check if the source mailbox has been removed or the login credentials have been changed. Please try to re-add it and then do the backup again.
Q: Information code 38156: The backup email %s cannot be found. Please check if the backup source exists.
Solution: For example, if you create the backup task for some emails, then the source emails are deleted, so you will get the error when performing the incremental backup. Please log in to your mailbox to check if the source data has been removed.
If the source data still exists, please try to recreate the backup task to run again.
Q: Information code 38157: %s verification failed. Please check if the account password is correct and try again.
Solution: It seems that the login credentials of the mailbox are wrong. Please check and confirm the account and password, then try again. In addition, some mailboxes need to require an App Password to be added. For more details about App Password, please refer to here.
Q: Information code 38158: IMAP traffic limit reached for %s mailbox. Please try again later.
Solution: Please check if your email IMAP daily traffic has reached the maximum limit. Please try again the next day. And, please also confirm that the network is stable.
Q: Information code 38159: Failed to retrieve %s mailbox information, please check the network and try again.
Solution: It seems that the login credentials of the mailbox are wrong. Please check and confirm the account and password, then try again. In addition, some mailboxes need to require an App Password to be added. For more details about App Password, please refer to here. And, please also confirm that the network is stable.
Q: Information code 38160: Failed to connect to %s mailbox server, please check the network and try again.
Solution: Network error. Please check if the internet is connected normally, then try again.