The ordinal <number> could not be located in the dynamic link library LIBEAY32.dll / The operating system cannot run %1

ID:    D6531
Published:    29 March 2004
Updated:    22 January 2014

Defect Id


Originally Reported Against

PVCS Version Manager

Resolved In

PVCS Version Manager 8.3




When launching the Version Manager (VM) Desktop client GUI, when executing a PCLI command or when launching an IDE that is integrated with Version Manager, a user may encounter the error:
The ordinal <number> could not be located in the dynamic link library LIBEAY32.dll.


The ordinal 2821 could not be located in the dynamic link library LIBEAY32.dll.

Sometimes the GUI just won't launch at all, but running it in console mode (by executing pvcsvmntc.exe from a Command Prompt window) shows:

Cannot load VMS: "VM_Install_Dir\vm\common\bin\win32\pvcsjvms.dll: The operating system cannot run %1"

or a stack dump, like:

 Exception in thread "main" java.lang.ExceptionInInitializerError
        at pvcs.system.PvcsConnection.addInterface(
        at pvcs.system.PvcsSystem.addInterface(
        at pvcs.system.PvcsConnection.addInterfacesFromFile(
        at pvcs.system.PvcsSystem.loadSystem(
        at pvcs.system.PvcsSystem.getSystem(
Caused by: java.lang.Exception: Unknown Exception at line 54 in VMNMInit.cpp
        at pvcs.vm.vms.Init.PvcsInit(Native Method)
        at pvcs.vm.vms.Init.load(
        at pvcs.vm.vms.Init.loadOrExit(
        at pvcs.vm.vms.AccessDatabase.<clinit>(
        ... 14 more

Likewise, the Serena VM Web Application Server (used for I-Net / File Server / WebDAV) may show error messages on its console, in the file VM_Install_Dir\vm\common\tomcat\logs\tomcat.log and/or end-user browser sessions such as:
java.lang.UnsatisfiedLinkError: VM_Install_Dir\vm\common\bin\win32\pvcsjvms.dll: The operating system cannot run %1
 java.lang.ClassLoader$NativeLibrary.load(Native Method)
If that system acts as a File Server, otherwise unaffected File Server clients will get error messages of the type:
Cannot find revision RevNum in archive "ArchivePath".
Error: EntityPath: Could not find a revision named * in the archive, "ArchivePath".
whenever they try to get revisions from split archives provided by this server.
These errors are typically the result of launching PVCS Version Manager on a system where Crystal Reports 9 or later is installed.
Crystal Reports will place copies of the files libeay32.dll and ssleay32.dll in the %windir%\System32 folder that are incompatible with the ones used by and shipped with PVCS Version Manager. Normally Version Manager will load the DLLs found in its installation directory, but the order of precedence in which DLL files get located on Windows operating systems force the use of DLL files found in %windir%\System32 over ones found in %PATH%, which is how the VM libraries are loaded.
Once the incompatible libraries get loaded into memory, the VM applications fail to start and pass the error to the user.
For example, the copy of the libeay32.dll from Crystal Reports in the %windir%\System32 folder is compared below to a copy from the PVCS Version Manager installation:

Directory of c:\winnt\system32


09/16/2002 04:30p             675,840 libeay32.dll
              1 File(s) 675,840 bytes


Directory of C:\Program Files\Serena\vm\common\bin\win32

09/08/2003  03:05 PM           839,680 libeay32.dll
               1 File(s)        839,680 bytes

Note the size difference.


This issue has been resolved as of Version Manager 8.3, by having it pre-load the offending DLLs from the VM directory. If these symptoms are seen in VM 8.3 or newer, check the ISLV.INI file to make sure it contains the section:


If this section cannot be located in the ISLV.ini file, add it to the bottom of that file after first closing all Version Manager instances on the affected PC.

To resolve this issue for Version Manager releases older than 8.3, the appropriate versions of the affected DLLs need to be loaded by the PVCS Version Manager code. 

The search order Windows uses to locate DLLs is:
  1. The directory containing the executable that wants to load the DLL.
  2. The current directory, also known as the "Start in" directory.
  3. The %SystemRoot%\system32 directory (eg. C:\WINNT\system32).
  4. The %SystemRoot%\system directory (eg. C:\WINNT\system).
  5. The %SystemRoot% directory (eg. C:\WINNT).
  6. The directories specified in %PATH%, left to right. 
In order for VM to use its own version of the libeay32.dll and ssleay32.dll DLLs, additional copies needs to be placed in a location that has a higher order of precedence than the mismatched versions from Crystal Reports (which are at location #3), leaving location #1 or #2.  Since location #2 is variable, the best solution is to use location #1.
Use the following matrix to locate the executable for each client:
Desktop GUI/PCLI
IDE Client (SCC)
VM_Install_Dir\vm\devint\bin as well as the directory of the IDE executable
Rich IDE Client for Visual Studio 2005
Determined by IDE
Rich IDE Client for eclipse
Determined by IDE
File Server/Web App (Running as a Service)
File Server/Web App (Running as an Application)
By copying the files libeay32.dll and ssleay32.dll from the directory VM_Install_Dir\vm\common\bin\win32 into the directories shown in this table, you will be able to resolve the problem for the respective clients.

In rare circumstances it may also be necessary to copy the files to the %windir%\System32 folder to overwrite the files that Crystal Reports copied there.


Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs