2 Replies Latest reply on May 16, 2013 8:18 PM by Scott_Symonds

    Re: SOA server not starting

      Even I'm getting the same error. But no bam_server.

      There are 1 nested errors:

      +weblogic.management.ManagementException: [Management:141223]The server name sa_s+
      erver1 specified with -Dweblogic.Name does not exist. The configuration includes
      +the following servers {AdminServer,soa_server1}.+
      at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(Runtim
      at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
      at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
      at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
      at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
      at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
      at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
      at weblogic.Server.main(Server.java:71)

      +<May 15, 2013 12:02:48 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st+
      ate changed to FAILED>
      +<May 15, 2013 12:02:48 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical+
      service failed. The server will shut itself down>
      +<May 15, 2013 12:02:48 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st+
      ate changed to FORCE_SHUTTING_DOWN>

        • 1. Re: SOA server not starting
          Is it a Windows Environment? If so please check the background service of weblogic is running or not?

          If not may I know the Environment details and its version?

          • 2. Re: SOA server not starting
            When I review the error log you have posted, it looks to me that the incorrect WebLogic server name was typed in. It is stating that only two servers exist in the WebLogic domain: AdminServer and soa_server1.

            If I am looking at this correctly, it appears that you were trying to start up a WebLogic server called "sa_server1". I think the 'o' in soa_server1 might be missing when you were trying to start the WebLogic server. If that is the case, this error happens when anyone tries to start a non-existing WebLogic server.

            What happens when you try to start "soa_server1"? I would make sure that there aren't any missing letters.

            Scott (PITSS)