Common Error Codes & Messages

Categories: Troubleshooting, Error Codes, XenServer, Hyper-V, Physical Systems, Alike v3, Alike v4


The following list of common error codes are separated into three categories: Windows systems, Alike Backup Delegate (ABD), and miscellaneous Alike errors. Get a description of each and when possible, a resolution.

Service/Windows Error Codes

Error 1219


This is a very common, and confusing, error but fortunately easy to fix. Windows throws an error 1219 when you try to login to a resource, such as a network share, with two different user accounts within the same session. The most common cause is when a Windows Explorer window is opened to a network share (e.g. the ADS folder), causing a conflict with Alike’s session.


“Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.”


If this is the case, simply close the offending explorer window and try again. You can also check the output of the command, net use, and close any conflicting sessions.

Close the sessions with the following syntax: net use /DELETE \\\session

Error 86


“The specified network password is not correct.”


Failed to connect to DS share (\\IP.TO.ADS\QSDS\data\) with error code: 86 (User Account)


This is usually caused by incorrect credentials, or a missing profile entry in the Alike Credential Profile manager for Q-Hybrid jobs. If you have no credentials entered, adding a new, default entry could solve this issue.

Error 1326



“The user name or password is incorrect.”


This is usually caused by incorrect credentials for your VM in the Alike Credential Profile manager for Q-Hybrid jobs.

Error 1727


“The remote procedure call failed and did not execute.”


Failed to connect to DS share (\\IP.TO.ADS\QSDS\data\) with error code: 1727 (User Account)


This is often caused by improper permissions to access WMI/DCOM on the remote system, but can also be related to CIFS or NTFS permissions on the ADS itself.

Error 71


“No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.”


The system hosting your ADS CIFS share has run out of available connections. This is often caused by an overwhelmed or under powered device sharing your ADS CIFS share. The most common cause is when the Alike ADS is being hosted on a workstation grade OS (Windows XP, Vista, 7, etc.), which impose connection limits.


To resolve this issue you must either reduce the load of that share, or move the ADS to a more robust system.

Error 3


“The system cannot find the path specified.”


Dedupe cache generation failed, backup performance may be degraded. Failed to open file on file \\\\data\jobs\x\y\z.HCA with error: The system cannot find the path specified. (code: 3)


This most often occurs when your Alike Data Store (ADS) is local to your Alike server, and the IP address has changed since your installation of Alike. To resolve this, either change your Alike server’s IP address back to the original address used, perform a recovery installation of Alike on top of your existing copy, or contact support for assistance.

Another common cause is when you specify your ADS path using a DNS name, instead of an IP Address. Since not all devices can resolve name, or they do not always resolve to the same device, using an IP address for your ADS path will usually solve this issue.

Error 64



  • “ERROR_NETNAME_DELETED” appears and crashes the active program window.
  • Your PC frequently crashes with Error 64 when running the same program.
  • “The specified network name is no longer available” is displayed.
  • Windows runs sluggishly and responds slowly to mouse or keyboard input.
  • Your computer periodically “freezes” for a few seconds at a time.

These 64 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Windows Operating System) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your ERROR_NETNAME_DELETED error occurs is a critical piece of information in troubleshooting the problem.


Corrupt download or incomplete installation of Windows Operating System software. Corrupt Windows registry keys associated with Windows Operating System. Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files. Another program maliciously or mistakenly deleted Windows Operating System-related files. ERROR_NETNAME_DELETED.

Windows System Error Codes such as “ERROR_NETNAME_DELETED” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. The important thing to note is that this is a DNS related issue.

  1. Check your ADS settings and change the DNS name/NETBIOS name to the IP address of the storage. Instead of having: \\storage.mycompany.domain.tld\data, or \\STORAGE\data, you should \\\data or whatever your IP is.
  2. Repair Registry Entries Associated with Error 64
  3. Conduct a Full Malware Scan
  4. Clean Out Your System Junk (Temporary Files and Folders) With Disk Cleanup
  5. Update Your Device Drivers
  6. Utilize Windows System Restore to “Undo” Recent System Changes
  7. Uninstall and Reinstall the Windows Operating System Program Associated with ERROR_NETNAME_DELETED
  8. Run Windows System File Checker (“sfc /scannow”)
  9. Install All Available Windows Updates
  10. Perform a Clean Installation of Windows

Error 67


“The network name cannot be found.”


The network name cannot be found. This error is returned if the network with the neighbor IP address is unreachable.


The first step is to check your ADS settings and change the DNS name/NETBIOS name to the IP address of the storage. Instead of having: \\storage.mycompany.domain.tld\data, or \\STORAGE\data, you should \\\data or whatever your IP is. The ResolveIpNetEntry2 function is used to resolve the physical address for a neighbor IP address entry on a local computer. Learn more here.

Error 87


“The parameter is incorrect.”


The WriteFile() or ReadFile() function call may fail with this error if you are operating on a named pipe and using overlapped I/O.


Microsoft recommends the following for Alignment and File Access Requirements: “File access sizes, including the optional file offset in the OVERLAPPED structure, if specified, must be for a number of bytes that is an integer multiple of the volume sector size. For example, if the sector size is 512 bytes, an application can request reads and writes of 512, 1,024, 1,536, or 2,048 bytes, but not of 335, 981, or 7,171 bytes.

File access buffer addresses for read and write operations should be physical sector-aligned, which means aligned on addresses in memory that are integer multiples of the volume’s physical sector size. Depending on the disk, this requirement may not be enforced.”

Learn more here.

ABD Related Error Codes (linux errno.h codes)

Error 22

  • Example: Seek failed on file /dev/nbd0 with error code : 22

This is most often caused by networking related issues between the source and destination ABDs. Often, this is due to aggressive idle settings in firewalls or network devices which forcibly close the network connection between the two devices. It can also be caused by network intermittencies or a generally unreliable connection between the two locations.

  • Resolution: If this is the case, simply close the offending explorer window and try again. You can also check the output of the command, net use, and close any conflicting sessions.

Close the sessions with the following syntax: net use /DELETE \\\session

Error 137

  • Example: “failure for device: X. Output: 137”

This is caused by the ABD running out of memory during the course of the job (usually a restore job).

  • Resolution: It can be resolved by assigning additional memory to the ABD template for the pool in question (i.e. going from 128MB to 512MB ram), and re-running the job.

PLEASE NOTE: This problem typically affects only older versions of Alike (pre v3.0). However, this error can occur in newer versions. If a newer installation of Alike encounters this issue, please open a support ticket.

Error Message: ABD Failed to mount ADS. mount: Cannot allocate memory

This misleading error may mean that the ABD appliance cannot fully connect to your CIFS network share, usually due to a permissions problem.

  • Resolution: Double-check the NTFS and CIFS Sharing permissions on the Alike Data Store (ADS) allows full access by the user account defined in the Alike Manager under Settings–>Storage.
Miscellaneous Errors

Error Message: “Failed to copy databases”

  • Resolution: Change the “Archive internal databases every___hours” setting under Tools–>System Settings–>Show Advanced Settings.

The default is undefined. Change this setting to archive every 6 to 8 hours.

Final Notes

If you didn’t find what you’re looking for here, or need help troubleshooting, please open a support ticket. See the KB article, “How to Use Quadric Support,” for instructions and tips on making your support experience as efficient as possible.

Easy To Install. Easy To Use. Free To Try.