cancel
Showing results for 
Search instead for 
Did you mean: 

WAS 6.40 JAVA SP15 upgrade failure

SandipAgarwalla
Active Contributor
0 Kudos

Hi All,

while upgrading WAS6.40 Java to SP15, i am getting the following error at phase no 20 - Deploy via SDM/J2EE

**ERROR 2006-01-18 20:22:32

MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.

**ERROR 2006-01-18 20:22:32

MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\ORA\callSdmViaSapinst.log.

**ERROR: Another SDM is running already for this SDM_HOME

directory. Exiting.

Processing error. Return code: 4Error: Processing error.

Return code: 4

Content of <b>callSdmViaSapinst.log</b> --

Jan 18, 2006 8:22:30 PM Info: Start logging to console

Jan 18, 2006 8:22:30 PM Info:

Jan 18, 2006 8:22:30 PM Info: ============================================

Jan 18, 2006 8:22:30 PM Info: = Starting to execute command 'deploy' =

Jan 18, 2006 8:22:30 PM Info: ============================================

Jan 18, 2006 8:22:30 PM Info: Starting SDM - Software Deployment Manager...

Jan 18, 2006 8:22:31 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4015.00.0000.20051212141956.0000

Jan 18, 2006 8:22:32 PM Info: SDM operation mode successfully set to: Integrated

Jan 18, 2006 8:22:32 PM Info: Initializing Network Manager (50017)

Jan 18, 2006 8:22:32 PM Info: Checking if another SDM is running on port 50018

Jan 18, 2006 8:22:32 PM Error: Could not start SDM - another Server may be running already.

Jan 18, 2006 8:22:32 PM Error: Another SDM is running already for this SDM_HOME directory. Exiting. Throwable: com.sap.sdm.client_server.launch.SDMRunningException Throwable message: Another SDM instance is running on this host

Jan 18, 2006 8:22:32 PM Error: Processing error. Return code: 4

Please help me out...

Regards,

Sandip

Accepted Solutions (1)

Accepted Solutions (1)

detlev_beutner
Active Contributor
0 Kudos

Hi Sandip,

restarting the computer itself should do the trick (that's the hard way, of course; you could also try to localise the SDM process and kill it).

Hope it helps

Detlev

Answers (2)

Answers (2)

detlev_beutner
Active Contributor
0 Kudos

Hi,

have the answers been of any value for you? If yes, please consider rewarding points for helpful answers! Thanks in avance!

Best regards

Detlev

SandipAgarwalla
Active Contributor
0 Kudos

Thanks Detlev,

It really helped.

Regards,

sandip

Former Member
0 Kudos

Hi sandip

1. Be sure that sdm is not opened by another user.

2. Be sure that the all user closed the NetWeaver studio.

3. Uninstall all the additional server via config tool.

I suggest to restart the engine before you start the patch.