Weblogic.nodemanager.common.ConfigException: Native Version is Enabled but Nodemanager Native Library Could not be Loaded (Doc ID 1301911.1)

Last updated on AUGUST 08, 2017

Applies to:

Oracle WebLogic Server - Version 10.0 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Mar-2016***

Symptoms

After installing as service, the node manager was not coming up as noticed in the log:

<Feb 28, 2011 10:49:38 AM> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:249)
at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:190)
at weblogic.nodemanager.server.NMServer.init(NMServer.java:182)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:390)
at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1734)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1029)
at weblogic.nodemanager.util.WindowsProcessControl.<init>(WindowsProcessControl.java:18)
at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(ProcessControlFactory.java:24)
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:247)
... 5 more

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms