Erorr in phase DEPLOY_ONLINE_DEPL

[Former Member]

Hello Netweaver Expert,<br><br>

I get an erorr when upgrade sap netweaver pi 7.1 to EHP1 in phase DEPLOY_ONLINE_DEPL. This the log of \usr\sap\<SID>\EHPI\java\log:<br><br>

LOGHEADER[START]/--><br>

HELP[Manual modification of the header may cause parsing problem!]/--><br>

LOGGINGVERSION[2.0.7.1006]/--><br>

NAME[ :\usr\sap\DXI\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_28.LOG]/--><br>

PATTERN[DEPLOY_ONLINE_DEPL_DDB_28.LOG]/--><br>

FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/--><br>

ENCODING[UTF8]/--><br>

LOGHEADER[END]/--><br><br>

Aug 24, 2010 10:34:47 PM:<br>

com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been started.

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter action=deploySlot

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter connect=standard

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter errorStrategy=skipDepending

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter rule=all

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:570) [Thread[main,5,main]]: Phase parameters have been checked. All required 1 phase parameters have been set.

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM.

Aug 24, 2010 10:34:47 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:161) [Thread[main,5,main]]: JSPM is not connected, trying to start it.

Aug 24, 2010 10:34:48 PM [Info]: com.sap.sdt.util.proc.Process.start(Process.java:164) [Thread[main,5,main]]: :\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp :\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm -boot=win -port=6250 -properties=jspm-srv_config.txt -startJSPM

Aug 24, 2010 10:34:49 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Current log directory is :\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_24_22_34_49.

Aug 24, 2010 10:34:51 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.finished(AbstractToolConnector.java:373) [Thread[Process(:\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp :\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm),5,main]]: JSPM terminated with exit code 0.

Aug 24, 2010 10:34:51 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.handleExitMessage(AbstractToolConnector.java:600) [Thread[JSPM,5,main]]: Handling tool exit with rc=0

Aug 24, 2010 10:34:53 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:721) [Thread[main,5,main]]: Connected to host [host_name] on port 6250.

Aug 24, 2010 10:35:07 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:164) [Thread[main,5,main]]: JSPM was started successfully.

Aug 24, 2010 10:35:07 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:207) [Thread[main,5,main]]: Trying to log in with user SAP*.

Aug 24, 2010 10:35:16 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:219) [Thread[main,5,main]]: JSPM successfully logged in with user SAP*.

Aug 24, 2010 10:35:16 PM [Info]: com.sap.sdt.util.net.AbstractCharacterCommLink.read(AbstractCharacterCommLink.java:131) [Thread[CharacterCommLink,5,main]]: socket closed

Aug 24, 2010 10:35:16 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.handleMsgClosed(AbstractToolConnector.java:552) [Thread[JSPM,5,main]]: Reporting failed commlink.

Aug 24, 2010 10:35:17 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream

Aug 24, 2010 10:35:17 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Closed input stream

Aug 24, 2010 10:35:17 PM [Info]: com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForJSPMTermination(JSPMConnector.java:457) [Thread[main,5,main]]: JSPM stopped.

Aug 24, 2010 10:35:17 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.

Aug 24, 2010 10:35:17 PM [Error]: com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123) [Thread[main,5,main]]:<b> Check account for user SAP* failed. JSPM is unable to logon on AS Java</b>.

JSPM version is 7.11.5.0.18. Current JSPM log directory is :\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_24_22_34_49.

Aug 24, 2010 10:35:17 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:714) [Thread[main,5,main]]: <html>The following <b>/thread/1625419 [original link is broken], but i do not know what's his/her solution to solve his/her problem. I change check my pswd in secstore and add profiles SAP_NEW for SAP* in shadow instance, but still get same problem :(. <br><br>

Any suggestion to help me please ?<br><br>

Regards<br>

FX<br><br>

Edited by: felix tansulla on Aug 24, 2010 6:34 PM

[tomas_black]

Hello Felix,

