VSquare Official Help Library
Diagnosing VMware clone error 18000
During a backup, one or more virtual machines may display one the following error in the VSquare log or in the final execution report:
An error occurred during disk backup. API error is 18000 - Generic Error.
An error occured during disk backup. API description is 18000 - VIX_E_CANNOT_CONNECT_TO_HOST
To diagnose the cause of this issue, it is necessary to access the executor.log file that is creted on the VSquare server.
The executor.log contains the detailed messages created by the Virtual Machine API libraries used by VSquare during each backup.
Since the log is saved in the calling process work folder, the location may vary, depending on the server configuration and on how the backupset is executed. In the case of an On Demand backup for example, the executor log is probably found in the application folder of the launching application (for example, CA). The fastest approach, is to just search for the file as follows :
Once the log has been found, you can use a text editor to open it and search for the name of the machine that is displaying the error. By reading some of the latest log lines, you should be able to find the source of the problem, like in the following example :
See Also
SSL: EOF in violation of protocol The session does not have the required permissions
An error occurred during disk backup. API error is 18000 - Generic Error.
An error occured during disk backup. API description is 18000 - VIX_E_CANNOT_CONNECT_TO_HOST
To diagnose the cause of this issue, it is necessary to access the executor.log file that is creted on the VSquare server.
The executor.log contains the detailed messages created by the Virtual Machine API libraries used by VSquare during each backup.
Since the log is saved in the calling process work folder, the location may vary, depending on the server configuration and on how the backupset is executed. In the case of an On Demand backup for example, the executor log is probably found in the application folder of the launching application (for example, CA). The fastest approach, is to just search for the file as follows :
C:\>dir executor.log /s
Once the log has been found, you can use a text editor to open it and search for the name of the machine that is displaying the error. By reading some of the latest log lines, you should be able to find the source of the problem, like in the following example :
FILE: WaitForPossession timeout on 'Z:\VSQUARE\sbs-file-server\27_05_2014_08_00_14\1sbs-file-server.domain.local.vmdk.lck\M63158.lck' due to a local process (2948)
DISKLIB-LIB : Failed to delete disk 'Z:\VSQUARE\sbs-file-server\27_05_2014_08_00_14\1sbs-file-server.domain.local.vmdk' or one of its components: Failed to lock the file
[NFC ERROR] Failed to delete disk 'Z:\VSQUARE\sbs-file-server\27_05_2014_08_00_14\1sbs-file-server.domain.local.vmdk': Failed to lock the file (16392).
[NFC ERROR] Failed to delete the existing file Z:\VSQUARE\sbs-file-server\27_05_2014_08_00_14\1sbs-file-server.domain.local.vmdk
[NFC ERROR] NfcFile_Open: Open failed:
[NFC ERROR] NfcReceiveFile: failed to open file
See Also
Categories
Applicable Plans
Applicable Versions
Last Update : 27 July 2017 - 08:28