Not Able To Start Managed Server With Error "weblogic.management.ManagementException: Booting as admin server, but servername, <msName>, does not match the admin server name, AdminServer" (Doc ID 2632439.1)

Last updated on OCTOBER 03, 2023

Applies to:

Symptoms

Unable to start Managed Server.

The following error is thrown when starting the managed server from WLS admin console or through using startManagedWebLogic.sh script (startManagedWebLogic ManagedServerName http://HostName:AdminPort)

<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, ServerName, does not match the admin server name, AdminServer
  at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
  at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:462)
  at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:167)
  at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:894)
  at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:581)
  at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:473)
  at weblogic.Server.main(Server.java:71) 

Changes

 Debug flags have been added in the Weblogic server startup script: startWebLogic.sh file

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.