one more try. Documentation says:

In a dual-stack system:
during the phase DEPLOY_ONLINE_DEPL the JAVA instance is disconnected from ABAP instance; ABAP instance must be down; SAPJup changes the following UME parameters:

(In the Configtool: cluster-data  >Global Server configuration  > services  >comp.sap.security.core.ume.service)

ume.persistence.data_source_configuration= dataSourceConfiguration_database_only.xml

ume.login.guest_user.uniqueids=SAP*

ume.superadmin.activated=TRUE

ume.superadmin.password= <SAP* password, entered in PREPARE dialog>

So please double check the SAP* password in both

Configtool: cluster-data >Global Server configuration > services >comp.sap.security.core.ume.service >

>ume.superadmin.password <

Configtool > secure store >

> admin/password/<SID> <

(of course the password must be the one entered in PREPARE phase)

Let us know if this has worked out.

Tomas Black

[Former Member]

Dear mr. black,

Many thank for your suggestion. Before, we have check for everything that just like you have been said. And still ge the same problem. Now, i have try to check again, and still get the same problem ;(

This is the configuration in our configtool:

ume.persistence.data_source_configuration = dataSourceConfiguration_database_only.xml

ume.login.guest_user.uniqueids = SAP* (but before the upgrade process is J2EE_GUEST)

ume.superadmin.activated = TRUE (i have ever try to set that value to FALSE, but my AS JAVA in SAP MMC can not running, then i set back to TRUE.)

ume.superadmin.password= <password> ( i have check this password in many many times. To prove and test it, i logon to my shadow ABAP stack with client 000 using SAP*. I can logon sucessfully and can acces many tcode.)

But in Configtool > secure store >, i cannot find admin/password/<SID>. In my configtool > secure store, there are 2 tabs: secure store data and connection pools. In secure store data tab there is no value, but in connection pools there are 4 value:

ClassName = oracle.jdbc.driver.OracleDriver

Password = <my SAPSR3DB pswd>

URL = jdbc:oracle:thin:@<host_name>:1527:<SID>

User = SAPSR3DB

My configtool and JSPM tool have been update by EHP installer to version 7.1105, before that is 7.104. I have check and test the password in that area (in connection pools tab) using this treatment:

i input the wrong paswd to the field password, then restart my instance in SAP MMC. So, what happen next ? My server can not running. Then i check my db user using sqlplus. SAPSR3DB has been lock by the system because i input the wrong paswd. So, what the next ? I unlock the SAPSR3DB and change the paswd in passwd field at connection pools tab with the correct paswd, start my server again, and my server running in green color ;). So, the conclusion is my paswd that i have been put to the field passwd at connection pools tab is really really correct.

So, any other idea ? Please don't give up to help me

Regards

FX

Edited by: felix tansulla

on Aug 30, 2010 8:01 AM

[Former Member]

dear mr black,<br><br>

I have make a mistake. My passwd for SAP* when in prepare phase is different with SAP* from initial setup. So, now i change the paswd at <b>ume.superadmin.password</b> wiht my SAP* password when in prepare phase. Then i restart my server, and continue the EHP installation, but DEPLOY_ONLINE_DEPL hang up up to more than 7 hours, there is no progress in log file. Then i try to logon to ABAP stack of my shodow system using SAP* and password that i have input in prepare phase, but faile. The error message say: inccorect paswd. But i can logon sucesfully using SAP* with paswd of my initial setup. This is normal or any something wrong ? Please every one help me.<br><br>

This the log content after i change my <b>ume.superadmin.password</b> with password that i have been input in prepare phase:<br><br>

LOGHEADER[START]/--><br>

HELP[Manual modification of the header may cause parsing problem!]/--><br>

LOGGINGVERSION[2.0.7.1006]/--><br>

NAME[E:\usr\sap\DXI\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_64.LOG]/--><br>

PATTERN[DEPLOY_ONLINE_DEPL_DDB_64.LOG]/--><br>

FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/--><br>

ENCODING[UTF8]/--><br>

LOGHEADER[END]/--><br><br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been started.<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter action=deploySlot<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter connect=standard<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter errorStrategy=skipDepending<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter rule=all<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:570) [Thread[main,5,main]]: Phase parameters have been checked. All required 1 phase parameters <br>have been set.

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM.<br>

Aug 30, 2010 1:14:28 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:161) [Thread[main,5,main]]: JSPM is not connected, trying to start it.<br>

Aug 30, 2010 1:14:29 PM [Info]: com.sap.sdt.util.proc.Process.start(Process.java:164) [Thread[main,5,main]]: E:\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp e:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm -boot=win -port=6250 -properties=jspm-srv_config.txt -startJSPM<br>

Aug 30, 2010 1:14:30 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Current log directory is E:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_30_13_14_30.<br>

Aug 30, 2010 1:14:31 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.finished(AbstractToolConnector.java:373) [Thread[Process(E:\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp e:\usr\sap\DXI\DVEBMGS00<br>\j2ee\JSPM<br>\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm),5,main]]: JSPM terminated with exit code 0.<br>

Aug 30, 2010 1:14:34 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:721) [Thread[main,5,main]]: Connected to host jktbtrsapx1 on port 6250.<br>

Aug 30, 2010 1:14:47 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:164) [Thread[main,5,main]]: JSPM was started successfully.<br>

Aug 30, 2010 1:14:47 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:207) [Thread[main,5,main]]: Trying to log in with user SAP*.<br>

[Former Member]

Hi Felix,

Try to login to JSPM and check whether you are able to login. If you are not able to login, then there is issue in password.

Regards,

Ranjith

[Former Member]

HI Ranjith,

I can not logon to my JSPM tool. It hang up too, so do you know to solve this password issue ?

Regards

FX

[tomas_black]

Hello Felix,

please provide the content of JSPM.TRC file (the last part, where we can see the ERROR messages).

Regards,

Tomas Black

[Former Member]

Dear Tom,

When i use my JSPM tool using sap* and the paswd is paswd from prepare phase, the JSPM hang up. I wait more than 1 hour, there is nothing happen. Then i close the JSPM tool, and there is no log file has been created in foldel JSPM\trc. But if i logon using sap* dan the paswd is master paswd from initial setup, one log created, the log say:

Aug 31, 2010 1:00:19 PM [Error|http://forums.sdn.sap.com/]: com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123) [Thread[CharacterCommLink,5,main]|http://forums.sdn.sap.com/]: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

Aug 31, 2010 1:00:19 PM [Error|http://forums.sdn.sap.com/]: com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor [Thread[CharacterCommLink,5,main]|http://forums.sdn.sap.com/]: com.sap.sdt.util.diag.DiagException: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

The JSPM.TRC created only when i'm not use paswd in prepare phase. So, how to analyze ?

[Former Member]

Dear Tom,<br><br>

After retry in many time, finally the JSPM.TRC created and appear in folder JSPM\trc. This is the content of JSPM.TRC file:<br><br>

Aug 31, 2010 6:27:18 PM [Error]:<br>

com.sap.sdt.j710.deploymentmgr.DeploymentManagerImpl [Thread[CharacterCommLink,5,main]]: com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.

Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.<br><br>

Aug 31, 2010 6:27:18 PM [Error]: <br>com.sap.sdt.j710.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:1310) [Thread[CharacterCommLink,5,main]]: com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.

Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.<br><br>

Aug 31, 2010 6:27:18 PM [Error]: <br> com.sap.sdt.j710.deploymentmgr.DeploymentManagerImpl [Thread[CharacterCommLink,5,main]]: com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.

Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.

at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:204)

at com.sap.engine.services.dc.api.session.impl.SessionImpl.<init>(SessionImpl.java:129)

at com.sap.engine.services.dc.api.session.impl.SessionFactoryImpl.newSession(SessionFactoryImpl.java:31)

at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:110)

