config.sh Fails To Start The Domain AdminServer Error while starting the domain.oracle.as.provisioning.util.ConfigException Cause: Starting the Admin_Server timed out. Action: See logs for more details. (Doc ID 1549043.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Fusion Middleware - Version 11.1.1.2.0 to 11.1.2.1.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms

Getting the following error when configuring 11.1.1.6 IDM. this can happen with any WLS install type.

oracle.as.provisioning.util.ConfigException:
Error while starting the domain.
Cause:
Starting the Admin_Server timed out.
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3150)
at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3040)

 

 This can be futher isolated to Weblogic Server domain configuration by simply just configuring a default base_domain with just wls/common/bin/config.sh

After exiting the configuration, or during, try running ./startWeblogic.sh to start the AdminServer.  It will fail to start with:

<Apr 22, 2013 4:58:20 PM BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
<Apr 22, 2013 4:58:21 PM BST> <Info> <Management> <BEA-141223> <The server name hostname specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.>
<Apr 22, 2013 4:58:21 PM BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: [Management:141223]The server name hostname specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
       at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
       at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
       at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
       at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
       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)

>
<Apr 22, 2013 4:58:21 PM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Apr 22, 2013 4:58:21 PM BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Apr 22, 2013 4:58:21 PM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
[hostname.oracle]:
[hostname.oracle]: echo $SERVER_NAME displays hostname

 

Cause

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