While running EBS 12.2 rapid cloning perl adcfgclone appsTier on target machine getting error Waiting for the AdminServer to start, Connection to AdminServer failed, AdminServer start failed, Make sure that AdminServer parameters specified in the move plan are correct.

ISSUE

Error 1:

FINEST : Jun 24, 2025 12:10:52 – [ServerStartUtility:checkAdminServerStartup] Unable to get non ssl MBean connection. Admin server might not be up. Error message is null
FINE : Jun 24, 2025 12:10:52 – [ServerStartUtility:startAdminServer] Starting of Admin server AdminServer is in progress …, 14 minutes passed.
FINE : Jun 24, 2025 12:10:52 – [ServerStartUtility:startAdminServer] Waiting for the AdminServer to start …
FINE : Jun 24, 2025 12:10:57 – [ServerStartUtility:checkAdminServerStartup] Checking server startup for the url -t3://dev..gov.sa:7001 FINEST : Jun 24, 2025 12:10:58 – [ServerStartUtility:checkAdminServerStartup] Unable to get non ssl MBean connection. Admin server might not be up. Error message is null FINE : Jun 24, 2025 12:10:58 – [ServerStartUtility:startAdminServer] Waiting for the AdminServer to start … FINE : Jun 24, 2025 12:11:03 – [ServerStartUtility:checkAdminServerStartup] Checking server startup for the url -t3://dev..gov.sa:7001

Error 2:

Error Message :1
Jun 24, 2025 19:30:03 – ERROR – CLONE-20362 Connection to AdminServer failed.
Jun 24, 2025 19:30:03 – CAUSE – CLONE-20362 AdminServer start failed. Make sure that AdminServer parameters specified in the move plan are correct.
Jun 24, 2025 19:30:03 – ACTION – CLONE-20362 Check the AdminServer logs.
Error Message :2
Jun 24, 2025 19:30:03 – SEVERE – CLONE-20937 “pasteConfig” operation of J2EE domain failed. Check clone log and error files for more details.
Error Message :3
Jun 24, 2025 19:30:03 – ERROR – CLONE-20237 Restoring the sourceid “J2EECOMPONENT@EBS_domain” has failed.
Jun 24, 2025 19:30:03 – CAUSE – CLONE-20237 An internal operation failed.
Jun 24, 2025 19:30:03 – ACTION – CLONE-20237 Check the clone log for more details.

CAUSE:

1. Low s_adminservertimeout value caused premature timeouts during configuration, leading to incomplete domain setup.
2. Corrupted or outdated WebLogic domain due to misaligned configuration with context file and AutoConfig templates.

SOLUTION:
Oracle Referece:
Recreate the Oracle E-Business Suite (EBS) WLS (Weblogic Server) Domain

1. In the Database Tier do the following:
   1.1. Log into the database tier.
   1.2. Source the environment.
   1.3. Ensure that database and listener are up and running.
   
2. In the Applications Tier do the following:

2.1. Source the RUN file system environment.
2.2. Stop all middle tier services using $ADMIN_SCRIPTS_HOME/adstpall.sh.
2.3. Ensure that no process is running from RUN file system.
2.4. Take a backup of the context file and Update s_adminservertimeout context variable value to 4000 and run AutoConfig.
2.5. Execute below command:
$ $FND_TOP/bin/txkrun.pl -script=ChkEBSDependecies -server=ALL_SERVERS
2.6. Recreate the domain by following below steps:
$ cd $FND_TOP/patch/115/bin
$ perl txkEBSDomainConfig.pl
2.7. Start the services and check the WLS domain is fine. For example, you might want to start the WLS console and check all the expected managed servers are up and running.

Note: when running txkEBSDomainConfig.pl you will be prompted “Enter the server start mode for the domain [DEFAULT – prod]:”.Choose the default value of prod.

Oracle Web Logic Server can be run in two different modes, either prod or dev, and the recommended option is to choose prod as it is safer.

The dev mode allows to deploy unsigned java classes but is quicker than prod.*