My Oracle Support Banner

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

Last updated on DECEMBER 16, 2023

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.


Unable to start Managed Server.

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

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

There are 1 nested errors: Booting as admin server, but servername, ServerName, does not match the admin server name, AdminServer
  at weblogic.t3.srvr.ServerServicesManager.startService(
  at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(
  at weblogic.t3.srvr.T3Srvr.initializeStandby(
  at weblogic.t3.srvr.T3Srvr.startup(
  at weblogic.Server.main( 


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


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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