Skip to main content
VM backup fails with the VMWARE VDDK65535 error
Updated over 10 months ago

Problem description

VMware Virtual Machine backup fails with the following VMWARE_VDDK65535 error:
​

SyncError: VMware VDDK: Internal Error  (#10005ffff : 18000)

Cause

This issue occurs when the certificate is updated for the vCenter/Hypervisor.

Traceback

  1. Download job logs. Refer to the Logs article.

  2. Extract the logs and navigate to the

    Phoenix <YYYY/MM/DD>-<timestamp>.log

    file and check for the following traceback in the logs.

    [2020-07-31 15:10:38,047] [INFO] In vddk_lib open_disk diskpath [abc-storage] VM - VM.vmdk
        [2020-07-31 15:10:38,047] [INFO] In vddk_lib open_disk openFlag 5
        [2020-07-31 15:10:38,125] [ERROR] VDDK error[18000] Cannot connect to the host.
        [2020-07-31 15:10:38,126] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:VMware VDDK: Internal Error  #10005ffff : 18000). Traceback -Traceback (most recent call last):
        File "agents/vmware/vixDiskLibOCManager.py", line 117, in handle_oc_work
        File "agents/vmware/vixDiskLibHelper/vddk_lib.py", line 120, in open_disk
        File "agents/vmware/vixDiskLibHelper/vddk_lib.py", line 205, in __raise_vddk_error
        SyncError: VMware VDDK: Internal Error  (#10005ffff : 18000)
  3. Extract the vmware_vddk.zip file and check for the following traceback in the logs.
    ​

    2020-07-21T19:02:00.364+01:00| vthread-4| E110: 2020-07-21T19:02:00.364+01:00 VixDiskLibVim: Error 18000 (listener error GVmomiFaultInvalidResponse).
        2020-07-21T19:02:00.364+01:00| vthread-4| W115: 2020-07-21T19:02:00.364+01:00 VixDiskLibVim: Login failure. Callback error 18000 at 2500.
        2020-07-21T19:02:00.364+01:00| vthread-4| E110: 2020-07-21T19:02:00.364+01:00 VixDiskLibVim: Failed to find the VM. Error 18000 at 2572.
        2020-07-21T19:02:00.365+01:00| vthread-4| I125: 2020-07-21T19:02:00.365+01:00 VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
        2020-07-21T19:02:00.365+01:00| vthread-4| E110: VixDiskLib: VixDiskLib_PrepareForAccess: Disable Storage VMotion failed. Error 18000 (Cannot connect to the host) (fault (null), type GVmomiFaultInvalidResponse, reason: (none given), translated to 18000) at 4321.
        2020-07-21T19:02:28.333+01:00| vthread-4| I125: VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .
        2020-07-21T19:02:28.333+01:00| vthread-4| I125: VixDiskLib: VixDiskLib_Connect: Establish connection.
        2020-07-21T19:02:28.333+01:00| vthread-4| I125: VixDiskLib: Resolve host.
        2020-07-21T19:02:28.348+01:00| vthread-4| I125: 2020-07-21T19:02:28.348+01:00 error -[7F3B30FE5740] [Originator@6876 sub=Default] Cannot log into 10.1.1.218:443: Other error encountered: SSL Exception: Verification parameters:
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> PeerThumbprint: E2:29:...........................................:AA
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> ExpectedThumbprint: 2c:02:...........................................:4c
    2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> ExpectedPeerName: 10.1.1.218
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> The remote host certificate has these problems:
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> 
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> * Host name does not match the subject name(s) in certificate.
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> 
        2020-07-21T19:02:28.348+01:00| vthread-4| I125+ --> * unable to get local issuer certificate

Resolution

This issue occurs only for the backup proxy with version lower than 4.8.3-69446.

To fix the error, reboot the backup proxy after the certificate is updated. The backups will complete successfully.


πŸ“ Note
​ This issue is fixed for backup proxy with version 4 .8.3-69446 and later.


Did this answer your question?