Problem while installing ECC6.0 IDES with EP

[Former Member]

Hi,

I have successfully installed ECC6.0 IDES with ABAP+JAVA.

Now while installing the same with ABAP+JAVA and with EP &EPC , I am getting the following error while installing.can any one tell me how the problem can be resolved?

Jan 6, 2009 9:54:45 AM Info: End of log messages of the target system.

Jan 6, 2009 9:54:45 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 6, 2009 9:54:45 AM ***Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0014.20071112134549.0000'/'1', grouped by software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1':***

***Caught exception during application deployment from SAP J2EE Engine's deploy API:***

***com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: java.lang.NullPointerException***

***Exception is:***

***java.lang.NullPointerException*** at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:666)

at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:332)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)

at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)

at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)

at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)

at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)

at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)

at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)

at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)

at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)

at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)

at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)

at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)

at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)

at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)

at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)

at com.sap.sdm.control.command.Command.exec(Command.java:42)

at SDM.main(SDM.java:21)

;

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

Jan 6, 2009 9:54:45 AM Info: Starting to save the repository

Jan 6, 2009 9:54:46 AM Info: Finished saving the repository

Jan 6, 2009 9:54:46 AM Info: Starting: Initial deployment: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1' will be deployed.

Jan 6, 2009 9:54:46 AM Error: Aborted: software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152326''/'1':

Failed deployment of SDAs:

development component 'irj'/'sap.com'/'SAP AG'/'7.0014.20071112134549.0000'/'1' : aborted

Please, look at error logs above for more information!

Jan 6, 2009 9:54:46 AM Info: Starting to save the repository

Jan 6, 2009 9:54:47 AM Info: Finished saving the repository

Jan 6, 2009 9:54:47 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Jan 6, 2009 9:54:47 AM Error: -

---

At least one of the Deployments failed -

---

Jan 6, 2009 9:54:48 AM Info: Summarizing the deployment results:

Jan 6, 2009 9:54:48 AM Error: Aborted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC14_0.SCA

Jan 6, 2009 9:54:48 AM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC214_0.SCA

Jan 6, 2009 9:54:48 AM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPPSERV14_0.SCA

Jan 6, 2009 9:54:48 AM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPWDC14_0.SCA

Jan 6, 2009 9:54:48 AM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/UWLJWF14_0.SCA

Jan 6, 2009 9:54:48 AM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/SAPEU14_0.SCA

Jan 6, 2009 9:54:48 AM Error: Processing error. Return code: 4

Awaiting for early reply,

Hi ,

I would like to add some of my observations

1. I checked in jcmon that SDM status is showing stopped.

2.I tried to start the SDM by executing the command StartServer.sh and got message that it was started successfully but in jcmon it is still showing as "stopped".

I am not sure whether the above problem is due to this.

Additionally, I would like to mention that my JDK version is 1.4.2_17 and platform is HP-UX11.31

Regards,

Moulinath

Edited by: Moulinath Ray on Jan 6, 2009 8:07 AM

Edited by: Moulinath Ray on Jan 6, 2009 8:08 AM

[Former Member · Accepted solution]

Yes SDM might be the problem, you cannot deploy without SDM. Check the dev_sdm log file in the work directory. One of the last lines should show if it started correctly:

JLaunchISetState: change state from [Starting (2)] to [Running (3)]

Likely causes are, Filesystem full, or database space exhausted.

Best regards, Michael

Edit: i checked jcmon, and SDM should have status running

[Former Member · Accepted solution]

Hi,

Thank you very much for your reply.

1. I checked the file system.One file system is showing full.

DevFS 11 11 0 100% /dev/deviceFileSystem

Please let me know how can I reduce it / deletion of which files will not cause any harm?

2. There is space remaining in Database.So, no problem with it.

3. I found the following message from sdm_log

$ tail dev_sdm

[Thr 2] Mon Jan 5 20:47:02 2009

[Thr 2] JLaunchRequestFunc: receive command:17, argument:0 from pid:14451

[Thr 2] JLaunchIShutdownInvoke: set shutdown interval (stop:1231168622/end:1231168742/TO:120)

[Thr 2] JLaunchProcessCommand: Invoke VM Shutdown

[Thr 2] JHVM_FrameworkShutdownDirect: invoke direct shutdown

[Thr 2] JLaunchISetState: change state from [Running (3)] to [Stopping (5)]

