EHPI failed in DEPLOY_ONLINE_DEPL

[Former Member]

I am upgrading my PI system from NW700 SPS14 to NW7.01 SPS3 with EHPI.

In the DEPLOY_ONLINE_DEPL it fails because SDM server is being shutdown

while the JSPM is trying to update the SDM repository. My full problem

analysis is below.

Thank you.

Dave

Error...

Error while executing DeploymentManager phase with action deploySlot.

Check the log files for the specified action.

Could not execute deployment of stack file D:\usr\sap\trans\EPS\Sept2009\SPSTab.xml.

JSPM could not log in to the Java server with user SAP*.

Probably the server is not running or the provided credentials are not correct.

JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.

JSPM version is 7.01.3.0.15.

Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.

[Thread[JSPM,5,main]]: Discarding message $com.sap.sdt.sltool.rapi.connector.MsgData@5738ec91

[Thread[main,5,main]]: JSPM was started successfully.

[Thread[main,5,main]]: Trying to log in with user SAP*.

[Thread[main,5,main]]: JSPM successfully logged in with user SAP*.

[Thread[CharacterCommLink,5,main]]: Socket closed

[Thread[JSPM,5,main]]: Reporting failed commlink.

Oct 12, 2009 1:42:11 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream

Oct 12, 2009 1:42:11 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream

Oct 12, 2009 1:42:11 PM [Info]: com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForJSPMTermination(JSPMConnector.java:457) [Thread[main,5,main]]: JSPM stopped.

Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.

Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.

JSPM version is 7.01.3.0.15. Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.

Oct 12, 2009 1:42:11 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:702) [Thread[main,5,main]]: JSPM could not log in to the Java server with user SAP*. Probably the server is not running or the provided credentials are not correct.

[Thread[main,5,main]]: Could not execute deployment of stack file D:\usr\sap\trans\EPS\Sept2009\SPSTab.xml.

[Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.

Start CMD

cd D:\usr\sap\DPI\DVEBMGS01\SDM\program

.\stopserver.bat

This should end with return code =104-no server running.

sdm.bat jstartup u201Cmode=standaloneu201D

sdm.bat changepassword u201Cnewpassword={enter password here as per password file}u201D

sdm.bat jstartup u201Cmode=integratedu201D

u2026no luck

Also tested the password by logging into SDM Guiu2026

sdm.bat remotegui (need to start the SDM server for this)

u2026no luck

Tried increasing java heap memory used by SDM from 256M to 512M as per OSS Note 1264514 and OSS Note 879377.

u2026no luck

When I look at jcontrol in SAPMMC I can seeu2026that the status of the jcontrol was "Some processes running [Safe Mode]

Follow Note 1267123 - System remains in SAFE mode after update.pdf u2026

Start CMD

cd D:\usr\sap\DPI\DVEBMGS01\j2ee\configtool

.\configtool.bat

The J2EE Engine Config Tool starts.

Menu File -> Safe Mode

Choose Safe Mode Enabled = NO then OK

Exit

Apply changes? = Yes

Logs Message appears, OK

OK

Restart SAP System 01 ONLY in SAPMMC then totally get out of SAPMMC before proceeding.

u2026no luck

OK the SDM server is failing to start so Iu2019ll look into thatu2026

Try to start manually in standalone modeu2026as per commands above.

u2026no luck

Follow the EHPI_Java Troubleshooting Guide.

Only suggestion is to stop the EHPI Java processes after setting the SDM server to normal mode.

u2026no luck

Look at JSPM logu2026

Oct 12, 2009 1:42:04 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been started.

Oct 12, 2009 1:42:04 PM [Info]: Phase type is com.sap.sdt.jspm.phases.PhaseTypeLupJSPM.

Oct 12, 2009 1:42:04 PM [Info]: Message type received login.

Oct 12, 2009 1:42:04 PM [Info]: Processing login request for user SAP*.

Oct 12, 2009 1:42:04 PM [Info]: Detecting system parameters...

Oct 12, 2009 1:42:04 PM [Info]: You can find additional information in log file D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52\DETECT_SYSTEM_PARAMETERS_01.LOG.

Oct 12, 2009 1:42:08 PM [Info]: Detection of system parameters has finished.

Oct 12, 2009 1:42:09 PM [Info]: Checking connectivity for SDM server on host DVW3SAPPI01, port 50118...

Oct 12, 2009 1:42:10 PM [Error]: com.sap.sdm.apiimpl.remote.client.APIRemoteExceptionImpl: Server DVW3SAPPI01 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server DVW3SAPPI01 at port 50118: Connection refused: connect

Oct 12, 2009 1:42:10 PM [Error]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.

Oct 12, 2009 1:42:10 PM [Info]: Could not process login request for user SAP*.

Oct 12, 2009 1:42:10 PM [Error]: JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.

JSPM version is 7.01.3.0.15. Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.

Oct 12, 2009 1:42:10 PM [Info]: Message type received disconnect.

Oct 12, 2009 1:42:10 PM [Info]: Remote connection is closed.

Oct 12, 2009 1:42:10 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.

Oct 12, 2009 1:42:10 PM [Info]: Start time: 2009/10/12 13:42:04.

Oct 12, 2009 1:42:10 PM [Info]: End time: 2009/10/12 13:42:10.

Oct 12, 2009 1:42:10 PM [Info]: Duration: 0:00:06.172.

Oct 12, 2009 1:42:10 PM [Info]: Phase status is initial.

OK definitely looks like we need to get that SDM server running!

Look at the SDM logsu2026

Maybe itu2019s just because the SDM is set to standalone? I set it to integrated!

Restart SAP System 01 ONLY in SAPMMC then totally get out of SAPMMC before proceeding.

u2026no luck

Iu2019m going back to the VM Clone to double check the SDM and SAP* and j2ee_admin passwords.

u2026no lucku2026because we are not rolling back the database when we do this.

Found new erroru2026some error about localhost so added changes to host file.

u2026no luck

OK now we up the logging on the SDM Server and find out why it is not runningu2026

Canu2019t find why? I am sure that in fact the EHPI is shutting it down.

Updated the kernel as per OSS Note 1274006 and 1122058 and per Kreasanu2019s suggestion.

Shutdown all SAP processes, unpacked kernel into SYS directory, restarted SAP, restarted EHPI (not from the start though).

u2026no luck

[sunny_pahuja2 · Accepted solution]

Hi,

> Probably the server is not running or the provided credentials are not correct.

> JSPM is unable to logon to SDM. Check that SDM password is correct and the system is up and running.

> JSPM version is 7.01.3.0.15.

> Current JSPM log directory is D:\usr\sap\DPI\DVEBMGS01\j2ee\JSPM\log\log_2009_10_12_13_41_52.

>

First thing before starting EHP upgrade, have you synchronized SDM as mentioned in upgrade guide ?

Second reason for this error is you have given wrong SDM password in configuration phase.

Please check above.

Thanks

Sunny

[Former Member · Accepted solution]

Thanks Sunny,

Yes, I did synchronize the sdm repository during the preparation step of the ehpi install.

Yes, I have tested the SDM password. If I manually change the sdm server to integrated and start the sdm server than I am able to log into the sdm remotegui with the password.

Kind regards,

Dave

[sunny_pahuja2 · Accepted solution]

Hi Dave,

Check SAP Note 701654 - Deployment aborts due to wrong J2EE Engine login information

Thanks

Sunny

[Former Member · Accepted solution]

Hello

Check whether j2ee_admin password matches with secure store value

Regards

[Former Member · Accepted solution]

Thank you Sunny and Supriya,

In fact because the UME has been set to ABAP, and the j2ee_admin is on the ABAP, it is not used because the ABAP has been moved to the shadow and is locked for upgrade.

What SAPjup does then is create a SAP* on the java and changes the secure store to use the SAP* user. I have double checked the secure store and I am able to log into the NWA as the SAP*(java) user (although the screen is blank like there is no user context).

The log file also shows that the SAP* user is being used.

The problem seams to be more that the SDM server is not running, and in fact it's not. Even if I change it to mode=integrated and start it, the upgrade stops teh server then changes it back to mode=standalone for some reason? The sdmlog###.log shos this but there are no errors.

Kind regards,

Dave

[Former Member · Accepted solution]

Further info...

The failing step is deployment of SAP_JAVASL with the message "Cannot update SDM. Could not auto-update SDM Server. Cannot execute java process for AutoUpdate. return code condition success evaluated to false for process java.exe for action ACTION_AUTO_UPDATE".

I understand that the SDM is being patched during this step, so it makes sense that the SDM server is shutdown during this step. How do I progress through this?

Kind regards,

Dave

[sunny_pahuja2 · Accepted solution]

Hi Dave,

Check below thread:

/thread/179386 [original link is broken]

Thanks

Sunny

[Former Member · Accepted solution]

Hi Sunny,

Thank you, I appreciate your interest in my problem.

I have seen the thread you have refered to before.

Michael says that fix was to let SAP repair the sdm repository. I can't do this because I have no SAP Gateway. I also don't think that this is really a good solution because 'what happens when I do prod'?

Markus idea about updating the SDM manually seams like a good thing to try...again it seams a bit dodgy, especially if there are no sap notes to support this practice. However I would be prepared to try it.

Problem I have now, is I played with the JSPM directly now (I know SAP say not to but I was running out of options and I got curious). I tried to just patch the SAP_JAVASL by itself to 7.01.5.1. It got a similar error anayhow. Problem now is the deployment queue is stuffed and SAPjup is confused. I'll have to roll back and try again. It''l take a few days. Then I'll post an update.

Kind regards,

Dave