MUT-02041 applying SP 12

Question

I'm getting an error when applying SP 12 Step 17 .- Deploy via SDM/J2EE:
<b>ERROR 2005-06-13 10:05:58
MUT-02041  SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\ORA\callSdmViaSapinst.log.</b>
(See callSdmViaSapinst.log below)
The instance is running (in green state).
What is "cluster instance" and how can I start it if not running?
Regards.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331142750.0000' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031020134252.0000'.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050407182127.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031007124545.0000'.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4012.00.0000.20041104140331.0000' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031117101211.0000'.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4012.00.0000.20040609162409.0000' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031103173534.0000'.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050503150058.0000' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Jun 13, 2005 10:05:55... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050503150058.0000' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3003.00.0000.20040108174709.0000'.
Jun 13, 2005 10:05:56... Error: An error occured while storing the cluster instances.
Jun 13, 2005 10:05:56... Error: There is no control instance running in the cluster:
Name:JM_T1118682356946_XI
Host:XI
State:5
Please check if there are running cluster instances.
Jun 13, 2005 10:05:56... Error: Received exception when saving current Engine state: There is no control instance running in the cluster:
Name:JM_T1118682356946_XI
Host:XI
State:5
Please check if there are running cluster instances.
Jun 13, 2005 10:05:56... Info: Error handling strategy: OnErrorStop
Jun 13, 2005 10:05:56... Info: Update strategy: UpdateLowerVersions
Jun 13, 2005 10:05:56... Info: Starting: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331133103.0000' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3003.00.0000.20031215150458.0000'.
Jun 13, 2005 10:05:56... Info: SDA to be deployed: F:\usr\sap\WA1\DVEBMGS00\SDM\root\origin\sap.com\SQLTrace\SAP AG\6.4012.00.0000.20050331133103.0000\SQLTrace.ear
Jun 13, 2005 10:05:56... Info: Software type of SDA: J2EE
Jun 13, 2005 10:05:57... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jun 13, 2005 10:05:57... Info: Starting cluster instance processes.
Jun 13, 2005 10:05:57... Error: An error occured while starting a cluster instance.
Jun 13, 2005 10:05:57... Error: There is no control instance running in the cluster:
Name:JM_T1118682357555_XI
Host:XI
State:5
Please check if there are running cluster instances.
Jun 13, 2005 10:05:57... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jun 13, 2005 10:05:57... Error: Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4012.00.0000.20050331133103.0000':
SDM could not start the J2EE cluster on the host XI! The online deployment is terminated.
There is no control instance running in the cluster:
Name:JM_T1118682357555_XI
Host:XI
State:5
Please check if there are running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Jun 13, 2005 10:05:58... Error: An error occured while restoring the cluster instances states
Jun 13, 2005 10:05:58... Error: There is no control instance running in the cluster:
Name:JM_T1118682358180_XI
Host:XI
State:5
Please check if there are running cluster instances.
Jun 13, 2005 10:05:58... Error: Received exception when restoring Engine state: There is no control instance running in the cluster:
Name:JM_T1118682358180_XI
Host:XI
State:5
Please check if there are running cluster instances.
Jun 13, 2005 10:05:58... Info: -
Deployment was successful -
Jun 13, 2005 10:05:58... Info: Summarizing the deployment results:
Jun 13, 2005 10:05:58... Error: Admitted: C:\tmp\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS12_0.SCA
Jun 13, 2005 10:05:58... Error: Processing error. Return code: 4

Answer 1

Hi Javier
Thanks for your reply.
It turned out that our issue was slightly different to yours although the error maessage (MUT02041 return code 4 failure at SAPinst failure at step 16 J2EE/SDM)appeared the same. We resolved the issue and were able to continue with  SP12 successfully. It was a database (oracle) password connection issue.
Here is the explanation that resolved our issue:
In the bootstrap log, the following error can be seen repeatedly:
Caused by: java.sql.SQLException: ORA-01017: invalid username/password;
logon denied
This is an indication that the database user connection information has
changed. Please use the configtool to check if the database connection
is working. The configtool can be used to change the database user
logon info if necessary.
To launch the configtool, please run the configtool.bat from the
following path:
<drive>:\usr\sap\<sid>\<instance>\j2ee\configtool\configtool.bat
When prompted with 'Do you want to use the default DB settings?' select
'yes'. If an error message is returned, this means that either the
database is not running, or the stored logon information is no longer
valid (someone changed the DB logon info). In this case verify that
the database is up. Next, if the configtool is still unable to connect
to the DB, then select the 'ok' option which will take you to the
'secure store' link. Select 'secure store' to display the stored logon
data. Select the 'jdbc/pool/<sid>/Password' entry. At the bottom
you'll see the parameter where you can update the password. Please set
the correct DB password for the SAP<sid>DB user. Click 'Add' and then
the SAVE icon in the menu bar of the configtool.
The bootstrap process uses this DB logon info to synchronize the
filesystem with the parameters stored in the DB. In your system this
process fails which causes the J2EE startup to fail.
This resolves the problem.