cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver 2004s Installation problem

0 Kudos

Hi Basis Experts,

I was installing NW 2004s in a system SUSE 10 and RDBMS MaxDB, I have a problem during the phase 42 of 50 "Install Software Units".

This is the log:

WARNING 2007-04-11 13:49:27

SDM call of deploySdaList ends with returncode 4. See output of logfile /tmp/sapinst_instdir/NW04S/SYSTEM/ADA/CENTRAL/AS/callSdmViaSapinst.log.

ERROR 2007-04-11 13:49:27

CJS-30156 SDM deployment failed for at least one of the components to deploy.

SOLUTION: Check '/tmp/sapinst_instdir/NW04S/SYSTEM/ADA/CENTRAL/AS/callSdmViaSapinst.log' for more information.

ERROR 2007-04-11 13:49:27

FCO-00011 The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|enableUsageTypes was executed with status ERROR .

And the callSdmViaSapinst.log is this:

Apr 11, 2007 1:49:13 PM Info: Start logging to console

Apr 11, 2007 1:49:13 PM Info:

Apr 11, 2007 1:49:13 PM Info: ============================================

Apr 11, 2007 1:49:13 PM Info: = Starting to execute command 'deploy' =

Apr 11, 2007 1:49:13 PM Info: ============================================

Apr 11, 2007 1:49:13 PM Info: Starting SDM - Software Deployment Manager...

Apr 11, 2007 1:49:13 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0006.20060303095356.0000

Apr 11, 2007 1:49:15 PM Info: SDM operation mode successfully set to: Standalone

Apr 11, 2007 1:49:16 PM Info: Initializing Network Manager (50117)

Apr 11, 2007 1:49:16 PM Info: Checking if another SDM is running on port 50118

Apr 11, 2007 1:49:16 PM Info: -


Starting deployment -


Apr 11, 2007 1:49:16 PM Info: Error handling strategy: OnErrorStop

Apr 11, 2007 1:49:16 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop

Apr 11, 2007 1:49:16 PM Info: Update strategy: UpdateLowerVersions

Apr 11, 2007 1:49:16 PM Info: Starting deployment prerequisites:

Apr 11, 2007 1:49:16 PM Info: Loading selected archives...

Apr 11, 2007 1:49:16 PM Info: Loading archive '/usr/dvdsap/D51031693/J2EE_OSINDEP/UT/EPBC06_0.SCA'

Apr 11, 2007 1:49:17 PM Info: Selected archives successfully loaded.

Apr 11, 2007 1:49:18 PM Info: Actions per selected component:

Apr 11, 2007 1:49:18 PM Info: Initial deployment: Selected development component 'irj'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000' will be deployed.

Apr 11, 2007 1:49:18 PM Info: No action: Selected development component 'com.sapportals.prt.bridge'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000' will not update currently deployed development component 'com.sapportals.prt.bridge'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000'.

Apr 11, 2007 1:49:18 PM Info: No action: Selected development component 'com.sap.pcd.dbschema'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000' will not update currently deployed development component 'com.sap.pcd.dbschema'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000'.

Apr 11, 2007 1:49:18 PM Info: Initial deployment: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.6.0.20060305011500' will be deployed.

Apr 11, 2007 1:49:18 PM Info: No action: Selected development component 'com.sapportals.prt.portalruntime'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000' will not update currently deployed development component 'com.sapportals.prt.portalruntime'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000'.

Apr 11, 2007 1:49:18 PM Info: Ending deployment prerequisites. All items are correct.

Apr 11, 2007 1:49:20 PM Info: Saved current Engine state.

Apr 11, 2007 1:49:20 PM Info: Starting: Initial deployment: Selected development component 'irj'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000' will be deployed.

Apr 11, 2007 1:49:20 PM Info: SDA to be deployed: /usr/sap/SBI/DVEBMGS01/SDM/root/origin/sap.com/irj/sap AG/7.0006.20060301194711.0000/epbcsda.ear

Apr 11, 2007 1:49:20 PM Info: Software type of SDA: J2EE

Apr 11, 2007 1:49:21 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Apr 11, 2007 1:49:21 PM Info: Starting cluster instance processes.

Apr 11, 2007 1:49:25 PM Info: Starting the instance JC_bw_SBI_01 running on host bw

Apr 11, 2007 1:49:25 PM Info: Starting the instance JC_bw_SBI_01 processes. The instance is running on host bw

Apr 11, 2007 1:49:25 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Apr 11, 2007 1:49:25 PM Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000':

SDM could not start the J2EE cluster on the host bw! The online deployment is terminated.

JStartupFramework could not start server process for the instance JC_bw_SBI_01 on the host bw

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)

Apr 11, 2007 1:49:26 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Apr 11, 2007 1:49:26 PM Info: -


Deployment was successful -


Apr 11, 2007 1:49:26 PM Info: Summarizing the deployment results:

Apr 11, 2007 1:49:26 PM Error: Admitted: /usr/dvdsap/D51031693/J2EE_OSINDEP/UT/EPBC06_0.SCA

Apr 11, 2007 1:49:26 PM Error: Processing error. Return code: 4

How can I solve this problem?

Pls help me

thanks in advance

Regards

Tania

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Tania,

Please check this link:

http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm

It states "The default timeout is 1800000 milliseconds(=30 minutes), so if the environment where the J2EE Engine is started or stopped has lower computing capabilities, then the process itself will be slower and the timeout should be increased.

Open command prompt in directory /usr/sap/<SID>/<INSTANCE_NAME >/SDM/program and execute:

sdm j2eeenginestartstop mode=automatic timeoutmillisec=<increased_timeout>".

Please award points if the answer was helpful.

Regards.

Ruchit.

Answers (9)

Answers (9)

0 Kudos

I was using java version 1.4_13 but when I changed to 1.4_12 the installation finished correctly.

Former Member
0 Kudos

Dear Tenia:

May I ask which version of java you use that can be solved this problem.

Have u uninstall all sourcecode then reinstall again or jsut change java

0 Kudos

Hi,

I could solve this problem when I Changed the java version.

Thanks all of you.

Tania

Former Member
0 Kudos

Hi,

Just check the <b>sdmrepository</b> file located in \usr\sap\X65\JC01\SDM\program\config

If the mode is <b>standalone</b> mode just change it to <b>integrated</b> mode by executing the following command in command prompt.

C:/usr/sap/SID/JCxx/SDM/program sdm jstartup "mode=integrated.

Hope this helps.

Plz do reward with points if helpful.

Regards ,

Nayana

Former Member
0 Kudos

Hi Tania

Apart from the solutions you received also check if ur logs are full.This you can do using DB manager.Its always good to put it to the overwrite mode.MaxDB has this limitation.Hope you know how to put the logs to overwrite mode from DB manager.Any querries feel free to ask.

Former Member
0 Kudos

Hi,

small correction in the commandline,

./sapinst SAPINST_SKIP_ERRORSTEP=true

regards

usharani

0 Kudos

Hi Usharani,

Thanks for your answer. I used the commandline ./sapinst SAPINST_SKIP_ERRORSTEP=true

and the Installation could advance until phase 45 "Configuring System Landscape Directory" and then sent me another error.

ERROR 2007-04-19 12:39:34

CJS-30199 The CTC classes were not found after waiting for 900 seconds.

ERROR 2007-04-19 12:39:34

FCO-00011 The step configSLDMainLocalMapSecRolesToUsers with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|configSLDMainLocalMapSecRolesToUsers was executed with status ERROR .

any suggestion?

Thanks in advance

Tania

0 Kudos

Hi everybody,

Thanks for yours answers, I did everythig you suggest but the installation send me the same error.

Tania

Former Member
0 Kudos

Hi Tania

Started the instance manually.Once it is up and running continue your deployment.It should go.The error is during the online deployment SDM tries to start the instance if in any case it fails you get this error.

What i suggested you is a workaround.

Reward points if useful

Former Member
0 Kudos

Hi,

This problem occurs because,

during any deployment,sdm has to go to standalone mode,and once the deployment is completed it has to come back to integrated mode(which is default mode).

but sometimes,when it fails to come back to integrated mode,this problem occurs,even though the deployment will be completed.

try this option when u run sapinst,

./sapinst SAPINST_ERRORSTEP=true

reward points if helpful

regards

usharni

0 Kudos

Hi Ruchit,

Thanks for yur answer, but I increased the timeout and the error continues.

Tania