Applications Manager on Windows fails to start with error "Can't find dependent libraries"

book

Article ID: 108023

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After upgrading to Applications Manager(AM) version 9.2.2+ or 9.3.0+, which requires 64bit Java ,  AM fails to start up with the below error which can be seen in the AgentService.log and/or RmiServer.log:


ErrorMsg: AwE-9999 Internal error
Details: nativecalls
java.lang.UnsatisfiedLinkError: %AW_HOME%\c\nativecalls.dll: Can't find dependent libraries
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(Unknown Source)
    at java.lang.ClassLoader.loadLibrary(Unknown Source)
    at java.lang.Runtime.loadLibrary0(Unknown Source)
    at java.lang.System.loadLibrary(Unknown Source)
    at com.appworx.agent.nativ.NativeCalls.<clinit>(NativeCalls.java:40)
    at com.appworx.agent.AgentService.<init>(AgentService.java:262)
    at com.appworx.agent.AgentService.main(AgentService.java:1015)

Environment

Release:
Component: APPMGR

Resolution

Add Java's bin directory to the PATH variable. This can be achieved by editing the PATH variable or it can be set to be appended to the PATH variable in the %AW_HOME%\site\sosite.bat. The sosite.bat gets called every time the Applications Manager Service starts.

An example line below:

SET PATH=C:\Program Files\Java\jre1.8.0_171\bin;%PATH%