[Thr 6] JLaunchIExitJava: exit hook is called (rc = 0)

[Thr 6] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 6] JLaunchCloseProgram: good bye (exitcode = 0)

4. In jcmon also, the status is showing as stopped.

5. I tried to start the SDM by executing command Startserver.sh fron /usr/sap/<SID>/DVEBMGS00/SDM/program

But it is not starting.The process is getting hanged.

$ ./StartServer.sh

running on HP-UX better use the '-XdoCloseWithReadPending' option

Starting SDM - Software Deployment Manager...

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

JStartupFramework is active

Operation mode of SDM in JStartupFramework is "Standalone". Simply start the server.

Initializing Network Manager (50017)

Starting SDM Server listening on port 50018

SDM started successfully.

Redirecting output to the two files "/usr/sap/IN1/DVEBMGS00/SDM/program/log/sdm_server.out" and "/usr/sap/IN1/DVEBMGS00/SDM/program/log/sdm_server.err" respectively.

6. One more point to mention is that the value of one kernel parameter "nkthread" is not matching with prescribed value>=10000. But I could not change the value and so proceeded with the installation.Can this be a root cause? While installing ECC only with ABAP+JAVA , I did not find any problem but this time I am facing the problem.

Please let me know your valueable inputs.

Thanks and Regards,

Moulianth

N.B. I just now checked the file system size of my ECC6.0 installation with ABAP+JAVA which finished successfully.There also the device file system was full.So, it seems that this is not the problem.

Edited by: Moulinath Ray on Jan 7, 2009 5:21 AM

[Former Member · Accepted solution]

1. ok, not a problem

2. ok

3. displays your SDM was shutdown jan 5th

4.

5. looks fine, SDM was started "standalone", not so sure if that could be a problem

6. nkthread: is the limit of threads on the server. I checked it on our boxes, the default is 8416, which should be ok. Besides that an SDM i checked had only 18 threads. But a j2ee server process can have easily 300 threads and more. You can verify the setting with: /usr/sbin/kctune nkthread

Could you please also check the sdm_server.out and sdm_server.err. I guess you already did several retries in sapinst, and the problem stays the same?

This document might also be helpful, but it is more for general SDM problems: [SDM Troubleshooting|http://help.sap.com/erp2005_ehp_04/helpdata/DE/76/fb72ec091f4bf8a2d8ba321bb7e8d9/frameset.htm]

Regards Michael

[Former Member · Accepted solution]

Hi,

1. I checked that the files do not exist.

$ ls -lrt |grep sdm*

-rw-rr 1 in1adm sapsys 681 Jan 5 20:46 std_sdm.out

-rw-rr 1 in1adm sapsys 15353 Jan 5 20:47 dev_sdm

-rw-rr 1 in1adm sapsys 1139 Jan 5 20:47 jvm_sdm.out

$ ls -lrt |grep sdm_server.out

$ ls -lrt |grep sdm_server.err

Should I create these files and then try to restart the SDM?

2. Here I am providing the message from jvm_sdm.out.

$ tail jvm_sdm.out

Starting SDM Server listening on port 50018

SDM started successfully.

Connection #1 ( SDM: 20090105151626)

End Connection #1

Connection #2 ( SDM: 20090105151701)

JControl is shutting SDM Server down

Asynchroneously processing shutdown request.

Server finished sending back the answer of the ShutdownRequest.

Shutting dispatcher down

Bye, bye!

Please help me out . By the mean time I am going through the SDM trouble shooting guide.

Thanks and Regards,

Moulinath Ray

[Former Member · Accepted solution]

Hi,

1. I checked that the files do not exist.

$ ls -lrt |grep sdm*

-rw-rr 1 in1adm sapsys 681 Jan 5 20:46 std_sdm.out

-rw-rr 1 in1adm sapsys 15353 Jan 5 20:47 dev_sdm

-rw-rr 1 in1adm sapsys 1139 Jan 5 20:47 jvm_sdm.out

$ ls -lrt |grep sdm_server.out

$ ls -lrt |grep sdm_server.err

Should I create these files and then try to restart the SDM?

2. Here I am providing the message from jvm_sdm.out.

$ tail jvm_sdm.out

Starting SDM Server listening on port 50018

SDM started successfully.

Connection #1 ( SDM: 20090105151626)

End Connection #1

Connection #2 ( SDM: 20090105151701)

JControl is shutting SDM Server down

Asynchroneously processing shutdown request.

Server finished sending back the answer of the ShutdownRequest.

Shutting dispatcher down

Bye, bye!

Please help me out . By the mean time I am going through the SDM trouble shooting guide.

Thanks and Regards,

Moulinath Ray

[Former Member · Accepted solution]

Hi,

1. I checked that the files do not exist.

$ ls -lrt |grep sdm*

-rw-rr 1 in1adm sapsys 681 Jan 5 20:46 std_sdm.out

-rw-rr 1 in1adm sapsys 15353 Jan 5 20:47 dev_sdm

-rw-rr 1 in1adm sapsys 1139 Jan 5 20:47 jvm_sdm.out

$ ls -lrt |grep sdm_server.out

$ ls -lrt |grep sdm_server.err

Should I create these files and then try to restart the SDM?

2. Here I am providing the message from jvm_sdm.out.

$ tail jvm_sdm.out

Starting SDM Server listening on port 50018

SDM started successfully.

Connection #1 ( SDM: 20090105151626)

End Connection #1

Connection #2 ( SDM: 20090105151701)

JControl is shutting SDM Server down

Asynchroneously processing shutdown request.

Server finished sending back the answer of the ShutdownRequest.

Shutting dispatcher down

Bye, bye!

Please help me out . By the mean time I am going through the SDM trouble shooting guide.

Thanks and Regards,

Moulinath Ray

[Former Member]

Hi,

1. I checked that the files do not exist.

$ ls -lrt |grep sdm*

-rw-rr 1 in1adm sapsys 681 Jan 5 20:46 std_sdm.out

-rw-rr 1 in1adm sapsys 15353 Jan 5 20:47 dev_sdm

-rw-rr 1 in1adm sapsys 1139 Jan 5 20:47 jvm_sdm.out

$ ls -lrt |grep sdm_server.out

$ ls -lrt |grep sdm_server.err

Should I create these files and then try to restart the SDM?

2. Here I am providing the message from jvm_sdm.out.

$ tail jvm_sdm.out

Starting SDM Server listening on port 50018

SDM started successfully.

Connection #1 ( SDM: 20090105151626)

End Connection #1

Connection #2 ( SDM: 20090105151701)

JControl is shutting SDM Server down

Asynchroneously processing shutdown request.

Server finished sending back the answer of the ShutdownRequest.

Shutting dispatcher down

Bye, bye!

Please help me out . By the mean time I am going through the SDM trouble shooting guide.

Thanks and Regards,

Moulinath Ray

Hi Michel,

1. Sorry for posting the same message thrice.Actually I was facing some error and thought that it did not get posted.

2. I found the files sdm_server.out and sdm_server.err. But no entries are there. Previously I searched in wrong directories.

Regards,

Moulinath

Edited by: Moulinath Ray on Jan 7, 2009 10:37 AM

[Former Member]

Hi Michael,

I changed the mode of SDM from Standalone to Integrated. Then I restarted the JAVA. SDM came up along with the JAVA. Then I started sapinst again. But, at the same phase ( 38th step of installation) , the installation stoppped because a deployment was failed and I checked that SDM again went down.

I got the following error message.

tail EPC_activation.log

Jan 7, 2009 5:48:36 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Jan 7, 2009 5:48:36 PM Error: -

---

At least one of the Deployments failed -

---

Jan 7, 2009 5:48:38 PM Info: Summarizing the deployment results:

Jan 7, 2009 5:48:38 PM Error: Aborted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC14_0.SCA

Jan 7, 2009 5:48:38 PM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPBC214_0.SCA

Jan 7, 2009 5:48:38 PM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPPSERV14_0.SCA

Jan 7, 2009 5:48:38 PM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/EPWDC14_0.SCA

Jan 7, 2009 5:48:38 PM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/UWLJWF14_0.SCA

Jan 7, 2009 5:48:38 PM Error: Admitted: /stage/stageecc1/AS_JAVA_DVD/51033513/DATA_UNITS/JAVA_J2EE_OSINDEP_UT/SAPEU14_0.SCA

Jan 7, 2009 5:48:38 PM Error: Processing error. Return code: 4

Can you please have a look into the issue?

Can it be due to curroption of the specific file for whih the deployment is failing?If there is a possibility of this, I can again download the AS_JAVA_DVD and start the installation again.

Thanks and Regards,

Moulinath