cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent Help PLEASEEEEEEEEEEEE

Former Member
0 Kudos

Hi to everyone:

Well I have a proble in installing de j2ee celtral instances that's the problem:

Please can someone help me with the SDM

WARNING 2007-05-11 21:16:21

Execution of the command "/usr/j2sdk1.4.2_13/bin/java -Xmx256M -Djava.ext.dirs=/

usr/sap/BIT/DVEBMGS00/SDM/program/lib:/usr/j2sdk1.4.2_13/jre/lib/ext -d64 -jar /

usr/sap/BIT/DVEBMGS00/SDM/program/bin/SDM.jar jstartup mode=standalone sdmhome=/

usr/sap/BIT/DVEBMGS00/SDM/program logfile=/tmp/sapinst_instdir/NW04S/LM/AS-JAVA/

ADDIN/ORA/CENTRAL/CI/callSdmViaSapinst.log" finished with return code 16. Output

:

Starting SDM - Software Deployment Manager...

tc/SL/SDM/SDM/sap.com/SAP AG/7.0009.20060817110748.0000

Error while reading the SDM repository. Error message is:

com.sap.sdm.persistency.FileCantReadException: Can't read file /usr/sap/BIT/DVEB

MGS00/SDM/program/config/sdmrepository.sdc

Error while reading the SDM repository.

Severe (internal) error. Return code: 16

ERROR 2007-05-11 21:16:21

MUT-02041 SDM call of jstartup mode=standalone ends with returncode 16

ERROR 2007-05-11 21:16:21

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

undefined.

ERROR 2007-05-11 21:16:21

FCO-00011 The step enableUsageTypes with step key |NW_Addin_CI|ind|ind|ind|ind|

0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|11|0|enableUsageTypes was e

xecuted with status ERROR .

THANKS.

Accepted Solutions (1)

Accepted Solutions (1)

praveenkumar_kadi
Active Contributor
0 Kudos

Hi,

I'm also experienced this problem.I have used following solution

Th problem you could find here is

even if you start the mode in either standalone or integrated your SDM won't start completely and shows the above error.

check for sdmrepository.sdc file under <Drive>:\usr\sap\<SAP_ID>\JC<Instance_ID>\SDM\program\config\

sdc file might got corrupted or it's size would have got reduced(compare with other sdc file that server creates everytime). even if you run sdm in standalone or integrated,

you will get the same error.

Solution is to compare with the backup file(like sdmrepository_backup_8.sdc) that sapinst creates everytime while upgarding the engine in the same folder and

replace and rename (sdmrepository.sdc) your corrupted sdc file with any of the previous one. now restart the installation

then your problem will be solved.

for the error description and solution you can also visit SAP Note:756084

and search for "sdmrepository.sdc"

hope that helps.

Former Member
0 Kudos

Thanks Praveen:

Your answer was very useful.

I give you points.

THANKS

Answers (0)