Error Messages & Solutions
Here you will find a list of common error messages that may occur during copying – including causes and suggested solutions.Error 2
Error message:The system cannot find the specified file
Common causes:
- File moved or deleted: The file was renamed, moved, or deleted since it was last used.
- Network issue: If the file is on a network drive, the error may occur due to a brief interruption in the network connection.
Solutions:
- Search for the file manually: Navigate to the corresponding folder in Windows Explorer and verify that the file actually exists. Use the Explorer's search function if needed.
- Check network connection: If accessing a file on the network, ensure that the connection to the network and the corresponding computer is stable.
Error 3
Error message:The system cannot find the specified path
Description:
The location (path) for a file or directory does not exist or is not accessible.
Common causes:
- Typo: The most common cause is incorrect spelling in the path name, file name, or drive name.
- File/folder moved or deleted: The file or directory being accessed was renamed, moved, or deleted since it was last used.
- Network issue: If the path refers to a shared network folder, the error may occur if the network connection is interrupted or the target computer is unreachable.
Solutions:
- Check the path: Go through the path step by step and verify each component (drive letter, folder name, file name) for correct spelling.
- Navigate manually: Try accessing the path manually via Windows Explorer to ensure it exists.
- Check network connection: If it's a network path, make sure your computer is connected to the network and the target computer is powered on.
Error 5
Error message:Access denied
Cause:
The user account used to start AllSync does not have permission to access the file or folder.
Solutions:
- Start AllSync with a user account that has the required access permissions for this data.
- Extend the access permissions of the file or folder to include the user account used with AllSync.
Error 8
Error message:Not enough memory available for this command
Description:
The system or a program does not have enough memory to complete a requested operation. This refers not only to physical RAM but also to virtual memory (the page file) used by the operating system to extend RAM.
Common causes:
- High system load: The most common cause is too many programs running simultaneously, consuming nearly all physical RAM and virtual memory.
- Memory leak: A faulty program continuously requests memory but does not release it. Over time, this can lead to complete exhaustion of available memory resources.
- Memory fragmentation: There may be enough free memory, but it is not in a contiguous block large enough for the current request.
- Limitations on 32-bit systems: On older 32-bit systems, the virtual address space per application is limited to 2 GB. Even if the PC has sufficient RAM, this limit can be reached, causing the error.
- Fixed page file size: If the page file size is manually set to a small fixed value, it can easily become fully utilized.
Solutions:
- Restart the system: A restart is almost always the first and simplest solution. It frees all memory and temporarily resolves memory leaks or fragmentation.
- Close programs: Exit all applications you do not currently need to manually free up memory.
- Check memory usage: Open Task Manager (Ctrl + Shift + Esc) and check which programs are using the most memory. This can help identify the cause of the memory issue.
- Adjust page file: Ensure that Windows automatically manages the size of the page file (virtual memory). You can find this in the Advanced System Settings under Performance → Settings → Advanced.
Error 15
Error message:This file would replace an existing file in the zip file, but no temp file is used. (ZIP)
Cause:
Existing files in a ZIP archive cannot be updated if no folder is defined for temporary ZIP file creation.
Solution:
Enable the option 'Temporary creation of ZIP files'.
Error 23
Error message:Data error (CRC check)
Description:
Error message 23 Data error (CRC check) is one of the most critical error messages related to data transfer or access to storage media. A CRC check (Cyclic Redundancy Check) is a method used to verify data integrity. When data is written or transferred, a checksum value is calculated and stored. During a later read access, this checksum is recalculated and compared with the stored value. If the values do not match, it means the data is corrupted. The error message is therefore a direct indication of data corruption. Since CRC errors are often a sign of impending hardware failure, you should try to back up important data from the affected storage medium as soon as possible.
Common causes:
- Physical damage to the storage medium: This is the most common cause. The hard drive has bad sectors or an SSD cell is faulty.
- Faulty data connection: The data cable (e.g., SATA or USB) is damaged or not properly connected. An unstable network connection during a copy can also cause CRC errors.
- Driver issues: An outdated or faulty driver for the storage controller can disrupt communication between the hardware and the operating system.
- Sudden system crash or power failure: If the system shuts down unexpectedly during a write operation, data may be partially or incorrectly written to the storage medium.
Solutions:
- Check the storage medium: This is the most important step. Use a specialized tool to check the drive. For Windows partitions, you can use the command-line tool chkdsk. Most SSD manufacturers offer their own diagnostic tools to check the condition of the drive.
- Check hardware and drivers: Make sure the data cable is securely connected and not damaged. Update the drivers for your storage controllers (found in Device Manager).
Error 32
Error message:The process cannot access the file because it is being used by another process
Common causes:
- The file is open in another application.
- Background process: A background service such as an antivirus or a cloud sync service (e.g. OneDrive, Dropbox) is currently accessing the file.
- Faulty program termination: A program that previously used the file crashed or did not close the file properly. In this case, the file handle remains active, causing the lock.
Solutions:
- Close programs: This is the simplest and most common solution. Close all programs that might be accessing the file and try again.
- Use the copy option 'Use Windows service 'Volume Shadow Copy' to copy locked files'.
- Restart: Restarting the computer almost always resolves such locks, as all file handles are closed.
Tips:
- Use the copy option 'Identify blocking process of locked files' to automatically detect and log the blocking process during a copy operation.
- Use the File-Lock Analyzer from AllSync to manually inspect locked files.
Error 33
Error message:The process cannot access the file because another process has locked part of the file
Description:
See information under error number 32.
Error 64
Error message:The specified network name is no longer available
Description:
A connection to a network resource (e.g. a shared folder, network drive, or network device) was interrupted.
Common causes:
- Server or computer offline: The device hosting the shared resource was shut down, restarted, or entered sleep mode.
- Network connection interrupted: The Wi-Fi connection briefly dropped, or the network cable was disconnected. This can also occur due to brief interruptions in the router or switch.
- Inactivity (timeout): The connection was inactive for a certain period, prompting the operating system or server to terminate the session to free up resources.
- Hardware issues: A fault in the network card, router, or switch can cause sporadic disconnections.
Solutions:
- Check network connection: Ensure your computer is connected to the network and the target computer (hosting the share) is powered on and reachable.
- Reconnect: Disconnect the network drive or share and reconnect. This forces the system to establish a fresh connection.
- Restart computer: Restarting the computer often helps terminate a faulty connection and establish a new, stable one.
- Timeout settings: If the connection drops due to inactivity, adjusting certain timeout values in the registry may help. This is an advanced setting and should only be performed by experienced users.
Error 67
Error message:The network name could not be found
Description:
The computer running AllSync cannot connect to the specified network resource.
Common causes:
- Incorrect network name: The most common cause is a typo in the name of the computer or shared folder.
- Computer offline: The target computer is turned off, in sleep mode, or not connected to the network.
- Network discovery is disabled: The network discovery feature is disabled on the target computer or your own computer, making it invisible to other devices.
- Firewall block: A firewall on one of the computers is blocking the necessary ports for file sharing.
- Name resolution issues: There is a problem with network services (such as DNS) that prevent the computer name from being resolved to a valid IP address.
Solutions:
- Check network names: Make sure the name of the computer and shared folder is spelled exactly right.
- Check target computer: Ensure the target computer is powered on and connected to the same network.
- Enable network discovery: Go to Windows settings → Network and Sharing Center and ensure that network discovery and file and printer sharing are enabled for the active network profile.
- Use IP address: Try using the IP address of the target computer instead of its name (e.g. \\192.168.1.100\Server). If that works, the issue is likely related to name resolution.
- Check firewall settings: Verify that the firewall on both computers is not blocking file and printer sharing. Windows Firewall usually has an automatic rule for this, but it may sometimes be disabled.
Error 82
Error message:The directory or file cannot be created
Description:
The operating system rejects the command to create a new file or folder at a specific location.
Common causes:
- Invalid path or file name: The specified path or file name contains invalid characters (such as ?, *, ", etc.), is too long for the file system, or refers to a folder that does not exist.
- Missing write permissions: This is a very common cause. The user or program does not have permission to create new files or folders in the destination directory. This can happen if the program is not run as administrator.
- No disk space: The destination drive is full and cannot accept new data.
- Write-protected medium: The destination drive or folder is marked as write-protected.
- File system error: An error in the file system of the destination drive may prevent file or folder creation.
- This error may occur when copying many files into a single folder on a FAT32 partition. FAT32 partitions allow a maximum of 65536 entries per folder. A file may require multiple entries depending on the length of its name. One entry is needed for the short name (8.3), and one additional entry for every 13 characters in the file name.
Solutions:
- Check path and file name: Verify the path and file name for typos and invalid characters. Also ensure that the destination folder actually exists.
- Check permissions: Make sure the program is run with administrator rights. Check the permissions for the destination folder and ensure the user has write access.
- Check disk space: Ensure there is enough free space on the destination drive.
- Remove write protection: If the drive or folder is write-protected, remove the protection in the folder or file properties.
- Fix file system errors: Use the Windows tool chkdsk to check the destination drive for errors and fix them.
- FAT32 partition: Distribute your files across multiple subdirectories to avoid the 65536-entry limit per folder.
Error 103
Error message:Cannot open this file. (ZIP)
Cause:
The file is locked for read access and cannot be compressed into a ZIP file.
Solution:
Use the copy option 'Use Windows service 'Volume Shadow Copy' to copy locked files'.
Error 112
Error message:There is not enough disk space available
Common causes:
- The disk is full: The destination drive already contains so much data that there is no space left for new files.
- Temporary files: Windows and other applications often create large amounts of temporary files that occupy disk space unnoticed.
- Full recycle bin: Deleted files remain in the recycle bin and continue to occupy space until they are permanently removed.
Solutions:
- Free up disk space: Delete files and folders you no longer need. Be sure to empty the recycle bin afterward to actually free up the space.
- Use Disk Cleanup: Use the built-in Windows tool Disk Cleanup (just search for cleanmgr.exe) to safely remove temporary files, cache files, and other system files.
Error 121
Error message:The semaphore timeout period has expired
Description:
This error means that a process waited for a response but did not receive it within the expected time. It most commonly occurs during network or hardware operations.
Common causes:
- Unstable network connection: This is the most common cause. The connection to the target system (server, NAS, etc.) is too slow, interrupted, or disrupted by a faulty Wi-Fi connection.
- Problem with the target system: The system being accessed is overloaded, frozen, or otherwise unable to respond quickly.
- Hardware failure: A defective network card, damaged network cable, or issues with the storage medium itself can prevent timely data transfer.
- Driver issues: An outdated or faulty driver for the network card or storage controller can slow down data transmission.
- Faulty USB connection: This error can also occur with external USB devices if the connection is faulty or the device takes too long to respond.
Solutions:
- Check network connection: Inspect your network cables and Wi-Fi connection. Ensure both your computer and the target device have a stable and fast connection.
- Restart systems: Restart both your computer and the target system (e.g. server or NAS device). This often resolves temporary network and system issues.
- Check hardware: Replace the network cable to ensure it is not defective.
- Update drivers: Make sure your drivers for the network card and storage controllers are up to date.
Error 282
Error message:The provided file system does not support extended attributes
Description:
Extended attributes are additional metadata that the operating system attaches to a file or folder. These include security information, encryption flags, or specific program data. This error means that the file system of the destination drive cannot store these extended attributes.
Common causes:
- FAT32 drive: The destination drive is formatted with the FAT32 file system. This does not support extended attributes.
- Network shares: The share uses a file system or network protocol that does not properly handle extended attributes.
Solution:
Enable 'Copy Method B' in the profile properties.
Error 320
Error message:The file was already open for writing, but permitted us to open for reading. (ZIP)
Cause:
The file is locked for read access and cannot be compressed.
Error 507
Error message:Cannot write to zip file. (ZIP)
Common causes:
- The disk is full or has been removed.
- The ZIP file to be created exceeds the maximum size of 4 gigabytes.
Error 508
Error message:Cannot move temporary file to target zip file. (ZIP)
Cause:
The ZIP file in the destination folder could not be deleted and replaced with the temporarily created ZIP file.
Solution:
Check the access rights of the ZIP file in the destination folder.
Error 521
Error message:Cannot open clipboard
Description:
Another software is using the clipboard and has locked it for other applications.
Solutions:
- Close other applications step by step and repeatedly try the action that triggered the error message.
- Restart Windows to release the clipboard again.
Error 999
Error message:Error paging memory
Description:
This error message is a serious warning and usually indicates a hardware problem. The operating system uses virtual memory (the page file on the hard drive) to extend physical RAM. Paging memory means the system is trying to load a page of this data from the hard drive back into RAM. The error occurs when this process fails because the data on the hard drive is unreadable or already corrupted. This is often a sign of impending hardware failure.
Common causes:
- Defective RAM: One of the most common causes is a faulty RAM module. The memory in RAM may be corrupted, causing data written to the page file to be faulty and unreadable.
- Faulty hard drive or SSD: The page file is stored on a storage medium. If the hard drive has bad sectors or the SSD cells are faulty, this can cause data corruption.
- Corrupted file system: Errors in the file system can affect the page file itself, preventing it from being read correctly.
- Driver issues: A faulty or outdated driver for the storage controller can disrupt communication between the operating system and the storage medium.
Solutions:
- Back up data (top priority): Since this error often signals hardware failure, immediately back up all important data to an external medium.
- Run RAM test: Test your memory using the built-in Windows diagnostic tool. Type Windows Memory Diagnostic in the Start search and follow the instructions.
- Check disk for errors: Use the tool chkdsk to verify the integrity of your hard drive.
- Update drivers: Make sure the drivers for your storage controllers and motherboard are up to date.
Error 1069
Error message:The service could not be started due to a logon failure
Common causes:
- The login credentials (username or password) of the user account are incorrect.
- The user account does not have the Log on as a service permission.
Solutions:
- Check the username and password of the user account credentials.
- Check the 'Log on as a service' permission for the user account being used.
Error 1117
Error message:The request could not be performed due to an I/O device error
Description:
This error message is a direct and serious warning indicating a hardware issue. Check the Windows system log for more information about the hardware problem. Since this error strongly suggests an impending drive failure, you should immediately back up all important data from this disk.
Common causes:
- Defective hardware: This is the most common cause. The disk itself is faulty, has bad sectors, or is close to failure.
- Faulty cable: A damaged or loose data cable (e.g. SATA or USB) can disrupt communication.
- Connection issues: The connector on the motherboard or the device itself is faulty.
- External power supply: For external hard drives, a problem with the power adapter or power source can trigger the error.
- Driver issues: An outdated or incompatible driver for the storage controller (e.g. SATA, USB) can cause communication errors.
Solutions:
- Check connections: Always start by checking the physical connection. Ensure all cables are securely connected. For external drives, try a different USB port.
- Use a different cable/port: Replace the data cable or connect the device to a different port to rule out cable or connector defects.
- Check disk for errors: Use the tool chkdsk to verify the integrity of your hard drive.
- Update drivers: Make sure the drivers for your storage controller are up to date in Device Manager.
Error 1130
Error message:Not enough server storage is available for this command
Description:
The term server storage refers to the limited internal memory the server uses to manage network connections and file operations. When this memory is exhausted, the server can no longer process additional requests.
Common causes:
- High server load: The most common cause is the server handling too many simultaneous connections or file accesses. Each connection consumes a small amount of this memory, and when the limit is reached, the error is triggered.
- Memory leak on the server: A service, application, or faulty driver on the server consumes this internal memory and does not release it.
- Misconfiguration: On older Windows Server versions, the default size for this memory (the so-called non-paged pool) may be too small and must be manually increased in the registry.
Solutions:
- Restart the server: A simple server restart is often the quickest and most effective solution, as it clears all internal memory and resolves temporary leaks.
- Reduce server load: If the error occurs under heavy usage, try reducing the number of simultaneous accesses to the server. Use Task Manager or Resource Monitor on the server to identify which processes consume the most resources.
- Server updates: Ensure the server operating system and all drivers are up to date. Patches often fix known memory issues.
- Adjust registry settings: This is an advanced method and should only be performed by experienced administrators. Sometimes increasing the IRPStackSize value in the registry can resolve the issue.
Error 1219
Error message:Multiple connections to a server or shared resource by the same user using different usernames are not allowed
Description:
This error means your computer already has an active connection to a specific server or computer on the network using a particular username. You are now trying to establish another connection to the same server using a different username. For security reasons, Windows allows only one active user login per server at a time.
Common causes:
- Different credentials: For example, you are connected to a shared folder on \\Server with user A and now trying to connect to another folder on \\Server with user B.
- Automatically saved credentials: Your computer has stored login credentials for the server and uses them without your knowledge. If you then try to manually connect using different credentials, a conflict occurs.
- Mixed connection types: You connected a network drive with one username and are now trying to access a resource via a UNC path (e.g. \\Server\Windows) using a different username.
Solutions:
- Replace the IP address in the network path with the computer name or vice versa:
\\192.168.0.1\Windows → \\Server\Windows - Disconnect all drives connected to the network resource in Windows Explorer.
- Disconnect existing connections to the shared network resource:
- Open the command prompt.
- Type net use to view all active network connections.
- Find the connection to the relevant computer and disconnect it using the command:
net use \\Server\Windows /delete
- Restart the computer: A restart clears all temporary network connections and stored sessions. After restarting, you can establish a new connection using the desired credentials.
- Delete saved credentials: Check the Windows Credential Manager.
- Type Credential Manager in the Start search.
- Look for credentials containing the server name and remove them.
Error 1450
Error message:Insufficient system resources to complete the requested service
Common causes:
- Memory fragmentation: This is one of the most common causes of this specific error. Although the computer still has plenty of free memory overall, it is divided into many small, non-contiguous blocks that are insufficient for a larger memory request.
- Exhausted Desktop Heap: Each open application with its own window consumes part of the Desktop Heap. If you run many programs simultaneously, this special memory area can be fully consumed, preventing new applications or windows from opening.
- Driver or application issues: A faulty driver or an application with a memory leak can consume system resources without releasing them.
- General system load: On systems with limited memory, this error can occur when too many processes run in parallel and exhaust resources.
Solutions:
- Restart the system: A restart usually resolves memory fragmentation and clears all cached resources. This simple step is often enough to fix the error.
- Close other programs: Exit all applications you do not currently need. This frees up system resources used by those programs.
- Registry modification (advanced): If the error occurs frequently on a system with many open windows or programs, it may be due to a small Desktop Heap. Advanced users can increase this value in the registry.
Error 1816
Error message:Not enough quota available
Description:
A quota is a limit on system memory that Windows allocates to certain processes.
Common causes:
- A program or driver (often antivirus software or file system filters) consumes this system memory but does not release it. During long copy operations, this can eventually exhaust the quota.
- System limit reached: Especially on older Windows versions or systems with limited memory, the default quota may be too low to copy a large number of files simultaneously. The amount of required system memory increases with the number of files and folders, not necessarily with their total size.
- Faulty driver: An outdated or faulty driver may cause inefficient use of system resources.
Solutions:
- Restart the system: This is often the quickest solution, as a restart clears all system memory and resets the quota.
- Check background programs: Temporarily disable programs that operate at the file level, such as your antivirus, and try the copy operation again. Such programs are a common cause of memory leaks.
- System and driver updates: Make sure your Windows operating system and all drivers (especially for storage systems and network adapters) are up to date.
- Advanced registry setting: For experienced users, it may be possible to manually increase the system memory quota via the registry.
Error 2202
Error message:The parameter for the user or group name is invalid
Description:
Windows cannot find the specified username.
Common causes:
- Incorrect spelling: The most common cause is a typo in the username.
- Unknown account: The specified user account does not exist on the local computer or in the domain.
- Invalid format: The username was entered in the wrong format. For example, the domain or computer name is missing (e.g. USERNAME instead of DOMAIN\USERNAME).
- The user account previously existed but has since been deleted.
Solutions:
- Check the name: Make sure the username is spelled correctly. Pay attention to uppercase and lowercase letters.
- Verify account existence: Check whether the account actually exists.
Error -2147024891
Error message:Access denied
Solution:
AllSync must be run as administrator when User Account Control is active.
Error -2147212522
Error message:The Volume Shadow Copy Service is already in use by another program
Solution:
Close the program that is preventing use of the Volume Shadow Copy Service.
Error -2147212529
Error message:Unexpected provider error
Solution:
Make sure the required services for the option 'Use Windows service 'Volume Shadow Copy' to copy locked files' are not disabled.
Error -2147212542
Error message:The Volume Shadow Copy Service could not be initialized
Solutions:
- Restart AllSync and try the operation again.
- Restart Windows and try the operation again.
Error -2147417848
Error message:Automation error
Solutions:
- Restart AllSync and try the operation again.
- Restart Windows and try the operation again.
Error -2147418113
Error message:Critical error
Solutions:
- Restart AllSync and try the operation again.
- Restart Windows and try the operation again.
