Script adadminsrvctl.sh Failed To Start AdminServer With "Cannot connect to Node Manager" Error
Last updated on MAY 09, 2017
Applies to:Oracle Applications DBA - Version 12.2 to 12.2 [Release 12.2Cloud]
Information in this document applies to any platform.
On an upgrade of E-Business Suite (EBS) 12.1 to 12.2, when trying to start AdminServer by the script adadminsrvctl.sh,
adadminsrvctl.sh: exiting with status 1 and the following error can be confirmed in adadminsrvctl.txt.
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.
Validated the passed arguments for the option ebs-nmstart-adminsrv
Checking if the Admin Server is already up.
The Admin Server is not already up.
Traceback (innermost last):
File "", line 1, in ?
File "", line 123, in nmConnect
File "", line 656, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Connecting to Node Manager ...
ERROR: Cannot connect to Node Manager. Check if port 5556 is correct
12/06/15-20:09:25 :: adadminsrvctl.sh: exiting with status 1
Upgraded Applications from 12.1 to 12.2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms