Quick Tip: WebLogic NodeManager Fails To Start As Windows Service

If your Oracle WebLogic NodeManager starts without issue when using startNodeManager.cmd but when configuring the WebLogic NodeManager as a Windows Service, it fails to start. The nodemanager.log file has the following entry:

Native version is enabled but NodeManager native library could not be loaded

The solution is to:

1. Delete the current Node Manager Windows Service
   C:\sc delete "NODE_MANAGER_WINDOWS_SERVICE_NAME"
2. modify the installNodeMgrSvc.cmd and add the highlighted portion:
   set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.RootDirectory=%DOMAIN_HOME% -Djava.library.path=%WL_HOME%\server\native\win\x64
3. Run the installNodeMgrSvc.cmd as Administrator

I hope this helps you when having issues trying to get the Oracle WebLogic Node Manager to start as a Windows Service.

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

NodeManager does not Start. Log Shows Error: weblogic.nodemanager.common.ConfigException “Native version is enabled but NodeManager native library could not be loaded” (Doc ID 2875144.1)

Start NodeManager Fails with Error “no nodemanager in java.library.path” (Doc ID 2907887.1)

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA  What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.

stewart@9rains.com

http://stewartschatz.com

Happy

0

Sad

0

Excited

0

Sleepy

0

Angry

0

Surprise

0