at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:73)

at com.sap.sdt.j710.deploymentmgr.DeploymentControllerFacade.connectDC(DeploymentControllerFacade.java:305)

at com.sap.sdt.j710.deploymentmgr.DeploymentControllerFacade.connect(DeploymentControllerFacade.java:117)

at com.sap.sdt.j710.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:1305)

at com.sap.sdt.jspm.gui.AbstractSystemInitializer.checkAccount(AbstractSystemInitializer.java:408)

at com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:118)

at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:135)

at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:118)

at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:247)

at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:579)

at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:229)

at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:146)

at java.lang.Thread.run(Thread.java:666)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.rmi_p4.P4ConnectionException: Error. Check your available working servers. Error message: server crashed while processing the request]

at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:519)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:387)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.InitialContext.<init>(InitialContext.java:197)

at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:181)

... 16 more

Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Error. Check your available working servers. Error message: server crashed while processing the request

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:743)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:725)

at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:148)

at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:395)

... 1 more<br><br>

Aug 31, 2010 6:27:18 PM [Error]: <br>com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123) [Thread[CharacterCommLink,5,main]]: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

Aug 31, 2010 6:27:18 PM [Error]: <br> com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor [Thread[CharacterCommLink,5,main]]: com.sap.sdt.util.diag.DiagException: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

at com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123)

at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:135)

at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:118)

at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:247)

at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:579)

at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:229)

at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:146)

at java.lang.Thread.run(Thread.java:666)<br><br>

Aug 31, 2010 6:27:18 PM [Error]:<br>com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123) [Thread[CharacterCommLink,5,main]]: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

JSPM version is 7.11.5.0.18. Current JSPM log directory is E:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_31_15_19_55.<br>

Aug 31, 2010 6:27:18 PM [Error]: <br> com.sap.sdt.jspm.unattended.RequestController [Thread[CharacterCommLink,5,main]]: com.sap.sdt.util.diag.DiagException: Check account for user SAP* failed. JSPM is unable to logon on AS Java.

JSPM version is 7.11.5.0.18. Current JSPM log directory is E:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_31_15_19_55.

at com.sap.sdt.jspm.unattended.processors.LoginRequestProcessor.process(LoginRequestProcessor.java:123)

at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:135)

at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:118)

at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:247)

at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:579)

at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:229)

at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:146)

at java.lang.Thread.run(Thread.java:666)<br><br>

Aug 31, 2010 6:27:19 PM [Error]: <br> com.sap.sdt.ucp.pce.ctrl.ExecutionDialog [Thread[main,5,main]]: Unable to process dialog ScrollDialog: Could not send dialog message. See previous messages.

Unable to send message. See previous message.

Communication link is closed.<br><br>

Aug 31, 2010 6:27:19 PM [Error]: <br> com.sap.sdt.ucp.pce.ctrl.ExecutionDialog [Thread[main,5,main]]: Unable to process dialog ScrollDialog: Could not send dialog message. See previous messages.

Unable to send message. See previous message.

Communication link is closed.<br><br>

Aug 31, 2010 6:27:19 PM [Error]: <br> com.sap.sdt.ucp.pce.ctrl.ExecutionDialog [Thread[main,5,main]]: Unable to process dialog ScrollDialog: Could not send dialog message. See previous messages.

Unable to send message. See previous message.

Communication link is closed.<br><br>

An this the content of deploy log in folder \j2ee\JSPM\log\:<br>

LOGHEADER[START]/-->

HELP[Manual modification of the header may cause parsing problem!]/-->

LOGGINGVERSION[2.0.7.1006]/-->

NAME[E:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_31_15_19_55\deploy_2010-08-31_15-20-10.log]/-->

PATTERN[deploy_2010-08-31_15-20-10.log]/-->

FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/-->

ENCODING[UTF8]/-->

LOGHEADER[END]/--><br><br>

Aug 31, 2010 3:20:10 PM [Info ]:DC API is trying to connect to 'host_name:50004'

