Categories
- All Categories
- Oracle Analytics Learning Hub
- 30 Oracle Analytics Sharing Center
- 19 Oracle Analytics Lounge
- 239 Oracle Analytics News
- 45 Oracle Analytics Videos
- 16K Oracle Analytics Forums
- 6.3K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 88 Oracle Analytics Trainings
- 16 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Issue Summary:OAS AdminServer Fails to Start — “Boot Identity Not Valid” and Schema Credential Sync
Environment
- Product: Oracle Analytics Server (OAS)
- WebLogic Version: 12.2.1.4.0
- OS: Linux
- Domain Home:
/obie/oas/user_projects/domains/bi - Java Home:
/obie/Software/jdk1.8.0_441
When starting the OAS domain using:
./start.sh
the following error occurred during AdminServer startup:
Admin Server Start Exception: Error occurred while performing nmStart :Error Starting server AdminServer : Received error message from Node Manager Server:[Server start command for WebLogic server 'AdminServer' failed due to: [Server failed to start up but Node Manager was not aware of the reason]].
The Node Manager log confirmed repeated restarts:
Server failed during startup. It may be retried according to the auto restart configuration.Server failed but will not be restarted because the maximum number of restart attempts has been exceeded.
Review of AdminServer Logs
From /obie/oas/user_projects/domains/bi/servers/AdminServer/logs/AdminServer.log, the critical error found was:
<Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid.The user name or password or both from the boot identity file (boot.properties) is not valid.The boot identity may have been changed since the boot identity file was created.
- Node Manager attempted to start AdminServer using these credentials but failed authentication.
- This caused the AdminServer to repeatedly enter a FAILED and FORCE_SHUTTING_DOWN state.
Additionally:
Startup config file .../data/nodemanager/startup.properties for server 'AdminServer' does not exist
showed the Node Manager was starting AdminServer using default parameters, not the correct configuration.
Answers
-
@User_R95ZU - Welcome to Oracle Analytics Community!
Please take a backup of boot.properties file and delete it for the AdminServer.
Then try bringing up the AdminServer using startWebLogic.sh script, it will request for the credentials, provide the correct credentials and then start the server for the first time.
It will create the new boot.properties file with correct credentials upon successful start.
Hope this helps!.
Please continue posting your queries in the community and have a great experience. Thanks!1 -
Hi @User_R95ZU
I echo the steps above, but the file names have changed and are slightly different in the latest Weblogic versions (adminServerUserKey.properties). You did not indicate which update of OAS you are using. They all use WLS 12214.
So, I will just add to the steps above, in case you need them
If you recently attempted to change the password for your 'administrator' user, then you can use the steps documented here:
How To Reset Weblogic Password In Oracle Analytics Server(OAS) (Doc ID 2786135.1)0 -
Hi Sumanth, I tried this step. Its now working
Error : Caused By: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1158)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.postInitialize(CommonSecurityServiceManagerDelegateImpl.java:1272)
at weblogic.security.service.SecurityServiceManager.postInitialize(SecurityServiceManager.java:586)
at weblogic.security.SecurityService.start(SecurityService.java:130)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090938]Authentication failure: The specified user failed to log in. javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User specified user denied
at com.bea.common.security.utils.ExceptionHandler.throwFailedLoginException(ExceptionHandler.java:62)
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:381)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:117)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:114)
Truncated. see log file for complete stacktrace<6 Nov, 2025 10:13:52,041 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<6 Nov, 2025 10:13:52,041 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<6 Nov, 2025 10:13:52,046 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
Stopping Derby server...
Derby server stopped.0 -
Hi Steve, Thanks for the kind help. But im not able to access the doc, could please share the steps.
0 -
Hello Oracle community,
Our boot.properties file is encrypted, but can we use the file from encrypted to plain text temporarily? will it works or not and will it impact any config files?
0 -
@User_R95ZU - The error "Authentication for user weblogic denied" means the credentials you are passing seems to be incorrect.
You can enter the content in boot.properties file as a plain text in below format and initiate a start.
username=weblogic
password=xyzThis will get encrypted upon successful restart, provided the authentication goes through successfully.
1 -
Hi Steve, Thanks for the kind help. But im not able to access the doc, could please share the steps.
You need to login in to My Oracle Support to access the document
0 -
Will change in boot.properties impact any configuration files?
—
Tried this method but still its not working getting below error.
Starting AdminServer ...
Admin Server Start Exception: Error occurred while performing nmStart : Error Starting server AdminServer : Received error message from Node Manager Server: [Server start command for WebLogic server 'AdminServer' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'AdminServer' log for detailed information.]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :
Unable to connect to AdminServer on host: BCCB-ETLBI-UAT-SRV.BCCB.COMFatal: Failed to start one or more Servers (return 3)
0

