Unable to start admin server before applying the AD and TXK patches

We were unable to start admin server before applying the AD and TXK patches (after 12.2 upgrade and running rapidwiz configure).

-bash-4.2$ adadminsrvctl.sh start

You are running adadminsrvctl.sh version 120.10.12020000.2

Enter the WebLogic Admin password:

Enter the APPS Schema password:

Starting WLS Admin Server…

NMProcess: <Sep 9, 2022 9:53:33 AM> <INFO> <Loading domains file: /u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains>

NMProcess: Sep 09, 2022 9:53:33 AM weblogic.nodemanager.server.NMServerConfig initDomainsMap

NMProcess: INFO: Loading domains file: /u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains

NMProcess: <Sep 9, 2022 9:53:33 AM> <INFO> <Loaded node manager configuration properties from ‘/u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.properties’>

NMProcess: Sep 09, 2022 9:53:33 AM weblogic.nodemanager.server.NMServer <init>

NMProcess: INFO: Loaded node manager configuration properties from ‘/u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.properties’

NMProcess: Node manager v10.3


NMProcess: Configuration settings:


NMProcess: NodeManagerHome=/u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1

NMProcess: ListenAddress=calrapdev02.harborfreight.com

NMProcess: ListenPort=5556

NMProcess: ListenBacklog=50

NMProcess: SecureListener=false

NMProcess: AuthenticationEnabled=true

NMProcess: NativeVersionEnabled=true

NMProcess: CrashRecoveryEnabled=false

NMProcess: JavaHome=/u01/install/APPS/fs1/EBSapps/comn/util/jdk64

NMProcess: StartScriptEnabled=false

NMProcess: StopScriptEnabled=false

NMProcess: StartScriptName=startWebLogic.sh

NMProcess: StopScriptName=

NMProcess: LogFile=/u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.log

NMProcess: LogLevel=INFO

NMProcess: LogLimit=0

NMProcess: LogCount=1

NMProcess: LogAppend=true

NMProcess: LogToStderr=true

NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter

NMProcess: DomainsFile=/u01/install/APPS/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.domains

NMProcess: DomainsFileEnabled=true

NMProcess: StateCheckInterval=500

NMProcess: QuitEnabled=true

NMProcess: UseMACBroadcast=false

NMProcess: DomainRegistrationEnabled=true

NMProcess: DomainsDirRemoteSharingEnabled=false


NMProcess: Domain name mappings:


NMProcess: EBS_domain_HFTDEV -> /u01/install/APPS/fs1/FMW_Home/user_projects/domains/EBS_domain_HFTDEV


NMProcess: <Sep 9, 2022 9:53:33 AM> <INFO> <Plain socket listener started on port 5556, host calrapdev02.harborfreight.com>

NMProcess: Sep 09, 2022 9:53:33 AM weblogic.nodemanager.server.Listener run

NMProcess: INFO: Plain socket listener started on port 5556, host calrapdev02.harborfreight.com

Invalid credentials passed.

Refer /u01/app/oracle/product/fs1/inst/apps/HFTDEV_calrapdev02/logs/appl/admin/log/adadminsrvctl.txt for details

adadminsrvctl.sh: exiting with status 1

adadminsrvctl.sh: check the logfile /u01/app/oracle/product/fs1/inst/apps/HFTDEV_calrapdev02/logs/appl/admin/log/adadminsrvctl.txt for more information …


Autoconfig was failing with below error

[CVM Error Report]

The following report lists errors encountered during CVM Phase

      <filename>  <return code where appropriate>

  /u01/install/APPS/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkManageDBConnectionPool.pl  1

  /u01/install/APPS/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkUpdateEBSDomain.pl  2

No. of scripts failed in CVM phase: 2

AutoConfig is exiting with status 2

AutoConfig execution completed on Thu Sep  8 23:10:06 2022

Action Plan

  1. Took a tar backup of Middle Tier binaries plus restore point on DB.
  2. Stop ALL application services
  3. Update application contextfile for s_adminservertimeout to “4000” and run autoconfig. If it fails with above error, you can ignore and proceed.
  4. Execute “perl $FND_TOP/bin/txkEBSDomainConfig.pl”. Provide existing apps and weblogic passwords.
  5. Restart admin server


adadminsrvctl.sh stop

adadminsrvctl.sh start

6. Stop application services and revert back the value of s_adminservertimeout to previous value. Rerun autoconfig and ensure it is successful.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s