Vmware Backup Job stays in a queued state after Snapshot Processing
Article ID: 100025806
Updated On:
Description
Error Message
SGMON Log reports the Below Message:
BEREMOTE: [08/16/11 15:43:08] [0000] 08/16/11 15:43:08 [fsys\shared] - VDDK-Log: VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib. Accelerated transport modes available.
BEREMOTE: [08/16/11 15:43:08] [0000] 08/16/11 15:43:08 [fsys\shared] - VDDK-Log: VixDiskLib: Enabling advanced transport modes.
BEREMOTE: [08/16/11 15:43:08] [0000] 08/16/11 15:43:08 [fsys\shared] - VDDK-Log: VMware VixDiskLib (1.2) Release build-323406
BEREMOTE: [08/16/11 15:43:08] [0000] 08/16/11 15:43:08 [fsys\shared] - VDDK-Log: System libeay32.dll library is older than our library (90706F < 90809F)
BEREMOTE: [08/16/11 15:43:08] [0000] SSLLoadSharedLibrary: Failed to load library libeay32.dll:126
BEREMOTE: [08/16/11 15:43:08] [0000] SSLLoadSharedLibrary: Failed to load library libeay32.dll:126
BEREMOTE: [08/16/11 15:43:08] [0000] 08/16/11 15:43:08 [fsys\shared] - VDDK-Log: SSLLoadSharedLibrary: Failed to load library libeay32.dll:126
Cause
Libeay32.dll and ssleay32.dll are libraries that contain encryption functions which allow for coded communications over networks. This file is opensource and is used in many opensource programs to help with SSL communication. It could be present on a machine in different versions and different locations, causing problems.
If a Third Party Application loads its own version of libeay32.dll from C:\Windows\system32, then it will cause version Mismatch with the library located at C:\Program Files\Veritas\Backup Exec\Vmware\Vixdisklib\bin
Resolution
Disclaimer: Please make sure that the software that uses the Libeay32.dll in the windows\system32 folder will be affected. Please contact the software vendor to get the latest version of Libeay32.dll.
Rename Libeay32.dll to Libeay32.dll_old from under C:\Windows\system32
If the Issue still persists, rename ssleay32.dll to ssleay32.dll_old
Note : The Solution only needs to be followed when the Log has a clear mention of the Mismatch version
To Enable Debug :-
Launch SGMON
Select Job Engine, RAWS, Agent Browser and Capture to File
Run the Job and when the failure occurs refer the SGMON Log from Backup Exec Install Path\Logs Directory
Issue/Introduction
