Error: "The Oracle Weblogic $Name NodeManager Service on Local Computer Started And Then Stopped" Generating nodemanager.log Error "Native version is enabled but NodeManager native library could not be loaded"
(Doc ID 2061349.1)
Last updated on AUGUST 04, 2023
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 8.0 and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
After creating a windows service for the WebLogic Node Manager, the following error occurs when attempting to start the service:
"The Oracle Weblogic $DomainName NodeManager ($Path) service on Local Computer start and then stopped. Some services stop automatically if they are not in use by other services or programs."
Reviewing the logging in nodemanager.log for the detailed error message yields:
"Native version is enabled but NodeManager native library could not be loaded"
The issue can be reproduced at will with the following steps:
- Browse to the windows services menu and start the WebLogic node manager.
- Observe error (then browse to the nodemanager.log and observe the detailed error message).
The issue has the following business impact:
Due to this issue, users cannot startup node manager as a service.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document