EHPI failed in DEPLOY_ONLINE_DEPL

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

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

Similar Messages

  • Solman upgrade 7.1 error in  PREPARE_JSPM_QUEUE

    Hi All,
    We are upgrading solman from 7.0 EHP1 to 7.1 , getting the below error in  PREPARE_JSPM_QUEUE phase
    " Checking whether product SAP SOLUTION MANAGER with version 7.1 is supported by this EHP Installer.
    Feb 21, 2012 6:04:32 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.validateProducts(JSPMSpStackQueuePreparator.java:309) [Thread[main,5,main]]: The product is not supported.
    Feb 21, 2012 6:04:32 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."
    I had checked the note Note 1431340 - EHPI fails at PREPARE_JSPM_QUEUE phase - stack rejected, no solution got .
    Can anyone advice please
    Regards,
    Nibu Antony

    Hi
    @ Nirmal
    For solman upgrade tool is Solmanup nad version is as below:
    Client Version 1.5.0 Server Version 1.5.0 Server Port 4241 DSUService
    Version: 1.1.6  Configured Plugins 
    Plugin ABAP at Version:      
    1.0.3      
    Plugin J2EE at Version:      
    1.0.5      
    I had already gone through the thread and the note as mentioned in initially, no luck still..

  • Error in DEPLOY_ONLINE_DEPL phase EHPI 7.01 SPS05 DualStack ABAP+JAVA

    Hello experts,
    I'm getting an error in DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in our BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA)
    The system is running on High Availability server.
    Restarting Q2B 00 instance failed.
    Cannot find instance with instance number 0 on host mcho35au in the cluster.
    I'm not sure, but maybe anything is wrong with my profiles...? I don't know....
    All J2EE deployments has been successfully finished (JSPM).
    I have restarted all instances DVEBMGS00 & SCS01 and Shadow Instance DVEBMGS02. SCS01 Instance is up and running as well.
    Then I have stop EHPI Upgrade and start it again.
    DEPLOY_ONLINE_DEPL_DDB_18.LOG:
    ==========================================
    RequestController.java:178)[Thread[main,5,main]]: Deployment of queue sapjup-queue completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    ==========================================
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    ==========================================
    Any ideas ?
    Please help me in this case.
    I'm wating for any feedbacks.
    Thanks a lot in advance !
    Gerd
    Edited by: Gerd Schuster on Nov 14, 2009 6:23 PM

    Problem:
    The DEPLOY_ONLINE_DEPL phase (Downtime Roadmap) under J2EE tab in enhancement package installation in BW System (Netweaver 7.0 SP 17 to NW 7.01 SPS 05 DualStack ABAP+JAVA, system is running on High Availability server) stopped with error:
    RequestController.java:178)[Threadmain,5,main]: Deployment of queue sapjup-queue
    completedwith error Cannot check the state(running/stoped) of the CI.
    Restarting Q2B 00 Instance failed
    Connot find instance with instance number 0 on host mcho35au in the cluster
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for
    the specified action. Could not execute deployment of stack
    file /usr/sap/trans/EPS/in/SMSDXML_CROSSSYS_20091109075202.238.xml. The deployment
    of the queue failed. Deployment of queue sapjup-queue completed with error Cannot check the
    state(running/stoped) of the CI. Restarting Q2B 00 instance failed. Cannot find instance with instance
    number 0 on host mcho35au in the cluster. JSPM version is 7.01.5.0.20. Current JSPM log directory
    is /usr/sap/Q2B/DVEBMGS00/j2ee/JSPM/log/log_2009_11_14_18_20_03.
    You can find more information in the log file /usr/sap/swdc/EHPI/java/log/DEPLOY_ONLINE_DEPL_DDB_19.LOG.
    Solution:
    stop all instances (shadow instance, SCSxx)
    In a High Availability server you have to modify few parameters in DEFAULT profile temporarily (replace alias-servername with real hostname):
    DEFAULT.PFL: SAPLOCALHOST = mcho35au
    DEFAULT.PFL: SAPDBHOST = mcho35au
    DEFAULT.PFL: rdisp/mshost = mcho35au
    # DEFAULT.PFL: rdisp/vbname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/enqname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    # DEFAULT.PFL: rdisp/btcname = mcho35au_Q2B_00  (<- maby it'snot relevant)
    DEFAULT.PFL: rdisp/sna_gateway = mcho35au
    in instance DVEBMGS00 switch profile icman = 0 to 1 (otherwise J2EE instance will not started)
    startsap DVEBMGS00
    Restart EHPI Upgrade (EHPI keep the old DEFAULT.PFL settings in shared memory!)
    ./EHPI/STARTUP jce_policy_zip=90000125.zip
    Repeat phase DEPLOY_ONLINE_DEPL
    Gerd
    Edited by: Gerd Schuster on Nov 16, 2009 2:59 PM

  • UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL failed

    hi Friends
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file D:/SP09/SPSTab.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11
    DEPLOY_ONLINE_DEPL_DDB_04.LOG;
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[D:\NW7\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_04.LOG]/>
    <!PATTERN[DEPLOY_ONLINE_DEPL_DDB_04.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Jun 8, 2010 9:50:42 AM [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.
    Jun 8, 2010 9:50:42 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.
    Jun 8, 2010 9:50:42 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter action=deploySlot
    Jun 8, 2010 9:50:42 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter connect=standard
    Jun 8, 2010 9:50:42 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter errorStrategy=skipDepending
    Jun 8, 2010 9:50:42 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter rule=all
    Jun 8, 2010 9:50:42 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.
    Jun 8, 2010 9:50:42 AM [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.
    Jun 8, 2010 9:50:42 AM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM.
    Jun 8, 2010 9:50:42 AM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:168) [Thread[main,5,main]]: JSPM was connected successfully.
    Jun 8, 2010 9:50:42 AM [Info]:     com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.deploy(SAPJupJSPMRapiAdapter.java:496) [Thread[main,5,main]]: Starting deployment.
    Jun 8, 2010 9:52:10 AM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
    Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:193) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error Archive with all relevant logs and traces is created in D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\errorReport.zip
    JSPM version is 7.11.4.0.12. Current JSPM log directory is D:\usr\sap\PP4\DVEBMGS00\j2ee\JSPM\log\log_2010_06_07_21_33_11.
    Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:714) [Thread[main,5,main]]: <html>The following <b><a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1399846">SAP Note 1399846</a></b>  may contain solution for the problem.
    Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:706) [Thread[main,5,main]]: The deployment of the queue failed.
    Jun 8, 2010 9:52:10 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file D:/SP09/SPSTab.xml.
    Jun 8, 2010 9:52:10 AM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
    Jun 8, 2010 9:52:10 AM [Info]:                         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.
    Jun 8, 2010 9:52:10 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/08 09:50:42.
    Jun 8, 2010 9:52:10 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/08 09:52:10.
    Jun 8, 2010 9:52:10 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:01:28.065.
    Jun 8, 2010 9:52:10 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    I have searched blogs and followed SAP Note 1371424,1284402, 1251735.
    Nothing relevent and fruitful.
    PI 7.01 SP09----> PI 7.11 SP04
    Please advice.
    Pooja

    Hi,
    Could you please paste latest logs of JSPM ?
    Thanks
    Sunny

  • EHPI PREP_INPUT/INSTANCELIST_PRE fails on SIDADM Password

    PREP_INPUT/INSTANCELIST_PRE fails with
    >>>> Required system passwords <<<<
    The system is running in a distributed environment. To be able to proceed, the
    <SID>adm user will be utilized. Enter the password for the <SID>adm user. In
    case you are using a Windows domain user, please enter the domain user
    password.
    SIDADM PASSWORD: ********
    >>>> Required system passwords <<<<
    The password is correct.  Can SSH to all servers with sidadm and password entered but still fails.
    Have manually typed the pwd, cut an pasted the password, tested all on each server in environment.
    This is a DPF environment with partitions on multiple nodes.  Also has 2 app servers as well.  sidadm connects to all servers as said before both with and without password (RSA Key enabled).

    > We are facing exactly the same issue with an EHP4 installation but on SunOS 5.10.
    > We are using the lastest EHP Installer 7.0 availabe:
    > Patch level 58 - released today 01.02.2011
    >
    > Can you give us some hints?
    Solaris stores passwords in /etc/shadow - which is only readable by root. Since EHPI is started by <sid>adm and there is no option to read that file and compare it with your given password. Solaris has RBAC you can create a role and add a permission for <sid>adm to read the file. An example how to do that is here: http://www.kernelthread.com/publications/security/solaris.html (check the 'ppriv' section). That would be the same as the first part of the note for AIX.
    For point two you can change the permissions as stated in the note for the runtime of EHPI and change it back.
    I'm sure that this issue is either because of a new Solaris release (check /etc/release) or because the method of how SAPehpi checks the password changed. I've done quite a bunch of upgrades on Solaris 10 and I've not had that problem.
    Markus

  • Error in EHPi at downtime phase DEPLOY_ONLINE_DEPL.

    Hello,
    We are getting error in downtime phase DEPLOY_ONLINE_DEPL as java.lang.NullPointerException: null and other term in the error ticket is Error while executing DeploymentManager phase with action deploySlot. I searched the notes pointing to this and none of the notes seem to solve the problem . Also i was not able to find thread related to this. Any help would be appreciated.
    Here is the excerpt of the JSPM trace file
    Jul 12, 2010 6:36:29 PM [Error]: ....sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:275) [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Error]:                                       com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException
         at com.sap.sdt.jspm.deployment.queuemanager.QueueManager.findLastQueue(QueueManager.java:350)
         at com.sap.sdt.jspm.deployment.queuemanager.QueueManager.findQueue(QueueManager.java:326)
         at com.sap.sdt.jspm.deployment.DeploymentFacade.findQueue(DeploymentFacade.java:390)
         at com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:178)
         at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:134)
         at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
         at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
         at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
         at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
         at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
         at java.lang.Thread.run(Thread.java:677)
    Jul 12, 2010 6:36:29 PM [Error]: ....sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:283) [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: Could not process deploy queue sapjup-queue request.
    Jul 12, 2010 6:36:29 PM [Error]: ....sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:296) [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Error]:                                       com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException
         at com.sap.sdt.jspm.deployment.queuemanager.QueueManager.save(QueueManager.java:371)
         at com.sap.sdt.jspm.deployment.DeploymentFacade.save(DeploymentFacade.java:400)
         at com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:290)
         at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:134)
         at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
         at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
         at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
         at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
         at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
         at java.lang.Thread.run(Thread.java:677)
    Jul 12, 2010 6:36:29 PM [Error]:          com.sap.sdt.jspm.tools.eval.JspmEvaluation.createEvaluationResults(JspmEvaluation.java:165) [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Error]:                                                           com.sap.sdt.jspm.tools.eval.JspmEvaluation [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException
         at com.sap.sdt.jspm.tools.eval.CreateJspmEvaluation$ComparableManagedComponent.compareTo(CreateJspmEvaluation.java:607)
         at java.util.Arrays.mergeSort(Arrays.java:1144)
         at java.util.Arrays.mergeSort(Arrays.java:1155)
         at java.util.Arrays.mergeSort(Arrays.java:1155)
         at java.util.Arrays.mergeSort(Arrays.java:1155)
         at java.util.Arrays.sort(Arrays.java:1079)
         at java.util.Collections.sort(Collections.java:117)
         at com.sap.sdt.jspm.tools.eval.CreateJspmEvaluation.sortComponents(CreateJspmEvaluation.java:561)
         at com.sap.sdt.jspm.tools.eval.CreateJspmEvaluation.addComponentInformation(CreateJspmEvaluation.java:271)
         at com.sap.sdt.j2ee.tools.eval.CreateEvaluation.addVersions(CreateEvaluation.java:215)
         at com.sap.sdt.j2ee.tools.eval.CreateEvaluation.createEvaluation(CreateEvaluation.java:167)
         at com.sap.sdt.jspm.tools.eval.JspmEvaluation.createJspmEvaluation(JspmEvaluation.java:267)
         at com.sap.sdt.jspm.tools.eval.JspmEvaluation.createEvaluationResults(JspmEvaluation.java:154)
         at com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:300)
         at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:134)
         at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
         at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
         at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
         at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
         at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
         at java.lang.Thread.run(Thread.java:677)
    Jul 12, 2010 6:36:29 PM [Error]:                                                                  com.sap.sdt.util.diag.DiagException [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: Deserialized exception com.sap.sdt.util.diag.JavaException: java.lang.NullPointerException: null
       at com.sap.sdt.jspm.unattended.processors.ExecuteRequestProcessor.process(ExecuteRequestProcessor.java:275)
       at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:134)
       at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
       at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
       at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
       at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
       at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
       at java.lang.Thread.run(Thread.java:677)
    Jul 12, 2010 6:36:29 PM [Error]:                                                                  com.sap.sdt.util.diag.DiagException [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: Deserialized exception com.sap.sdt.util.diag.DiagException: java.lang.NullPointerException: null
    JSPM version is 7.01.5.1.3. Current JSPM log directory is C:\usr\sap\BWQ\DVEBMGS02\j2ee\JSPM\log\log_2010_07_12_17_14_16.
       at com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178)
       at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:150)
       at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
       at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
       at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
       at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
       at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
       at java.lang.Thread.run(Thread.java:677)
    Jul 12, 2010 6:36:29 PM [Error]:                com.sap.sdt.jspm.unattended.RequestController.logResponse(RequestController.java:242) [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: java.lang.NullPointerException: null
    JSPM version is 7.01.5.1.3. Current JSPM log directory is C:\usr\sap\BWQ\DVEBMGS02\j2ee\JSPM\log\log_2010_07_12_17_14_16.
    Jul 12, 2010 6:36:29 PM [Error]:                                                        com.sap.sdt.jspm.unattended.RequestController [Thread[CommLink(com.sap.sdt.util.net.CharacterCommLink),5,main]]: com.sap.sdt.util.diag.DiagException: java.lang.NullPointerException: null
    JSPM version is 7.01.5.1.3. Current JSPM log directory is C:\usr\sap\BWQ\DVEBMGS02\j2ee\JSPM\log\log_2010_07_12_17_14_16.
         at com.sap.sdt.jspm.unattended.RequestController.logResponse(RequestController.java:242)
         at com.sap.sdt.jspm.unattended.RequestController.processRequest(RequestController.java:153)
         at com.sap.sdt.jspm.unattended.CommunicationController.notifyJSPMRequestListeners(CommunicationController.java:120)
         at com.sap.sdt.jspm.unattended.CommunicationController$JSPMConnectionObserver.receive(CommunicationController.java:249)
         at com.sap.sdt.ucp.communication.SDTServerConnection$SDTServerConnectionObserver.msgReceived(SDTServerConnection.java:589)
         at com.sap.sdt.util.net.AbstractCommLink.fireMsgReceived(AbstractCommLink.java:276)
         at com.sap.sdt.util.net.AbstractCommLink.run(AbstractCommLink.java:218)
         at java.lang.Thread.run(Thread.java:677)
    And the excerpt of the JSPM_MAIN file is as follows:
    Jul 12, 2010 6:36:29 PM [Info]: Message type received execute.
    Jul 12, 2010 6:36:29 PM [Info]: Processing request to deploy queue sapjup-queue.
    Jul 12, 2010 6:36:29 PM [Error]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Error]: Could not process deploy queue sapjup-queue request.
    Jul 12, 2010 6:36:29 PM [Error]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Info]: Adding system configuration.
    Jul 12, 2010 6:36:29 PM [Info]: Generating phase and total run times.
    Jul 12, 2010 6:36:29 PM [Info]: Adding version information.
    Jul 12, 2010 6:36:29 PM [Warning]: Cannot generate JSPM evaluation results.
    Jul 12, 2010 6:36:29 PM [Error]: java.lang.NullPointerException: null
    Jul 12, 2010 6:36:29 PM [Error]: java.lang.NullPointerException: null
    JSPM version is 7.01.5.1.3. Current JSPM log directory is C:\usr\sap\BWQ\DVEBMGS02\j2ee\JSPM\log\log_2010_07_12_17_14_16.
    Please help..!
    We are trying to upgrade NW 7.0 SPS 20 system to NW EHP1 SP 05
    Thanks,
    Sachhi.

    Hi,
    could you please check below things:
    1) Stack xml file should be correct and contains all components.
    2) All the support patches should be in download directory and also in EPS/in.
    Thanks
    Sunny

  • Error in the DEPLOY_ONLINE_DEPL phase in Downtime on Dualstack upgrade

    Hi Gurus,
    again i got struck with another error in the pahse  DEPLOY_ONLINE_DEPL of Downtime.
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file G:/EHP5DUAL/SMSDXML_IJE_20110925114634.078.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error JSPM version is 7.02.8.0.3. Current JSPM log directory is D:\usr\sap\IJE\DVEBMGS01\j2ee\JSPM\log\log_2011_12_07_19_15_55. sap.com/CAF: Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1': Failed deployment of SDAs: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted Please, look at error logs above for more information! Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/LM-TOOLS: Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/ETPRJSCHEDULER: Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/EPBC2: Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/EP-PSERV: Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/SWLIFECYCL: Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/UWLJWF: Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/SAP-EU: Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. The following SAP Note 1399846 may contain solution for the problem.
    You can find more information in the log file G:\EHP5_Down\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_02.LOG.
    Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager com.sap.sdt.ucp.phases.PhaseException Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. DEPLOY_ONLINE_DEPL DEPLOYMENT_BASED_UPGRADE NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
    When reporting problems to SAP Support, attach the trouble ticket file G:\EHP5_Down\EHPI\java\log\TroubleTicket_37.txt to your message.
    JSPM log:
    sap.com/SAP_JTECHS: DEPLOYED
    sap.com/BI_UDI: DEPLOYED
    sap.com/CAF: ERROR
    Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
    Failed deployment of SDAs:
    development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted
    Please, look at error logs above for more information!
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/LM-TOOLS: ERROR
    Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/UMEADMIN: NOT DEPLOYED
    Archive G:\EHP5DUAL\UMEADMIN08_0-10006669.SCA has been admitted for deployment but deployment did not start. ready for update (but not updated yet)
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/NET-PDK: DEPLOYED
    sap.com/ETPRJSCHEDULER: ERROR
    Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/EPBC2: ERROR
    Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/EP-PSERV: ERROR
    Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/EP-WDC: NOT DEPLOYED
    Archive G:\EHP5DUAL\EPWDC08_0-10006502.SCA has been admitted for deployment but deployment did not start. ready for update (but not updated yet)
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/SWLIFECYCL: ERROR
    Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/UWLJWF: ERROR
    Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    sap.com/SAP-EU: ERROR
    Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0':
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/CAF: Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component CAF/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519132845'/1:
    Failed deployment of SDAs:
    development component caf/UI/ptn/common/sap.com/MAIN_NW702P03_C/3520877/1 : aborted
    Please, look at error logs above for more information!
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/LM-TOOLS: Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component LM-TOOLS/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519133035'/1:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/ETPRJSCHEDULER: Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component ETPRJSCHEDULER/sap.com/SAP AG/1000.7.02.8.0.20110519133428'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/EPBC2: Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component EPBC2/sap.com/SAP AG/1000.7.02.8.0.20110519131841'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/EP-PSERV: Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component EP-PSERV/sap.com/SAP AG/1000.7.02.8.0.20110614172722'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/SWLIFECYCL: Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component SWLIFECYCL/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519133223'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/UWLJWF: Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component UWLJWF/sap.com/SAP AG/1000.7.02.8.0.20110519132125'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: sap.com/SAP-EU: Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component SAP-EU/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519132114'/0:
    No further description found.
    Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
    Dec 7, 2011 9:24:48 PM [Error]: Deployment of queue sapjup-queue completed with error
    JSPM version is 7.02.8.0.3. Current JSPM log directory is D:\usr\sap\IJE\DVEBMGS01\j2ee\JSPM\log\log_2011_12_07_19_15_55.
    Thanks in advance
    Venkat

    Hi Siva,
    Log file:sdmcl20111207153503.log
    2011 9:18:11 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Dec 7, 2011 9:18:11 PM   Info: Starting cluster instance processes.
    Dec 7, 2011 9:18:11 PM   Info: Starting the instance JC_admin0001_IJE_01 running on host admin0001
    Dec 7, 2011 9:18:24 PM   Info: Starting the instance JC_admin0001_IJE_01 processes. The instance is running on host admin0001                                                      
    Dec 7, 2011 9:18:24 PM   Info: Starting the process dispatcher
    Dec 7, 2011 9:18:24 PM   Info: Starting the process server0
    Dec 7, 2011 9:22:17 PM   Info: Cluster instance processes have been successfully started.
    Dec 7, 2011 9:22:19 PM   Info: Begin of log messages of the target system:
    11/12/07 21:18:11 -  ***********************************************************
    11/12/07 21:22:17 -  Start updating EAR file...
    11/12/07 21:22:17 -  start-up mode is lazy
    11/12/07 21:22:17 -  EAR file updated successfully for 203ms.
    11/12/07 21:22:17 -  Start updating...
    11/12/07 21:22:18 -  EAR file uploaded to server for 485ms.
    11/12/07 21:22:19 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
                         Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
                              com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:689)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                         Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1052)
                              at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1283)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:402)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:325)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:166)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3241)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:677)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    11/12/07 21:22:19 -  ***********************************************************
    Dec 7, 2011 9:22:19 PM   Info: End of log messages of the target system.
    Dec 7, 2011 9:22:19 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Dec 7, 2011 9:22:19 PM   Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1', grouped by software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
    Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Dec 7, 2011 9:22:19 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:20 PM   Info: Finished saving the repository for 563 ms.
    Dec 7, 2011 9:22:20 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
    Dec 7, 2011 9:22:20 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
    Failed deployment of SDAs:
    development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted
    Please, look at error logs above for more information!
    Dec 7, 2011 9:22:20 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:21 PM   Info: Finished saving the repository for 750 ms.
    Dec 7, 2011 9:22:21 PM   Info: Starting: Update: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0' updates currently deployed software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.6.1.20060305015600''/'0'.
    Dec 7, 2011 9:22:21 PM   Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0':
    No further description found.
    Dec 7, 2011 9:22:21 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:21 PM   Info: Finished saving the repository for 735 ms.
    Dec 7, 2011 9:22:21 PM   Info: Starting: Update: Selected software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0' updates currently deployed software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.6.0.20060305011500''/'0'.
    Dec 7, 2011 9:22:21 PM   Error: Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0':
    No further description found.
    Dec 7, 2011 9:22:21 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:22 PM   Info: Finished saving the repository for 922 ms.
    Dec 7, 2011 9:22:22 PM   Info: Starting: Initial deployment: Selected software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0' will be deployed.
    Dec 7, 2011 9:22:22 PM   Error: Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0':
    No further description found.
    Dec 7, 2011 9:22:22 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:23 PM   Info: Finished saving the repository for 531 ms.
    Dec 7, 2011 9:22:23 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
    Dec 7, 2011 9:22:23 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1':
    No further description found.
    Dec 7, 2011 9:22:23 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:24 PM   Info: Finished saving the repository for 750 ms.
    Dec 7, 2011 9:22:24 PM   Info: Starting: Initial deployment: Selected software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0' will be deployed.
    Dec 7, 2011 9:22:24 PM   Error: Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0':
    No further description found.
    Dec 7, 2011 9:22:24 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:24 PM   Info: Finished saving the repository for 547 ms.
    Dec 7, 2011 9:22:24 PM   Info: Starting: Update: Selected software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0' updates currently deployed software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.6.0.20060305024800''/'0'.
    Dec 7, 2011 9:22:24 PM   Error: Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0':
    No further description found.
    Dec 7, 2011 9:22:24 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:25 PM   Info: Finished saving the repository for 531 ms.
    Dec 7, 2011 9:22:25 PM   Info: Starting: Update: Selected software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0' updates currently deployed software component 'SAP-EU'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.4.20060301135451''/'0'.
    Dec 7, 2011 9:22:25 PM   Error: Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0':
    No further description found.
    Dec 7, 2011 9:22:25 PM   Info: Starting to save the repository
    Dec 7, 2011 9:22:25 PM   Info: Finished saving the repository for 578 ms.
    Dec 7, 2011 9:22:25 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Dec 7, 2011 9:22:25 PM   Error: -
    At least one of the Deployments failed -
    Thanks,
    Venkat

  • Error in EHPI Tool in EHP4 upgrade process

    Hello All,
    I have ECC dual stack server at EHP3 and i am upgrading it to EHP4 via EHPI Tool.
    In EHPI wizard "Configuration" step for ABAP is done properly but in J2EE it is stuck with an error "An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase.
    The stack XML D:\SID_Upgrade_Data\SMSDXML_SID_20091217105348.343.xml is not supported by this EHP installer."
    I have seen the log file of EHPi it says.
    "The stack XML D:\SID_Upgrade_Data\SMSDXML_SID_20091217105348.343.xml is not supported by this EHP installer."
    At the time of creation of Stack configuration xml file i have selected all the SCA from solutiion manager, but i cant understand why J2EE is not accepting  the xml that is properly identified by ABAP?
    What can be the reson for this.
    Pls help.
    Thanks and regards.
    Vinit

    Hello All,
    Now i am in "Downtime" phase of EHPI tool The ABAP Phase is Waiting and in MAIN_NEWBAS/GETSYNC_MODPROF_STARTED Phase.
    The J2EE status is Running and it says Phase DEPLOY_ONLINE_DEPL is running ...
    Although there is no log wriiting since last 15 Hrs. The last log that i came to know says.
    ABAP Log(SAPehpiConsole.log).
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Starting of UPDATE CMOD in batch (job RSMODACU)
    working ...
    >> 2009/12/29 22:07:07  END OF PHASE   MAIN_NEWBAS/JOB_RSMODACU
    >> 2009/12/29 22:07:07  START OF PHASE MAIN_NEWBAS/DBCLEAN_UPG
    >> 2009/12/29 22:07:13  END OF PHASE   MAIN_NEWBAS/DBCLEAN_UPG
    >> 2009/12/29 22:07:13  START OF PHASE MAIN_NEWBAS/EXEC_SMON
    >> 2009/12/29 22:07:16  END OF PHASE   MAIN_NEWBAS/EXEC_SMON
    >> 2009/12/29 22:07:16  START OF PHASE MAIN_NEWBAS/STOPSAP_DUAL
    Stopping system ...
    >> 2009/12/29 22:07:29  END OF PHASE   MAIN_NEWBAS/STOPSAP_DUAL
    >> 2009/12/29 22:07:29  START OF PHASE MAIN_NEWBAS/GETSYNC_MODPROF_STARTED
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    JAVA LOG(Dailog Log)
    Java Enhancement Package Installation
    </font>
    <p>When reporting problems to SAP Support, attach the trouble ticket file <b>D:\EHPI\java\log\TroubleTicket_03.txt</b> to your message.<br>
    </html>.
    Dec 29, 2009 4:22:23 PM [Info]:                                               com.sap.sdt.ucp.dialog.Dialog.process(Dialog.java:264) [Thread[main,5,main]]: Dialog PhaseErrorMessage variable handler has been updated.
    Dec 29, 2009 4:22:23 PM [Info]:                                               com.sap.sdt.ucp.dialog.Dialog.process(Dialog.java:214) [Thread[main,5,main]]: Waiting for input in dialog ActionErrorDialog type Composite.
    Dec 29, 2009 4:22:31 PM [Info]:                                               com.sap.sdt.ucp.dialog.Dialog.process(Dialog.java:233) [Thread[main,5,main]]: Processing input in dialog ActionErrorDialog type Composite.
    Dec 29, 2009 4:22:31 PM [Info]:  com.sap.sdt.util.dialog.ExclusiveSelectionDialog.updateVariables(ExclusiveSelectionDialog.java:339) [Thread[main,5,main]]: In dialog ActionErrorOption the value of variable repeat labeled Repeat phase from point of failure has been set to value of variable true.
    Dec 29, 2009 4:22:31 PM [Info]:  com.sap.sdt.util.dialog.ExclusiveSelectionDialog.updateVariables(ExclusiveSelectionDialog.java:339) [Thread[main,5,main]]: In dialog ActionErrorOption the value of variable ignore labeled Ignore error and go to next phase (requires password) has been set to value of variable false.
    Dec 29, 2009 4:22:31 PM [Info]:  com.sap.sdt.util.dialog.ExclusiveSelectionDialog.updateVariables(ExclusiveSelectionDialog.java:339) [Thread[main,5,main]]: In dialog ActionErrorOption the value of variable jump labeled Jump to another phase (requires password) has been set to value of variable false.
    Dec 29, 2009 4:22:31 PM [Info]:  com.sap.sdt.util.dialog.ExclusiveSelectionDialog.updateVariables(ExclusiveSelectionDialog.java:339) [Thread[main,5,main]]: In dialog ActionErrorOption the value of variable exit labeled Exit program has been set to value of variable false.
    Dec 29, 2009 4:22:31 PM [Info]: com.sap.sdt.util.dialog.NavigationButtonGroupDialog.updateVariables(NavigationButtonGroupDialog.java:342) [Thread[main,5,main]]: In dialog Buttons the value of variable BUTTON labeled #Continue has been set to value of variable Continue.
    Dec 29, 2009 4:22:31 PM [Info]: com.sap.sdt.util.dialog.NavigationButtonGroupDialog.updateVariables(NavigationButtonGroupDialog.java:346) [Thread[main,5,main]]: Dialog Buttons has been confirmed.
    Dec 29, 2009 4:22:31 PM [Info]:                        com.sap.sdt.util.dialog.CompositeDialog.isConfirmed(CompositeDialog.java:281) [Thread[main,5,main]]: Dialog ActionErrorDialog has been confirmed.
    Dec 29, 2009 4:22:31 PM [Info]:                                com.sap.sdt.util.dialog.InfoDialog.updateHandler(InfoDialog.java:116) [Thread[main,5,main]]: Dialog type InfoText with dialog name Info displays dialog text <html>
        An error has occurred during the execution of the <i>DEPLOY_ONLINE_DEPL</i> phase.<br>
        <div style="background-color: #dde8ef"><font face="Helvetica, Arial">
        Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
    Could not execute deployment of stack file D:\HRC_Upgrade_Data\SMSDXML_HRC_20091222112753.484.xml.
    The deployment of the queue failed.
    Deployment of queue sapjup-queue completed with error Cannot stop J2EE instance, SCS instance or OS services.
    Cannot stop OS services, SCS instance and J2EE instance.
    Cannot stop instance HRC 10.
    Could not stop instance 10.
    JSPM version is 7.01.5.1.3. Current JSPM log directory is S:\usr\sap\HRC\DVEBMGS10\j2ee\JSPM\log\log_2009_12_29_14_57_26.
    <br>
        </font></div>
        <p>You may now do one of the following:
        <ul>
          <li><i>Repeat phase from point of failure.</i> After you have corrected the error, you can repeat the phase from the exact point where the error occurred.
          <li><i>Ignore error and go to next phase.</i> You must obtain a password from SAP Support to use this option.
          <li><i>Jump to another phase.</i> You can choose the phase you want to jump to from a list of all phases that belong to the current module. You must obtain a password from SAP Support to use this option. 
          <li><i>Exit program.</i>
        </ul>
        </html>.
    Dec 29, 2009 4:22:31 PM [Info]:                                com.sap.sdt.util.dialog.InfoDialog.updateHandler(InfoDialog.java:116) [Thread[main,5,main]]: Dialog type InfoText with dialog name Info displays dialog text What do you want to do?.
    Dec 29, 2009 4:22:31 PM [Info]: 
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Thanks and Regards
    Vinit

  • Erorr in phase DEPLOY_ONLINE_DEPL

    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

    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

  • DEPLOY_ONLINE_DEPL phase -- Cannot restart cluster HS1 in SAFE mode.

    To ALL:
    During the down time step of implementing EHP4 I receive the following error:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[I:\downloads\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_17.LOG]/>
    <!PATTERN[DEPLOY_ONLINE_DEPL_DDB_17.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Jan 14, 2010 2:36:51 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.
    Jan 14, 2010 2:36:51 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.
    Jan 14, 2010 2:36:51 PM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter action=deploySlot
    Jan 14, 2010 2:36:51 PM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter connect=standard
    Jan 14, 2010 2:36:51 PM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter errorStrategy=skipDepending
    Jan 14, 2010 2:36:51 PM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter rule=all
    Jan 14, 2010 2:36:52 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.
    Jan 14, 2010 2:36:52 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.
    Jan 14, 2010 2:36:52 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:127) [Thread[main,5,main]]: Trying to connect JSPM.
    Jan 14, 2010 2:36:52 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:136) [Thread[main,5,main]]: JSPM is not connected, trying to start it.
    Jan 14, 2010 2:36:53 PM [Info]:                                                com.sap.sdt.util.proc.Process.start(Process.java:164) [Thread[main,5,main]]: I:\downloads\EHPI\jvm\jre\bin\java -ea  -Xmx1024m -cp g:\usr\sap\HS1\DVEBMGS02\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar  Jspm -boot=win  -port=6250 -properties=jspm-srv_config.txt -config=/jspm/sdmRepositorySync=true -startJSPM
    Jan 14, 2010 2:36:56 PM [Info]:                                                     java.lang.Thread.getStackTrace(Thread.java:1501) [Thread[ProcessReader,5,main]]: >> Current log directory is G:\usr\sap\HS1\DVEBMGS02\j2ee\JSPM\log\log_2010_01_14_14_36_55.
    Jan 14, 2010 2:36:58 PM [Info]:     com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.finished(AbstractToolConnector.java:373) [Thread[Process(I:\downloads\EHPI\jvm\jre\bin\java -ea  -Xmx1024m -cp g:\usr\sap\HS1\DVEBMGS02\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar  Jspm),5,main]]: JSPM terminated with exit code 0.
    Jan 14, 2010 2:37:01 PM [Info]:      com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:729) [Thread[main,5,main]]: Connected to host sapes2 on port 6250.
    Jan 14, 2010 2:37:01 PM [Warning]:   com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.discardMsg(AbstractToolConnector.java:775) [Thread[JSPM,5,main]]: Discarding message $com.sap.sdt.sltool.rapi.connector.MsgData@43422d0b
    Jan 14, 2010 2:37:19 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:139) [Thread[main,5,main]]: JSPM was started successfully.
    Jan 14, 2010 2:37:19 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:184) [Thread[main,5,main]]: Trying to log in with user SAP*.
    Jan 14, 2010 2:37:19 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:190) [Thread[main,5,main]]: JSPM detect non deployable components login request property is set to "false".
    Jan 14, 2010 2:38:52 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:199) [Thread[main,5,main]]: JSPM successfully logged in with user SAP*.
    Jan 14, 2010 2:38:52 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:143) [Thread[main,5,main]]: JSPM was connected successfully.
    Jan 14, 2010 2:38:52 PM [Info]:     com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.deploy(SAPJupJSPMRapiAdapter.java:477) [Thread[main,5,main]]: Starting deployment.
    Jan 14, 2010 2:44:58 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.
    Jan 14, 2010 2:44:58 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error Cannot restart cluster in SAFE mode with action NONE.
    Cannot restart cluster HS1 in SAFE mode.
    Shuting down the HS1 cluster failed.
    Could not shut down the whole cluster.
    com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: There was an IOException while sending a command to the cluster instance
    com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: There was an IOException while sending a command to the cluster instance
    JSPM version is 7.01.5.1.3. Current JSPM log directory is G:\usr\sap\HS1\DVEBMGS02\j2ee\JSPM\log\log_2010_01_14_14_36_55.
    Jan 14, 2010 2:44:58 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:695) [Thread[main,5,main]]: The deployment of the queue failed.
    Jan 14, 2010 2:44:58 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file F:\SAP_DOWNLOADS\EHP4\sapnotes\SMSDXML_HS1_20091231185454.628.xml.
    Jan 14, 2010 2:44:58 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
    Jan 14, 2010 2:44:58 PM [Info]:                         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.
    Jan 14, 2010 2:44:58 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/01/14 14:36:51.
    Jan 14, 2010 2:44:58 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/01/14 14:44:58.
    Jan 14, 2010 2:44:58 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:08:07.020.
    Jan 14, 2010 2:44:58 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    The main issue seems to be restarting the cluster in SAFE mode.
    Any help would be greatly appreciated !!
    Thanks,
    Scott

    Hi,
    > Jan 14, 2010 2:44:58 PM [Error]:             >com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment >of queue sapjup-queue completed with error Cannot restart cluster in SAFE mode with action NONE.
    > Cannot restart cluster HS1 in SAFE mode.
    > Shuting down the HS1 cluster failed.
    > Could not shut down the whole cluster.
    > com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: There was an IOException while sending a command to the >cluster instance
    > com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: There was an IOException while sending a command to the >cluster instance
    >
    Have you tried to stop manually and restart it again ?
    Also, read the troubleshooting guide in <upgrade directory>/EHPI/java/htdoc. Similar situation is described there.
    Thanks
    Sunny
    Edited by: Sunny Pahuja on Jan 15, 2010 7:55 AM

  • Enhancement pack installer error at DEPLOY_ONLINE_DEPL phase

    I am having an issue while installing EHP 1 SP 07.
    Here is the text of the error that pops up on the screen:
    An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
    Error while executing DeploymentManager phase with action deploySlot.
    Check the log files for the specified action. Could not execute deployment of stack file D:/EHPI/java/Patches/stack.xml.
    The deployment of the queue failed. Deployment of queue sapjup-queue completed with error JSPM version is 7.01.7.1.3.
    Current JSPM log directory is D:\usr\sap\NPD\JC00\j2ee\JSPM\log\log_2010_12_06_14_57_46.
    sap.com/BI-BASE-S: Deployment of archive D:\EHPI\java\Patches\BIBASES07_0-10005888.SCA has been terminated.
    Aborted: software component 'BI-BASE-S'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612220300''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/BI-IBC: Deployment of archive D:\EHPI\java\Patches\BIIBC07_0-20002782.SCA has been terminated. Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225404''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/BIWEBAPP: Deployment of archive D:\EHPI\java\Patches\BIWEBAPP07_0-20002783.SCA has been terminated. Aborted: software component 'BIWEBAPP'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225533''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/EP-PSERV: Deployment of archive D:\EHPI\java\Patches\EPPSERV07_0-10005915.SCA has been terminated. Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100614135411''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/EPBC2: Deployment of archive D:\EHPI\java\Patches\EPBC207_0-10005895.SCA has been terminated. Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230445''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/KMC-BC: Deployment of archive D:\EHPI\java\Patches\KMCBC07_0-10005912.SCA has been terminated. Aborted: software component 'KMC-BC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230753''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/KMC-CM: Deployment of archive D:\EHPI\java\Patches\KMCCM07_0-10005893.SCA has been terminated. Aborted: software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230851''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/KMC-COLL: Deployment of archive D:\EHPI\java\Patches\KMCCOLL07_0-10005901.SCA has been terminated. Aborted: software component 'KMC-COLL'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230917''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/SWLIFECYCL: Deployment of archive D:\EHPI\java\Patches\SWLIFECYCL07_0-10005910.SCA has been terminated. Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW701P07_C'/'1000.7.01.7.0.20100622150309''/'5': No further description found.
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. sap.com/UWLJWF: Deployment of archive D:\EHPI\java\Patches\UWLJWF07_0-10005903.SCA has been terminated. Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612231021''/'5': Failed deployment of SDAs: development component 'com.sap.netweaver.bc.wf.db'/'sap.com'/'SAP AG'/'7.0107.20100604135629.0000'/'5' : aborted Please, look at error logs above for more information!
    Error during deployment. See D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log for details. The following SAP Note 1399846 may contain solution for the problem.
    You can find more information in the log file D:\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_06.LOG.
    Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager com.sap.sdt.ucp.phases.PhaseException Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. DEPLOY_ONLINE_DEPL DEPLOYMENT_BASED_UPGRADE NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
    When reporting problems to SAP Support, attach the trouble ticket file D:\EHPI\java\log\TroubleTicket_08.txt to your message.
    Any ideas?
    Thank you in advance,
    Neil

    D:/usr/sap/NPD/JC00/SDM/program/log/sdmcl20101206205930.log Errors only
    Dec 6, 2010 3:11:58 PM   Info: E R R O R ******* (DbMssColumn)
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 mss-Error:  compareTo (PROFILE): conversion necessary: original length 127 greater than target length 84
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  KMC_WF_SUBSTITUTE modify column PROFILE from type : VARCHAR,len : 127,dec : 0,not null : true,default : | |
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  KMC_WF_SUBSTITUTE modify column PROFILE from type : VARCHAR,len : 127,dec : 0,not null : true,default : | |
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  KMC_WF_SUBSTITUTE modify column PROFILE to   type : VARCHAR,len : 84,dec : 0,not null : true,default : | |
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  KMC_WF_SUBSTITUTE modify column PROFILE to   type : VARCHAR,len : 84,dec : 0,not null : true,default : | |
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 mss-Info:  table KMC_WF_SUBSTITUTE contains data
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  Action: CONVERT
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  Action: CONVERT
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  Table has to be converted
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Info:  Table has to be converted
    Dec 6, 2010 3:11:58 PM   Info:
    Dec 6, 2010 3:11:58 PM   Info: E R R O R ******* (DbModificationManager)
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Error:  Table KMC_WF_SUBSTITUTE: Conversion currently not possible
    Dec 6, 2010 3:11:58 PM   Info:
    Dec 6, 2010 3:11:58 PM   Info: E R R O R ******* (DbModificationManager)
    Dec 6, 2010 3:11:58 PM   Info: 15:11:56 2010-12-06 dbs-Error:  Table KMC_WF_SUBSTITUTE: Conversion currently not possible
    Dec 6, 2010 3:11:58 PM   Info: 15:11:58 2010-12-06 dbs-Info:  Analysis and adjustment of tables finished with errors
    Dec 6, 2010 3:11:58 PM   Info: 15:11:58 2010-12-06 dbs-Info:  Analysis and adjustment of tables finished with errors
    Dec 6, 2010 3:11:58 PM   Error: Aborted: development component 'com.sap.netweaver.bc.wf.db'/'sap.com'/'SAP AG'/'7.0107.20100604135629.0000'/'5', grouped by software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612231021''/'5':
    No further description found.
    Dec 6, 2010 3:11:58 PM   Info: Starting to save the repository
    Dec 6, 2010 3:11:59 PM   Info: Finished saving the repository for 625 ms.
    Dec 6, 2010 3:11:59 PM   Info: Starting: Update: Selected software component 'BI-BASE-S'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612220300''/'5' updates currently deployed software component 'BI-BASE-S'/'sap.com'/'SAP AG'/'1000.7.00.14.7.20080715114730''/'3'.
    Dec 6, 2010 3:11:59 PM   Error: Aborted: software component 'BI-BASE-S'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612220300''/'5':
    No further description found.
    Dec 6, 2010 3:11:59 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:00 PM   Info: Finished saving the repository for 640 ms.
    Dec 6, 2010 3:12:00 PM   Info: Starting: Update: Selected software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225404''/'5' updates currently deployed software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118035805''/'0'.
    Dec 6, 2010 3:12:00 PM   Error: Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225404''/'5':
    No further description found.
    Dec 6, 2010 3:12:00 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:00 PM   Info: Finished saving the repository for 688 ms.
    Dec 6, 2010 3:12:00 PM   Info: Starting: Initial deployment: Selected software component 'BIWEBAPP'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225533''/'5' will be deployed.
    Dec 6, 2010 3:12:00 PM   Error: Aborted: software component 'BIWEBAPP'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612225533''/'5':
    No further description found.
    Dec 6, 2010 3:12:00 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:01 PM   Info: Finished saving the repository for 656 ms.
    Dec 6, 2010 3:12:01 PM   Info: Starting: Update: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100614135411''/'5' updates currently deployed software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.2.20080424063333''/'3'.
    Dec 6, 2010 3:12:01 PM   Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100614135411''/'5':
    No further description found.
    Dec 6, 2010 3:12:01 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:02 PM   Info: Finished saving the repository for 1140 ms.
    Dec 6, 2010 3:12:02 PM   Info: Starting: Update: Selected software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230445''/'5' updates currently deployed software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.4.20080527102951''/'2'.
    Dec 6, 2010 3:12:02 PM   Error: Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230445''/'5':
    No further description found.
    Dec 6, 2010 3:12:02 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:03 PM   Info: Finished saving the repository for 750 ms.
    Dec 6, 2010 3:12:03 PM   Info: Starting: Update: Selected software component 'KMC-BC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230753''/'5' updates currently deployed software component 'KMC-BC'/'sap.com'/'SAP AG'/'1000.7.00.14.3.20080428150051''/'2'.
    Dec 6, 2010 3:12:03 PM   Error: Aborted: software component 'KMC-BC'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230753''/'5':
    No further description found.
    Dec 6, 2010 3:12:03 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:04 PM   Info: Finished saving the repository for 672 ms.
    Dec 6, 2010 3:12:04 PM   Info: Starting: Update: Selected software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230851''/'5' updates currently deployed software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.00.14.4.20080617151136''/'2'.
    Dec 6, 2010 3:12:04 PM   Error: Aborted: software component 'KMC-CM'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230851''/'5':
    No further description found.
    Dec 6, 2010 3:12:04 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:04 PM   Info: Finished saving the repository for 719 ms.
    Dec 6, 2010 3:12:04 PM   Info: Starting: Update: Selected software component 'KMC-COLL'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230917''/'5' updates currently deployed software component 'KMC-COLL'/'sap.com'/'SAP AG'/'1000.7.00.14.4.20080704101734''/'2'.
    Dec 6, 2010 3:12:04 PM   Error: Aborted: software component 'KMC-COLL'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612230917''/'5':
    No further description found.
    Dec 6, 2010 3:12:04 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:06 PM   Info: Finished saving the repository for 1171 ms.
    Dec 6, 2010 3:12:06 PM   Info: Starting: Initial deployment: Selected software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW701P07_C'/'1000.7.01.7.0.20100622150309''/'5' will be deployed.
    Dec 6, 2010 3:12:06 PM   Error: Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW701P07_C'/'1000.7.01.7.0.20100622150309''/'5':
    No further description found.
    Dec 6, 2010 3:12:06 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:06 PM   Info: Finished saving the repository for 735 ms.
    Dec 6, 2010 3:12:06 PM   Info: Starting: Update: Selected software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612231021''/'5' updates currently deployed software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.12.0.20070509052701''/'2'.
    Dec 6, 2010 3:12:06 PM   Error: Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.01.7.0.20100612231021''/'5':
    Failed deployment of SDAs:
    development component 'com.sap.netweaver.bc.wf.db'/'sap.com'/'SAP AG'/'7.0107.20100604135629.0000'/'5' : aborted
    Please, look at error logs above for more information!
    Dec 6, 2010 3:12:06 PM   Info: Starting to save the repository
    Dec 6, 2010 3:12:07 PM   Info: Finished saving the repository for 562 ms.
    Dec 6, 2010 3:12:07 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Dec 6, 2010 3:12:07 PM   Error: -
    At least one of the Deployments failed -

  • EHPI installer: Error while reading a dynpro. Stuck at Start Shadow First.

    Hi Everyone,
    I am dead in the water with my test install of EhP5 using the most current installer.  This small test is on an older iseries, V5R4 with 8G memory. The SAP version is ECC 6.0 at sp Basis  23 and Applications at 19.
    The install stops at Start Shadow First, but the instance and work processes are up on the server.   The log- SAPehpiConsole reads:
    Severe error(s) occured in phase MAIN_SHADOW/START_SHDI_FIRST!
    Last error code set: RFC call to upg_is_shadow_system failed with key
    RFC_ERROR_SYSTEM_FAILURE (open): Error while reading a dynpro
    Please refer to these logs in the posted replys following this post for readability.
    The shadow system work process wp01 log showsan RFC error as follows:
    Wed Sep 14 11:29:58 2011
    ABAP Program SAPMSSY2                                .
    Source                                          Line 0.
    Error Code DYNPRO_READ_FAILED.
    Module  $Id: //bas/720_REL/src/krn/dynp/dyrdypdb.c#3 $ SAP.
    Function dy_dbread Line 100.
    RABAX: level LEV_RX_STDERR completed.
    RABAX: level LEV_RX_RFC_ERROR entered.
    RABAX: level LEV_RX_RFC_ERROR completed.
    RABAX: level LEV_RX_RFC_CLOSE entered.
    RABAX: level LEV_RX_RFC_CLOSE completed.
    RABAX: level LEV_RX_ERROR_SAVE entered.
    RABAX: level LEV_RX_ERROR_SAVE completed.
    RABAX: level LEV_RX_ERROR_TPDA entered.
    RABAX: level LEV_RX_ERROR_TPDA completed.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    RABAX: level LEV_RX_END entered.
    RABAX: level LEV_RX_END completed.
    RABAX: end no http/smtp
    RABAX: end RX_BTCHLOG RX_VBLOG
    Error while reading a dynpro.
    C Wed Sep 14 11:33:59 2011
    C  *** ERROR => SQL-Error -204 in function db_open  (dbsldb4.cpp  10630)
    C  {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=}_0
    RABAX: level LEV_RX_IMC_ERROR entered.
    RABAX: level LEV_RX_IMC_ERROR completed.
    RABAX: level LEV_RX_DATASET_CLOSE entered.
    RABAX: level LEV_RX_DATASET_CLOSE completed.
    C  Reopen: FALSE
    B  *** ERROR => dbdynpdb2: dbdd_dbtab_columns (DYNPSOURCE) failed with rc = 4
    dbdynpdb2.c  2506]
    B  {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BZY=> unexpected return code 4          calling dbdd_dbtab [dbdynpdb     2508]
    So I have a problem communicating with the shadow. Or is it a problem with the db_open?
    From the test system I have an entry in SM59 to the shadow and I get this error when trying a connection test.
    Error Details     Error while reading a dynpro.
    And trying to logon to the client sends the same message, it does not bring up the login screen.
    OK. So in the 3 weeks that I have restarted, re-set and completely restored and restarted the install, I have always come to this point. I have search for similar issues and have done a review of pertinent notes etcu2026    Just as a comment, last year I successfully did the Ehp 4 upgrade without many problems on this same system using last years SAP system.   In the month that I have been trying to do this,  SAP has replaced the EHPI installer 3 times which indicates some problems on their part.
    Any comments or suggestions would be greatly appreciated.
    Pat

    The 2 logs from the installer are here.
    The STARTSFI is as follows:
    1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20110913144811")
    4 ETQ399 Set environment for standard connect:
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '14', GwService = 'sapgw14'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_db4_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    1 ETQ206 Executing pre-phase DB specific actions.
    3 ETQ399 Fixing IFS authorities for '/usr/sap/TEH/EHPI/abap/exe'
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
    4 ETQ399 Set environment for shadow connect:
    4 ETQ399 Set RFC variables for shadow connect:
    4 ETQ399 System-nr = '15', GwService = 'sapgw15'
    4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
    4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    4 ETQ399 Set tool parameters for shadow connect:
    4 ETQ399   default TPPARAM: SHADOW.TPP
    4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
    4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWI
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Starting shadow instance
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    2 ETQ231 RFC Login failed
    repeats the rfc call with a fail until this final entry.
    2EETQ399 Starting shadow instance failed
    2EETQ399 Test RFC failed finally
      The DEVTRACE.LOG is here:
    $                               Directory:    /usr/sap/TEH/EHPI/abap/log
    Name:         DEVTRACE.LOG
    trc file: "dev_disp.new", trc level: 1, release: "720"
    sysno      15
    sid        TEH
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    100
    intno      20020600
    make       single threaded, ASCII, 64 bit, optimized
    profile    /usr/sap/TEH/EHPI/abap/TEH/SYS/profile/TEH_DVEBMGS15_omni
    pid        75851
    kernel runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)
    length of sys_adm_ext is 376 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (15 75851) [dpxxdisp.c   1287]
    #shared lib "dw_xml.so" version 100 successfully loaded
    #shared lib "dw_xtc.so" version 100 successfully loaded
    #shared lib "dw_stl.so" version 100 successfully loaded
    #shared lib "dw_gui.so" version 100 successfully loaded
    #shared lib "dw_mdm.so" version 100 successfully loaded
    #shared lib "dw_rndrt.so" version 100 successfully loaded
    #shared lib "dw_abp.so" version 100 successfully loaded
    #shared lib "dw_sym.so" version 100 successfully loaded
    #shared lib "dw_aci.so" version 100 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    rdisp/dynamic_wp_check : 0
    rdisp/calculateLoadAverage : 1
    Tue Sep 13 14:48:58 2011
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6404]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >omni_TEH_15                             <
    DpShMCreate: sizeof(wp_adm)##17440#(1744)
    DpShMCreate: sizeof(tm_adm)##4976768#(24760)
    DpShMCreate: sizeof(wp_ca_adm)##56000#(56)
    DpShMCreate: sizeof(appc_ca_adm)#56000#(56)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064
    DpShMCreate: sizeof(comm_adm)##576064#(1136)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)##0#(104)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)##0#(80)
    DpShMCreate: sizeof(vmc_adm)##0#(1856)
    DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)
    DpShMCreate: sizeof(gw_adm)#48
    DpShMCreate: sizeof(j2ee_adm)#2032
    DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000050000000, size: 5759216)
    DpShMCreate: allocated sys_adm at 700000050000010
    DpShMCreate: allocated wp_adm_list at 700000050002970
    DpShMCreate: allocated wp_adm at 700000050002b60
    DpShMCreate: allocated tm_adm_list at 700000050006f90
    DpShMCreate: allocated tm_adm at 700000050006fe0
    DpShMCreate: allocated wp_ca_adm at 7000000504c6070
    DpShMCreate: allocated appc_ca_adm at 7000000504d3b40       
    Directory:    /usr/sap/TEH/EHPI/abap/log
    Name:         DEVTRACE.LOG
    DpShMCreate: allocated comm_adm at 7000000504e1610
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 70000005056e060
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 70000005056e110
    DpShMCreate: allocated j2ee_adm at 70000005056e150
    DpShMCreate: allocated ca_info at 70000005056e950
    DpShMCreate: allocated wall_adm at 70000005056e9d0
    DpCommAttachTable: attached comm table (header=7000000504e1610/ft=7000000504e1620)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (3 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation std
    EsStdUnamFileMapInit: ES base = 0x7000000a0000000
    EsStdInit: Extended Memory 4096 MB allocated
    <ES> 1023 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 96 MB
    DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    Tue Sep 13 14:48:59 2011
    WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13097]
    Tue Sep 13 14:49:02 2011
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0K=> DpMsAttach, mscon ( omni) [dpxxdisp.c   12339]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >omni_TEH_15                             <)
    DpStartStopMsg: start msg sent
    Tue Sep 13 14:49:11 2011
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
    CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Tue Sep 13 14:49:13 2011
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
    MBUF state ACTIVE
    DpWpBlksLow: max wp blocks in queue is 800 (80 %)
    MBUF component UP
    DpMsgProcess: 1 server in MBUF
    DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
    Tue Sep 13 14:50:24 2011
    DpModState: change server state from STARTING to ACTIVE
    trc file: "dev_ms.new", trc level: 1, release: "720"
    [Thr 01] Tue Sep 13 14:48:39 2011
    [Thr 01] MsSOsPrivInit: Run priority adjusted to 12
    [Thr 01] ms/http_max_clients = 500 -> 500
    [Thr 01] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    92
    intno      20020600
    make       multithreaded, ASCII, 64 bit, optimized
    pid        75850
    [Thr 01] Tue Sep 13 14:48:40 2011
    [Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 75850) [msxxserv_mt. 2274]
    [Thr 01] SigISetDefaultAction : default handling for signal SIGCHLD
    [Thr 01] load acl file = /usr/sap/TEH/EHPI/abap/TEH/SYS/global/ms_acl_info
    [Thr 01] MsGetOwnIpAddr: my host addresses are :
    [Thr 01]   1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)
    [Thr 01]   2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    [Thr 01] MsHttpInit: full qualified hostname = omni.plastekgroup.com
    [Thr 01] HTTP logging is switch off
    [Thr 01] MsHttpOwnDomain: own domain[1] = plastekgroup.com
    [Thr 01] *** I listen to port 3615 (3615) ***
    [Thr 01] CUSTOMER KEY: >H1357713078<
    [Thr 01] build version=720.2011.05.04
    trc file: "dev_rd", trc level: 1, release: "720"
    Tue Sep 13 14:49:07 2011
    ***LOG S00=> GwInitReader, gateway started ( 75855) [gwxxrd.c     1758]
    systemid   327 (IBM i with OS400)
    relno      7200
    patchlevel 0
    patchno    96
    intno      20020600
    make       single threaded, ASCII, 64 bit, optimized
    pid        75855
    gateway runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)
    gateway (version=720.2011.04.20)
    Tue Sep 13 14:49:10 2011
    gw/reg_no_conn_info = 1
    gw/local_addr : 0.0.0.0
    gw/reg_no_conn_info = 1
    SWITCH TRC-RESOLUTION from 1 TO 1
    CCMS: initialize CCMS Monitoring for ABAP instance with J2EE addin.
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Tue Sep 13 14:49:13 2011
    CCMS: Initalized shared memory of size 40000000 for monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1002.
    CCMS: AlMsUpload successful for /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/log/ALMTTREE (0 MTEs).
    Bind service sapgw15 (socket) to port 3315
    GwIRegInitRegInfo: reg_info file /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/data/reginfo not found
    GwPrintMyHostAddr: my host addresses are :
      1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)
      2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    Full qualified hostname = omni.plastekgroup.com
    DpSysAdmExtCreate: ABAP is active
    DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    DpIPCInit2: read dp-profile-values from sys_adm_ext
    DpShMCreate: sizeof(wp_adm)##17440#(1744)
    DpShMCreate: sizeof(tm_adm)##4976768#(24760)
    DpShMCreate: sizeof(wp_ca_adm)##56000#(56)
    DpShMCreate: sizeof(appc_ca_adm)#56000#(56)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064
    DpShMCreate: sizeof(comm_adm)##576064#(1136)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)##0#(104)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)##0#(80)
    DpShMCreate: sizeof(vmc_adm)##0#(1856)
    DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)
    DpShMCreate: sizeof(gw_adm)#48
    DpShMCreate: sizeof(j2ee_adm)#2032
    DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000060000000, size: 5759216)
    DpShMCreate: allocated sys_adm at 700000060000010
    DpShMCreate: allocated wp_adm_list at 700000060002970
    DpShMCreate: allocated wp_adm at 700000060002b60
    DpShMCreate: allocated tm_adm_list at 700000060006f90
    DpShMCreate: allocated tm_adm at 700000060006fe0
    DpShMCreate: allocated appc_ca_adm at 7000000604d3b40
    DpShMCreate: allocated comm_adm at 7000000604e1610
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 70000006056e060
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 70000006056e110
    DpShMCreate: allocated j2ee_adm at 70000006056e150
    DpShMCreate: allocated ca_info at 70000006056e950
    DpCommAttachTable: attached comm table (header=7000000604e1
    MtxInit: -2 0 0
    DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 fro
    Tue Sep 13 14:50:14 2011
    GwDpInit: attached to gw_adm at 70000006056e110
    Tue Sep 13 14:50:16 2011
    DpSetProcessPriority: Run priority for gwrd adjusted to 12

  • Ehp5 Implementation - System fails to start at MAIN_NEWBAS/STARTSAP_NBAS

    Hello,
    I'm running an Ehp5 implementation from ERP 6.0. Ehpi is stuck in step Downtime during phase MAIN_NEWBAS/STARTSAP_NBAS with the following error:
    Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
    Connect_PM GWHOST=sapapt01, GWSERV=sapgw00, SYSNR=00 
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR partner '10.10.1.21:3300' not reached
    TIME Mon Jan 16 23:03:11 2012
    RELEASE 720
    COMPONENT NI (network interface)
    VERSION 40 RC -10
    MODULE nixxi.cpp LINE 3286
    DETAIL NiPConnect2: 10.10.1.21:3300
    SYSTEM CALL connect
    ERRNO 111
    ERRNO TEXT Connection refused
    COUNTER 226 
    System start failed
    I checked the system instance and it was down. When I try to start up it manually with startsap, I do not get any error:
    sapapt01:ippadm 16> startsap
    Checking IPP Database
    Database is running
    Starting Startup Agent sapstartsrv
    OK
    Instance Service on host sapapt01 started
    starting SAP Instance DVEBMGS00
    Startup-Log is written to /home/ippadm/startsap_DVEBMGS00.log
    /usr/sap/IPP/SYS/exe/run/sapcontrol -prot NI_HTTP -nr 00 -function Start
    Instance on host sapapt01 started.
    The problem is that no work process is started nor dispatcher or message server. When I look at the instance work directory I see that the only files that are written are the following:
    available.log
    sapstartsrv.log
    logsave.bin
    dev_tp (but it's empty)
    The content of sapstartsrv.log is the following:
    trc file: "sapstartsrv.log", trc level: 0, release: "720"
    pid        29149
    [Thr 47879647924784] Tue Jan 17 00:51:54 2012
    No halib defined => HA support disabled
    CCMS agent initialization: return code 0.
    CCMS agent start: return code 0.
    Initializing SAPControl Webservice
    Starting AutoRestart thread
    SapSSLInit failed => https support disabled
    [Thr 1079777600] Tue Jan 17 00:51:56 2012
    AutoRestart thread started
    Starting WebService thread
    Webservice thread started, listening on port 50013
    Trusted http connect via Unix domain socket '/tmp/.sapstream50013' enabled.
    trusted unix domain socket user is starting SAP System at 2012/01/17  0:52:04
    The startsap_DVEBMGS00.log at the sidadm home directory shows the following:
    Trace of system startup/check of SAP System IPP on Tue Jan 17 00:51:54 ART 2012
    Called command: startsap start
    00:51:54
    Starting Startup Agent sapstartsrv
    00:52:04
    Instance Service on host sapapt01 started
    00:52:04
    starting SAP Instance DVEBMGS00
    00:52:04
    Startup-Log is written to /home/ippadm/startsap_DVEBMGS00.log
    00:52:04
    /usr/sap/IPP/SYS/exe/run/sapcontrol -prot NI_HTTP -nr 00 -function Start
    17.01.2012 00:52:05
    Start
    OK
    00:52:15
    Instance on host sapapt01 started
    The /var/log/messages content is the following:
    Jan 17 00:51:56 sapapt01 SAPIPP_00[29149]: SAP Service SAPIPP_00 successfully started.
    I can't find any clue why the system processes are not starting. The phase is the next after kernel upgrade from 700 to 720, so I believe it is related to the switch and maybe my kernel is not correctly updated or something is missing.
    Please let me know any suggestion to know why the system is not starting.
    Regards,
    Alejandro

    Hi,
    No object was removed with the cleanipc command, anyway I've rebooted the server and then started db and sap again. Now the dev traces are written.
    Output of the cleanipc command:
    sapapt01:ippadm 42> ./cleanipc 00
    Show/Cleanup SAP-IPC-Objects V2.3, 94/01/20
    ===========================================
    +----+
    | To inhibit destruction of valid SAP-IPC-Objects |
    | during shutdown, this program requires now      |
    | special options for removing IPC-Objects.       |
    +----+
    Running SAP-Systems (Nr)...:
    ---- Show IPC-Objects of Sap-System  0 -
    Number of IPC-Objects...........:    0
    Summary of all Shared Memory....:     8802.0 MB (may be incomplete when not in superuser mode)
    Number of SAP_ES files found:.............:    0
    Number of SAP_ES files removed:...........:    0
    dev_w0 trace file:
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      00
    M sid        IPP
    M systemid   390 (AMD/Intel x86_64 with Linux)
    M relno      7000
    M patchlevel 0
    M patchno    185
    M intno      20050900
    M make:      single threaded, Unicode, 64 bit, optimized
    M pid        29183
    M
    M
    M Tue Jan 17 03:23:58 2012
    M  kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000
    -UC)
    M  length of sys_adm_ext is 576 bytes
    M  ***LOG Q01=> ThInit, WPStart (Workproc 0 1 29183) [thxxhead.c   1290]
    M  ThInit: running on host sapapt01
    M  calling db_connect ...
    B  create_con (con_name=R/3)
    B  Loading DB library '/usr/sap/IPP/SYS/exe/run/dboraslib.so' ...
    B  Library '/usr/sap/IPP/SYS/exe/run/dboraslib.so' loaded
    *B  *** ERROR => Version mismatch between kernel (700.08) and DBSL shared library*
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) [thxxhead.c   1449]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thx
    xhead.c   10524]
    M
    M  Info for wp 0
    M
    M    pid = 29183
    M    severity = 0
    M    status = 0
    M    stat = WP_RUN
    M    waiting_for = NO_WAITING
    M    reqtype = DP_RQ_DIAWP
    M    act_reqtype = NO_REQTYPE
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source =
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M    mode_cleaned_counter = 0
    The kernel version seems to be 700 here, I don't know why because when I check the disp+work -version  is 720.
    Regards,
    AN

  • Upgrade to ERP EhP5 fails in phase RUN_GENPUTTBSHD

    Hi
    We are updating en ERP 604 to 605.
    Phase RUN_GENPUTTBSHD fails during schedule of a batch job.
    A dump is generated with this text:
    Runtime Errors         GEN_PROGRAM_NOT_EXISTS
    Short text:      Program "PUTTB_SHD" does not exist.
    The program could be running from the shadow instance, but from what I can see a shadow instance has not yet been created yet.
    Output from logfiles has been inserted below.
    Anyone facing this kind of error? I have seen at least one similar issue but no solution provided.
    Thanks
    Brgds Tom
    SAPEHPICONSOLE.LOG:
    >> 2011/06/08 11:58:59  START OF PHASE PREP_IMPORT/SUBMOD_TOOLIMPORT_POST/RUN_GENPUTTBSHD
    Starting of PUTTB_SHD generation in batch (job RS_GENERATE_PUTTB_SHD)
    RSPTBINI.LOG:
    1 ETQ201 Entering upgrade-phase "RUN_GENPUTTBSHD" ("20110608115859")
    4 ETQ399 Set environment for standard connect:
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_mss_schema=ed1
    4 ETQ399   auth_shadow_upgrade=0
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'PREP_IMPORT/RUN_GENPUTTBSHD'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'RS_GENERATE_PUTTB_SHD'
    2 ETQ399 Arg[1] = 'SAP_TMPLOG'
    2 ETQ399 Arg[2] = 'NO-IGNORE'
    2 ETQ399 Arg[3] = 'RS_GENERATE_PUTTB_SHD\.$(SAPSID)'
    2 ETQ399 Arg[4] = '5'
    2 ETQ399 Arg[5] = 'PUTTB_SHD generation'
    2 ETQ399 Arg[6] = 'RSPTBINI.ELG'
    4 ETQ010 Date & Time: 20110608115859 
    4 ETQ265 Starting report "RS_GENERATE_PUTTB_SHD" with variant "SAP_TMPLOG" in batch
    4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
    2WETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
    2WETQ361 code/exception  : BATCH_SCHEDULING_FAILED
    4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    2EETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
    2EETQ361 code/exception  : BATCH_SCHEDULING_FAILED
    2EETQ362 key             : BATCH_SCHEDULING_FAILED
    2EETQ364 message         :
    2EETQ399 EXCEPTION BATCH_SCHEDULING_FAILED RAISED
    4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    2EETG894 Exception "BATCH_SCHEDULING_FAILED" raised, write variant failed with error code -1
    2EETG890 Exception "BATCH_SCHEDULING_FAILED" raised, job scheduling failed with error code -1
    2EETQ261 Start of batchjob "RS_GENERATE_PUTTB_SHD" failed
    1 ETQ207 Executing post-phase DB specific actions.
    4 ETQ010 Date & Time: 20110608120854 
    BATCHCHK_IMP.LOG:
    1 ETQ201 Entering upgrade-phase "BATCHCHK_IMP" ("20110608084941")
    4 ETQ399 Set environment for standard connect:
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_mss_schema=ed1
    4 ETQ399   auth_shadow_upgrade=0
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'PREP_IMPORT/BATCHCHK_IMP'.
    4 ETQ260 Starting batchjob "RDDIT008"
    4 ETQ010 Date & Time: 20110608084941 
    4 ETQ260 Starting batchjob "RDDIT008"
    4 ETQ230 Starting RFC Login to: System = "ED1", GwHost = "bas01", GwService = "sapgw00"
    4 ETQ359 RFC Login to: System="ED1", Nr="00", GwHost="bas01", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    4 ETQ399 JOBNAME='RDDIT008', REPNAME='RDDIT008', VARNAME='', BATCHHOST='bas01', IV_SCHEDEVER=' '
    4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
    4 ETQ399 Returned JOBCOUNT='08494100'
    4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
    4 ETQ010 Date & Time: 20110608084946 
    4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
    4 ETQ239 Logging off from SAP system
    4 ETQ263 Batchjob "RDDIT008" finished successfully
    1 ETQ207 Executing post-phase DB specific actions.
    4 ETQ010 Date & Time: 20110608084946 
    SAPEHPICHK.LOG:
    CURRENTPHASE PREP_IMPORT/SUBMOD_TOOLIMPORT_POST/RUN_GENPUTTBSHD
    ...started at 20110608103533
    Using phase log file 'RSPTBINI.LOG'.
    ...begin dialogue at 20110608103534
    ...end dialogue at 20110608103537
    ..finished at 20110608103537 with status CALLING PUTTB_SHD generation FAILED.
    Error message set: 'RFC call to SUBST_START_REPORT_IN_BATCH failed with key BATCH_SCHEDULING_FAILED (BATCH_SCHEDULING_FAILED): EXCEPTION BATCH_SCHEDULING_FAILED RAISED'
    ...begin dialogue at 20110608103538

    Hi
    SAP got back with this info:
    This error is caused due to the report RS_GENERATE_PUTTB_SHD being deleted druing the upgrade.
    This is a recently discovered problem with the SAPehpi patch 81.
    and the issue is fixed with the lateset version of SAPehpi.
    It will import the report RS_GENERATE_PUTTB_SHD during TOOLIMPORT.
    To use this version, you have to reset the current EHPI run and start from scratch with the new version
    New version (83) downloaded, reset prepare and the phase was now completed
    Thanks,
    Tom

  • Error in START_SHDI_FIRST... RFC logon fails

    Hello All,
    I cannot get past a step in the enhancement package 4  installation.  The step is called:  START_SHDI_FIRST. The error says to troubleshoot by looking at 2 logs,  STARTSFI.LOG  and DEVTRACE.log.   extracted below.
    The problem can be described this way. The step begins as the installer tries to start the shadow system.   The first attempt stopped and I could see that the shadow was not started.  I used the information in note 525677 to manually start the shadow and could verify that it was starting. 
    The screen says to retry until I can logon to the shadow.   I am able to logon as user SAP* with password pass in client 000.   I am not able to logon as myself and receive the message: Logon not possible (error in license check). 
    As SAP* I use the transaction SLICENSE, and could see that the maintenance certificate had expired. I loaded that certificate without an error.
    I also see that the hardware key information is missing.  SAP* is not allowed to update that information.
    I believe that no other user will be able to logon as long as the license is an issue.   The installer is trying to do a remote logon to verify that the system is up (my interpretation) .
    I also see this information in the shadow system dev_W1 log.
    M  *** ERROR => ThMsGetHardwareId: ThOpcodeToMsg failed (1) [thxxmsg.c    3095]                                                                
    M  ***LOG Q16=> ThGetMsHwId, DpMBufHwIdGet (HWID_PENDING) [thxxmbuf.c   511]                                                                   
    M  *** ERROR => SlicLikeyGetHardwareKey: no hwid from MSG server: -1 [sliclikey.c  1301]                                                       
    M  *** ERROR => likey_get_validity_dates: Error getting the hardware key. You might find some information in file "dev_ms" on the message server
    M                                                                               
    M Thu Jul 29 15:18:28 2010                                                                               
    M  *** ERROR => ThCheckReqInfo: message send/receive failed [thxxhead.c   17580]                                                               
    M                                                                               
    M  Modeinfo for User T8/M1                                                                               
    So, am I correct in seeing that the missing hardware key is the problem in the shadow system?   Any ideas would be appreciated,  otherwise I will clear the systems out and start over.  Thanks.
    Pat.
    Below is the DEVTRACE   (extract)
    Directory:  /usr/sap/TEH/EHPI/abap/log
    Name:       DEVTRACE.LOG
    trc file: "dev_disp.new", trc level: 1, release: "701"
    sysno      15
    sid        TEH
    systemid   324 (IBM iSeries with OS400)
    relno      7010
    patchlevel 0
    patchno    69
    intno      20020600
    make:      single threaded, ASCII, 64 bit, optimized
    pid        103802
    Thu Jul 29 14:54:58 2010
    kernel runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
    length of sys_adm_ext is 364 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (15 103802) [dpxxdisp.c   1287]
         shared lib "dw_xml.so" version 69 successfully loaded
         shared lib "dw_xtc.so" version 69 successfully loaded
         shared lib "dw_stl.so" version 69 successfully loaded
         shared lib "dw_gui.so" version 69 successfully loaded
         shared lib "dw_mdm.so" version 69 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3615
    MtxInit: 30000 0 0
    Thu Jul 29 14:54:59 2010
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    rdisp/queue_size_check_value :  -> off
    ThTaskStatus: rdisp/reset_online_during_debug 0
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation std
    <ES> Info: use normal pages (no huge table support available)
    EsStdUnamFileMapInit: ES base = 0x7000000b0000000
    EsStdInit: Extended Memory 4096 MB allocated
    <ES> 1023 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 96 MB
    Thu Jul 29 14:55:00 2010
    WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13279]
    DpSetProcessPriority: Run priority for work process startup adjusted to 20
    DpSetProcessPriority: Run priority for work process startup adjusted to 20
    Thu Jul 29 14:55:01 2010
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
    ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 9
        (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
    ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
    ***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1816]
    Thu Jul 29 14:55:19 2010
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Thu Jul 29 14:55:53 2010
    ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
    ERROR => NiPConnect: SiConnect failed for hdl 3 / sock 10
        (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
    ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
    Thu Jul 29 14:56:34 2010
    ERROR => MsISnd2: not_attached [msxxi.c      1321]
    ***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5007]
    trc file: "dev_ms", trc level: 1, release: "701"
    [Thr 01] Thu Jul 29 14:54:56 2010
    [Thr 01] MsSOsPrivInit: Run priority adjusted to 12
    [Thr 01] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
    systemid   324 (IBM iSeries with OS400)
    relno      7010
    patchlevel 0
    patchno    63
    intno      20020600
    make:      multithreaded, ASCII, 64 bit, optimized
    pid        103801
    [Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 103801) [msxxserv_mt. 1853]
    [Thr 01] Thu Jul 29 14:54:57 2010
    [Thr 01] SigISetDefaultAction : default handling for signal 20
    [Thr 01] ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3239]
    [Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1 / sock 7
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:3615) [nixxi.cpp    3239]
    [Thr 01] *** ERROR => MsSCommInit: NiBufListen(3615) (rc=NIESERV_USED) [msxxserv_mt. 10222]
    [Thr 01] *** ERROR => MsSInit: MsSCommInit (internal) [msxxserv_mt. 1903]
    [Thr 01] *** ERROR => main: MsSInit [msxxserv_mt. 5983]
    [Thr 01] ***LOG Q02=> MsSHalt, MSStop (Msg Server 103801) [msxxserv_mt. 6030]
    trc file: "dev_rd", trc level: 1, release: "701"
    Thu Jul 29 14:55:00 2010
    Shared memory semaphore administration area size = 10608
    Thu Jul 29 14:55:06 2010
    ***LOG S00=> GwInitReader, gateway started ( 103807) [gwxxrd.c     1758]
    systemid   324 (IBM iSeries with OS400)
    relno      7010
    patchlevel 0
    patchno    68
    intno      20020600
    make:      single threaded, ASCII, 64 bit, optimized
    pid        103807
    gateway runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
    gateway (version=701.2009.09.28)
    gw/local_addr : 0.0.0.0
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
    Thu Jul 29 14:55:09 2010
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    Bind service sapgw15 (socket) to port 3315
    GwPrintMyHostAddr: my host addresses are :
      1 : [10.127.0.100] omni (HOSTNAME)
      2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    Full qualified hostname = omni.plastekgroup.com
    DpSysAdmExtCreate: ABAP is active
    DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    MtxInit: -2 0 0
    Thu Jul 29 14:55:47 2010
    GwDpInit: attached to gw_adm at 700000080599e90
    Thu Jul 29 14:55:48 2010
    DpSetProcessPriority: Run priority for gwrd adjusted to 12
    AN EXTRACT OF STARTSFI_LOG
    Directory:  /usr/sap/TEH/EHPI/abap/log
    Name:       STARTSFI.LOG
    1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20100729145436")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '14', GwService = 'sapgw14'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_db4_schema=<null>
    4 ETQ399   auth_shadow_upgrade=<null>
    4 ETQ399 Set environment for standard connect:
    4 ETQ399 ENV: dbs_db4_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=0
    4 ETQ399 Set RFC variables for standard connect:
    4 ETQ399 System-nr = '14', GwService = 'sapgw14'
    4 ETQ399 Set tool parameters for standard connect:
    4 ETQ399   default TPPARAM: DEFAULT.TPP
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
    4 ETQ399 Set environment for shadow connect:
    4 ETQ399 ENV: dbs_db4_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=1
    4 ETQ399 Set RFC variables for shadow connect:
    4 ETQ399 System-nr = '15', GwService = 'sapgw15'
    4 ETQ399 Set tool parameters for shadow connect:
    4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
    4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    4 ETQ399   default TPPARAM: SHADOW.TPP
    4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
    4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
    4 ETQ383 translates to path "exe"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Starting shadow instance
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2 ETQ399 Stopping shadow instance
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    2 ETQ231 RFC Login failed
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    2 ETQ231 RFC Login failed
    2 ETQ353 Starting system
    3 ETQ399 Executing command: 'startsap  SID(TEH) INSTANCE(15) PROFILE('/usr/sap/TEH/EHPI/abap/TEH/SYS/profile/START_DVEBMGS15_omni')'.
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2 ETQ370 starting test RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
    4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
    4 ETQ239 Logging off from SAP system
    2WETQ372 test RFC failed, rc="-1"
    2EETQ399 Starting shadow instance failed
    2EETQ399 Test RFC failed finally

    Hi,
    You are getting this error because your hardware key in the license installed in slicense is wrong. Since upgrade tries to login with ddic user and if there is problem with license then only SAP* user is allowed.
    Please perform below steps to resolve the problem. Check at OS level what is the hardware key, if the hardware key that is present in slicense is different then generate a permanent license of that hardware key and apply it in shadow instance. After that check whether you are able to login with user other than SAP*, if yes, then repeat the phase.
    Please perform above steps and let us know the result.
    Thanks
    Sunny

Maybe you are looking for

  • What are the main uses for a Macbook Pro, and also for a Macbook Air?

    I'm curious of whether I should buy a Macbook Pro, or Macbook Air. Before I make my decision I would like to know what are the main purpaces for each Macbook.

  • New Windows Setup Can Be Synced To Only the Last Used Windows Installation?

    Hello, I have found out that Windows allows you to synchronize only with the last used Windows installation and does not allow you to choose to which of your Windows installations you want to synchronize. Why is that? Here's my experience. 1. I insta

  • Mac OS X v10.5: Fonts not displaying correctly

    i'm not sure if this is a leopard problem or something else all together in the last couple of weeks i have had strange symbols popping up within certain programs. for example on some web pages, these include wikipedia and one of news pages which com

  • Screen sharing error

    I want my MacBook Pro to share its screen with my iMac. Both OSX 10.6.8; both on Wifi (n). It always went fine. Since a few weeks it won't work and I get an error on the iMac when I call there for the MacBook's screen. I tried switching off Screen sh

  • Continuing issues with two podcasts...

    I am back to having issues with posts not being visible in iTunes... The feeds are: feeds.feedburner.com/SosChurchStockholm and feeds,feedbruner.com/JohannesAmritzersPodcast And they do not validate when trying to verify them through feedvalidator.or