000016877 - AxM 6.1 and 6.2 services fail to start  'Error 126: The specified module could not be found.'

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016877
Applies ToAccess Manager 6.1 and 6.2
2003 Server and 2008 Server
IssueAxM 6.1 and 6.2 services fail to start, "Error 126: The specified module could not be found."
AxM services fail to start, "Error 126: The specified module could not be found."
Cause

Shared C runtime library msvcr71.dll not present (for java 1.6)

AxM 6.2 using Java 1.7 is missing msvcr100.dll

Resolution

The library msvcr71.dll (the C runtime libraries) must be accessible by jservice.exe.

It can be copied into the same folder as jservice.exe (the bin folder of AxM)

The library is typically found in system32 of the Windows installation, where it would be shared by many applications. If it is copied to the bin directory instead, it will not affect other applications that may have a dependency on a specific version of the library.

Same solution applies to msvcr100.dll

Also the msvcr100.dll is part of 2010 vcredist.exe - included in AxM 6.2, located in the cst directory(needed for lockbox):

\axm-server-6.2-win-64\win-64\cst\Windows64\vcredist.exe

You can run vcredist.exe even if you are not going to use lockbox, and it will install msvcr100.dll in the system32 directory and resolve the error.

 

Notes

The Sysinternals utility called Process Monitor (procmon.exe) may be used to isolate the cause of the service failure. Add a filter for "Process Name is jservice.exe Include", so that only the events related to jservice.exe will be displayed. In this case there was a QueryOpen for msvcr71.dll in the path which failed each time with "name not found". There may be another file dependency or registry key that is incorrect or missing.

Oracle file a bug for this in Java 1.6 and it still applies to Java 1.7

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291

Legacy Article IDa53562

Attachments

    Outcomes