Aug 31, 2010 6:27:18 PM [Error ]:[ Exception ]::SessionImpl::getContext():[get ctx. NamingException],cause=Exception during getInitialContext operation. Cannot establish connection to the remote server.<br><br>

Regards<br>

FX

[tomas_black]

Hello Feliz,

see here:

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. Root exception is com.sap.engine.services.rmi_p4.P4ConnectionException: Error. Check your available working servers. Error message: server crashed while processing the request 

This might be that the J2EE is just not up. Or it might be an issue with the P4 communication protocol - JSPM is 'crashing' for some reason.

Please check notes #883943 and #955233 for this.

If the issue persists, please check note #993189 - what's the JDK version you're using?

Best regards,

Tomas Black

[Former Member]

I use JDK 1.4.2

[Former Member]

Hi Felix,

Try change your value ume.persistence.data_source_configuration from config tool to dataSourceConfiguration_database_r3_rw.xml. So your ume.persistence.data_source_configuration will be look like this:

<b>ume.persistence.data_source_configuration = dataSourceConfiguration_database_r3_rw.xml</b>

May be helpfull.

Regards

Hendri

[Former Member]

Hi Felix,

If you change your data source to ABAP, then you cannot revert back, so be careful before changing the data source.

Regards,

Ranjith

[tomas_black]

Hello Felix,

assuming you've double checked the SAP* password, it could be that JSPM was not bootstrap or deployed correctly.

Please perform the following steps

1) use forced J2EE bootstrap so all the content will be extracted from database to the file system

1.1) open the following file for edit:

/usr/sap/<SID>/DVEBMGS## /j2ee/cluster/bootstrap/bootstrap.properties

1.2) edit element.resynch parameter:

element.resynch = FORCE

1.3) restart J2EE engine

Also please, try to upgrade the SAP JVM, to do that read note #1133020 - How to import a SAP JVM patch into an AS in case you have problem to perform it try do manually patch according with note #1025085 - How to manually patch the SAPJVM 5.1.

After that, please try to continue the installation.

I hope this helps.

Best regards,

Tomas Black

[Former Member]

Thx for reply mr. black,

I have check my file system :\usr\sap\<SID>\SYS\exe\jvm\NTAMD64, there are 2 folder about sap JVM: sapjvm_5.1.015 and sapjvm_5.1.053. I think my EHP installer has been deploy SAPJVM package succesfully. So i do not need to extract SAPJVM5_53-10004442.SAR file manually. But i follow another step in sap note 1025085 (step 6 - 10), and delete folder sapjvm_5.1.015. Then i start EHP installer again, but still get same problem with same log error

Any other idea please ?

Regards

FX

Edited by: felix tansulla on Aug 26, 2010 8:54 AM

[Former Member]

Hi Felix,

Stop the instance manually and clean the shared memory, then start the instance and continue the failed step.

Even i got the same error while upgrading from EP 7.0 to EHP1. following the above procedure resolved my issue.

Regards,

Ranjith

[Former Member]

Dear Kumar,

We use Windos Server 2003, and Oracle 10 g. How do we to clean shared memory in Windows? I think "cleanipc" command only work in UNIX system.

Regards

FX

[tomas_black]

Hello Felix,

no, cleanipc command does not work in Windows. The equivalent command in MS Windows systems is 'reboot'

FYI I'm still trying to find out a solution for your problem.

Best regards,

Tomas Black

[Former Member]

Hi

Go to the shadow instance path on file system and run the JSPM from the shadow instance. Use the user name sap* and the password and check u can login to it or not.

make sure in mmc the abap and java are up.

make sure the shadow instance is also up in mmc

please let me know the result

Thanks

[Former Member]

Thx for reply Kiran,

My shadow file system (DVEBMGS02) didn't have JSPM folder, so i can not exceute the go.bat. It exist on my original file system DVEBMGS00. When i start the JSPM tool from my original file system and login using sap*, it's hang up. <br><br>

Regards<br>

FX