How to resolved adminserver startup failure.

Introduction:- In this article we have resolved adminserver startup failure. While starting the WLS Admin Server, unable to do that, after connecting to node manager showing error as ERROR: Invalid credentials passed even we passed correct password.

Reproduced the error as below. You can start the adminserver on the run file system. After that we Resolved adminserver startup failure. 


Reproduced the error as below. You can you start the adminserver on the run file system. 


Executing service control script:

/oracle/PROD/EBSFS/fs2/inst/apps/PROD_prdsrv/admin/scripts/ start -nopromptmsg

Timeout specified in context file: 4000 second(s)


script returned:



You are running version 120.10.12020000.11


Starting WLS Admin Server…


Invalid credentials passed.

Refer /oracle/PROD/EBSFS/fs2/inst/apps/PROD_prdsrv/logs/appl/admin/log/adadminsrvctl.txt for details


AdminServer logs are located at /oracle/PROD/EBSFS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs exiting with status 1 check the logfile /oracle/PROD/EBSFS/fs2/inst/apps/PROD_prdsrv/logs/appl/admin/log/adadminsrvctl.txt for more information …

Connecting to Node Manager …

ERROR: Invalid credentials passed.

ERROR: Unable to connect to the Node Manager. The Admin Server cannot be started up.

Successfully disconnected from Node Manager.

AdminServer logs are located at /oracle/PROD/EBSFS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs

08/21/21-15:02:48 :: exiting with status 1


To resolve the error we have done many more  as below. Here we have decrypted the weblogic password to findout correct password. Finally we got same password , earlier we passed during startup.


Please find below the way to decrypt WebLogic password as requested:


1> First we need to get the encrypted password from file :

cat $EBS_DOMAIN_HOME/servers/AdminServer/security/



2> Get the domain path :



3> Run below WLST script :




wls:/offline> domain = “/u01/oracle/fs1/FMW_Home/user_projects/domains/EBS_domain_VIS “

wls:/offline> service =

wls:/offline> encryption =

wls:/offline> print encryption.decrypt(“{AES}bVOPrUkmVNlnYMpIIVddRKn+rUGLb46yJOjAT5KO2n8=”)


Another way to pass correct password.
Just modify the ‘’ file for the Weblogic Admin Server.

– The file is locate at $EBS_DOMAIN_HOME/servers/AdminServer/security

– Replace the encrypted username and password with clear text




– Start the Admin Server

– Once the Admin Server starts the username and password will get encrypted again


also please check below In run and patch fs.



Remove the lok from patch and retest


Checking if the Node Manager is already up..

Connecting to Node Manager …

ERROR: Invalid credentials passed.

ERROR: Unable to connect to the Node Manager

After done above steps still showing same error.

Finally we have decided to recreate the weblogic domain.  Before going to recreate the domain,we need to know how to recreate the domain.

1. In the Database Tier do the following:


1.1. Log into the database tier.

1.2. Source the environment.

1.3. Ensure that database and listener are up and running.


2. In the Applications Tier do the following:

2.1. Source the RUN file system environment.

2.2. Stop all middle tier services using $ADMIN_SCRIPTS_HOME/

2.3. Ensure that no process is running from RUN file system.

2.4. Take a backup of the context file. Update s_adminservertimeout context variable value to 4000 and run AutoConfig.

2.5. Execute below command:

$ $FND_TOP/bin/ -script=ChkEBSDependecies -server=ALL_SERVERS

2.6. Recreate the domain by following below steps:

$ cd $FND_TOP/patch/115/bin

$ perl


Domain recreation is completed successfully.


2.7. Start the services and check the WLS domain is fine. For example, you might want to start the WLS console and check all the expected managed servers are up and running.


Once domain recreation completed successfully. Now we need to recreate the patch fs as below.

Below are the needed steps to recreate the patch fs from the scratch, You will need to make sure to have a valid backup of your system before you execute it as this plan will imply to remove information from your system and we might need to go back to the point the action plan is executed in case anything may not go as expected.


[1] adpreclone


On the RUN File-System, source RUN File-System:

$ source EBSapps.env run

# RUN Admin server MUST be up for this step

# check status:


# start if needed:


# execute adpreclone:

$ cd $INST_TOP/admin/scripts

$ perl appsTier

[2] detach PATCH homes
# This step is performed from the RUN file-system detaching oracle_homes on the PATCH file-system:
$ cd $FMW_HOME/oracle_common/oui/bin
$ ./runInstaller -detachhome ORACLE_HOME={oracle home} -silent
# for each PATCH oracle_home , it seems your patch fs is fs2 currently, if so:
<PATCH_FMW_HOME>/webtier [ /d01/oracle/ebsprd/fs2/FMW_Home/webtier ]
<PATCH_FMW_HOME>/Oracle_EBS-app1 [ /d01/oracle/ebsprd/fs2/FMW_Home/Oracle_EBS-app1 ]
<PATCH_FMW_HOME>/oracle_common [ /d01/oracle/ebsprd/fs2/FMW_Home/oracle_common ]
# The 10.1.2 Oracle Home needs a different syntax
$ ./runInstaller -removeHome ORACLE_HOME=<s_tools_oh> -silent
<PATCH ORACLE_HOME> [ /d01/oracle/ebsprd/fs2/EBSapps/10.1.2 ]
[3] copy RUN to PATCH
# it may be helpful for RUN environment to be DOWN for this step
# copy each of these locations from RUN to PATCH
<APPL_TOP> [ /d01/oracle/ebsprd/fs1/EBSapps/appl ]
<COMMON_TOP> [ /d01/oracle/ebsprd/fs1/EBSapps/comn ]
<OracleAS Tools 10.1.2 ORACLE_HOME> [ /d01/oracle/ebsprd/fs1/EBSapps/10.1.2 ]
[4] remove PATCH FMW_HOME directory
[ /d01/oracle/ebsprd/fs2/FMW_Home ]
[5] adcfgclone
$ cd <PATCH COMMON_TOP>/clone/bin
$ perl appsTier
For the prompts in this step:
Do you want to add a node (yes/no) [no] : no
Enter the full path of Run File System Context file : <absolute path to the Run File System Context file>
RC-00217: Warning: Configuration home directory (s_config_home) evaluates to <PATCH s_config_home>. A directory with this name already exists and is not empty.
Do you want to continue (y/n) : y
This is expected as part of the rebuild.
Target System Port Pool [0-99] : <desired PATCH File System Port Pool>
This will be the PATCH File System port pool. Would suggest that the RUN and PATCH port pools be different by approx twice number of managed servers on this node.
[6] verify work
in new terminal – source PATCH file-system
$ EBSapps.env patch
in new terminal – source RUN file-system
# Run Admin server MUST be up for this step
$ EBSapps.env run
$ adop phase=fs_clone force=yes

1 thought on “How to resolved adminserver startup failure.”

Leave a Comment