Avamar: Avamar client software conflicts with third-party business application
Summary: Installing the Avamar client on a Windows Server adds its bin folder to PATH, causing a service to load the 32‑bit ssleay32.dll from Avamar instead of the correct version, leading to a be unresponsive. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
After successfully installing the Avamar Client, a third party service crashes. Removing the Avamar Client corrects the behavior.
Cause
The Avamar client installation adds "C:\Program Files\avs\bin\" to the environment variable "$PATH" on a Windows Server.
The third party service also places C:\Program Files\Nuance\Recognizer\bin\SSLeay32.dll to the environment variable "$PATH" on the Windows Server.
Before the Avamar Client installation, the third party service loads the ssleay32.dll as C:\Program Files\Nuance\Recognizer\bin\SSLeay32.dll.
After installing the Avamar Client, the third party service loads the ssleay32.dll as C:\Program Files\avs\bin\ssleay32.dll causing the service to terminate due to an unexpected dll.
The third party service also places C:\Program Files\Nuance\Recognizer\bin\SSLeay32.dll to the environment variable "$PATH" on the Windows Server.
Before the Avamar Client installation, the third party service loads the ssleay32.dll as C:\Program Files\Nuance\Recognizer\bin\SSLeay32.dll.
After installing the Avamar Client, the third party service loads the ssleay32.dll as C:\Program Files\avs\bin\ssleay32.dll causing the service to terminate due to an unexpected dll.
Resolution
Remove the "C:\Program Files\avs\bin\" from "$PATH" in the environment variable after the Avamar Client installation. Environment variable "$PATH" specifies the directories in which executable programs are located on the machine that can be started without knowing and typing the whole path to the file on the command line.
Alternatively, move the "C:\Program Files\avs\bin" entry in the Path parameter in Environment Variables from the first item to the last, thereby changing the priority for the custom application software to be higher on the list.
Also, check to see if the "libeay32.dll" and "ssleay32.dll" files are present in the avs\bin directory.
The main problem is that those 2 files, which are 32bit, should not be in avs\bin directory, which is a 64bit directory. Those files should be present also in the avs\bin32 directory. So those two files can simply be deleted from avs\bin, without changing the env var PATH, and that should fix the issue.
Alternatively, move the "C:\Program Files\avs\bin" entry in the Path parameter in Environment Variables from the first item to the last, thereby changing the priority for the custom application software to be higher on the list.
Also, check to see if the "libeay32.dll" and "ssleay32.dll" files are present in the avs\bin directory.
The main problem is that those 2 files, which are 32bit, should not be in avs\bin directory, which is a 64bit directory. Those files should be present also in the avs\bin32 directory. So those two files can simply be deleted from avs\bin, without changing the env var PATH, and that should fix the issue.
Additional Information
The "libeay32.dll" and ssleay32.dll" files are not part of Windows, they are SSL library DLLs that come with Avamar, as well as other software.
Affected Products
AvamarProducts
Avamar, Avamar Client for WindowsArticle Properties
Article Number: 000060040
Article Type: Solution
Last Modified: 10 Dec 2025
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.