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

Similar Messages

  • Tp error during EHPI checks NTCHK phase

    Hi,
    We are running the EHPI and recieve the following error during the Checks phase:
    Severe error(s) occured in phase PREP_GENCHECKS/NTACT_CHK!
    Last error code set: Process 'tp' exited with 12, see '/uexports/DV1/EHPI/abap/log/TP.ECO' for details
    Error during "tp ntaction"-call - check TP.ECO
    TP.ECO=
    SAPehpi> Starting subprocess 16165 at 20101007100438
    ENV: DIR_LIBRARY=/uexports/DV1/EHPI/abap/exenew
    ENV: JAVA_HOME=/opt/java1.4
    ENV: LD_LIBRARY_PATH=/uexports/DV1/EHPI/abap/exenew:/uexports/DV1/EHPI/jvm/jre/lib/ia64/server:/uexports/DV1/EHPI/jvm/jre/
    lib/ia64:/uexports/DV1/EHPI/jvm/jre/../lib/ia64
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/DV1/102_64
    ENV: ORACLE_SID=DV1
    ENV: PATH=/uexports/DV1/EHPI/abap/exenew:/opt/java1.4/bin:/oracle/DV1/102_64/bin:.:/home/dv1adm:/usr/sap/DV1/SYS/exe/run:/
    usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/fcms/bin:/
    usr/contrib/kwdb/bin:/usr/bin/X11:/opt/graphics/common/bin:/opt/upgrade/bin:/opt/ipf/bin:/opt/resmon/bin:/opt/perf/bin:/op
    t/wbem/bin:/opt/wbem/sbin:/opt/prm/bin:/opt/sec_mgmt/bastille/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/gnome/bin:/opt/ignite/
    bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/hpsmh/bin:/opt/wlm/bin:/opt/hpnpl//bin:/usr/contrib/bin/X11:/opt/sfm/bin:/opt/
    mozilla:/opt/perl_32/bin:/opt/perl_64/bin:/opt/swa/bin:/oa/cdirect/ndm/bin:.
    ENV: SAPSYSTEMNAME=DV1
    ENV: auth_shadow_upgrade=0
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPR3
    ENV: dbs_ora_tnsname=DV1
    EXECUTING /uexports/DV1/EHPI/abap/exenew/tp (/uexports/DV1/EHPI/abap/exenew/tp) ntaction ntop=chkant DV1 pf=/uexports/DV1/
    EHPI/abap/bin/DEFAULT.TPP srctt=DDNTT srctf=DDNTF dsttt=DDNTT dsttf=DDNTF intdel=YES -Dntact_timecmp=no protyear=40
    initial value of NLS_LANG: 'AMERICAN_AMERICA.UTF8'
    This is /uexports/DV1/EHPI/abap/exenew/tp version 372.04.88 (release 701, unicode enabled)
    Warning: Parameter INTERRUPT is no longer used.
    Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 8).
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 8).
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 12
    meaning:
      A tool used by tp aborted
    Process with ID 16165 terminated with status 12
    NTCHK.LOG=
    1 ETQ201 Entering upgrade-phase "NTACT_CHK" ("20101007100438")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ399 Set environment for standard connect:
    4 ETQ399 ENV: dbs_ora_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=0
    4 ETQ399 Set RFC variables for standard connect:
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Set tool parameters for standard connect:
    4 ETQ399   default TPPARAM: DEFAULT.TPP
    1 ETQ200 Executing actual phase 'PREP_GENCHECKS/NTACT_CHK'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'CHKANT'
    2 ETQ399 Arg[1] = 'DDNTT'
    2 ETQ399 Arg[2] = 'DDNTF'
    2 ETQ399 Arg[3] = 'DDNTT'
    2 ETQ399 Arg[4] = 'DDNTF'
    2 ETQ399 Arg[5] = ''
    2 ETQ399 Arg[6] = 'NOBUFRESET'
    2 ETQ399 Arg[7] = ''
    2 ETQ399 Arg[8] = ''
    2 ETQ399 Arg[9] = ''
    2 ETQ399 Arg[10] = 'NTCHK.ELG'
    4 ETQ380 computing toolpath for request "TP_NTACTION_SHD"
    4 ETQ381 request "TP_NTACTION_SHD" means "tp ntact for shadow tables"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHDNEW"
    4 ETQ383 translates to path "exenew"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Checking of nametabs ...
    4 ETQ399 2010/10/07 10:04:38: put_execute: (tp) forkpid:16165
    It doesn't even get to the point of creating NTCHK.ELG
    -rw-rr   1 dv1adm     sapsys      287923 Oct  7 10:19 SAPehpichk.log
    -rw-rr   1 dv1adm     sapsys       13144 Oct  7 10:19 TROUBLE_SAVELOGS.LOG
    -rw-rr   1 dv1adm     sapsys      151957 Oct  7 10:19 SAPehpi_troubleticket_logs.sar
    -rw-rw-r--   1 dv1adm     sapsys       10039 Oct  7 10:19 SLOG700
    -rw-rw-r--   1 dv1adm     sapsys       80609 Oct  7 10:19 ALOG700
    -rw-rr   1 dv1adm     sapsys        9238 Oct  7 10:19 TP.ECO
    -rw-rr   1 dv1adm     sapsys        1729 Oct  7 10:19 SAPehpi_troubleticket.log
    -rw-rw-r--   1 dv1adm     sapsys     112988412 Oct  7 10:19 PN401007.DV1
    -rw-rr   1 dv1adm     sapsys        1292 Oct  7 10:05 NTCHK.LOG
    -rw-rr   1 dv1adm     sapsys       57379 Oct  7 10:05 SAPehpiConsole.log
    -rw-rw-r--   1 dv1adm     sapsys      148736 Oct  7 10:04 ULOG10_4
    -rw-rr   1 dv1adm     sapsys       10692 Oct  7 10:04 SAPehpi.ECO
    -rw-rr   1 dv1adm     sapsys       10581 Oct  7 10:04 NTCHK.SAV
    takderp1:dv1adm 530> ll NT*
    -rw-rr   1 dv1adm     sapsys        1292 Oct  7 10:05 NTCHK.LOG
    -rw-rr   1 dv1adm     sapsys       10581 Oct  7 10:04 NTCHK.SAV
    SAPehpi_troubleticket.log=
    This trouble ticket was created by SAPehpi on 20101007101947
    SAPehpi broke during phase NTACT_CHK in module PREP_GENCHECKS / General checks
    Error Message: Process 'tp' exited with 12, see '/uexports/DV1/EHPI/abap/log/TP.ECO' for details
    Error during "tp ntaction"-call - check TP.ECO
    Summary of SAPehpi:
    SAPehpi Release:        7.10/1
    SAPehpi Version:        SAPehpi version 7.10/1
    Start Release:          700
    Target Release:         701
    Summary of host system details:
    SID:                    DV1
    Host:                   takderp1
    MS Host:                takderp1
    GW Host:                takderp1
    Start Path:             /usr/sap/DV1/SYS/exe/run
    Kernel Path:            /usr/sap/DV1/SYS/exe/run
    Summary of operating system details:
    OS Type:                HP-UX IA64
    OS Version:             11.23
    Summary of database details:
    Database Type:          ora
    Database Version:       10.2.0.2.0
    Summary of RFC details:
    Host:                   takderp1
    GW Host:                takderp1
    Client:                 000
    Destination:            DV1
    Language:
    System No.:             00
    Any help would be appreciated.
    Thanks,
    Jim

    Hi Eric,
    I have the log posted above but here is an excert from the TP.ECO log.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 12
    meaning:
      A tool used by tp aborted
    Process with ID 22858 terminated with status 12
    Regards,
    JIm

  • XPRAS_UPG error in DOWNTIME phase in EHP4

    Hi,
    I am getting the below error in XPRAS_UPG in DOWNTIME phase of EHP4 installation in ERP 6.0 on HP-UNIX and Oracle.
    XPRA ERRORS and RETURN CODE in SAPRW70104.HD1
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1AETR012XProgram terminated (job: "RDDEXECL", no.: "10302400")
      Long text:
        Cause
          Program "&V#&", which was started in the background, was terminated
          abnormally.
        System Response
          The system created a job log for the terminated program.
        What to do
          Proceed as follows:
          Log onto the system in which the program was executed. The system is
          specified at the beginning of the transport log.
          Then call transaction SM37 to display the job log.
          Enter "&V#&" as job name and "DDIC" as user name.
          Restrict the starting date to the starting date specified in the
          transport log.
          For the other selection criteria, select only jobs with the status
          "cancelled". Then press <LS>Execute</>.
          A list of the jobs satisfying the selection criteria is displayed.
          You can display the log by pressing <LS>Job log</>.
          If the list contains several jobs, you can select the job with the ID "
          &V#&" with <LS>Display</> -> <LS>Job details</> or define further
          details for the selection criteria in the initial screen of transaction
          SM37.
          If the ABAP processor reports cancellation, double-clicking on the
          corresponding message in the job log branches to the display of the
          corresponding short dump.
    1AEPU320 See job log"RDDEXECL""10302400""HD1"
    1 ETP111 exit code           : "12"
    >>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
    XPRAs are application reports that run at the end of an upgrade.
    Most XPRA reports have a report documentation that explains what
    the report does and how errors can be corrected.
    Call transaction se38 in the SAP system, enter the report name,
    select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
    I was successfully able to umlock the system and in SM37 I could see the job log pointing to ST22. In ST22 we have many dumps related to error PXA_NO_FREE_SPACE. I found many notes in marketplace but all are referring the parameter abap/buffersize which needs to increased. I am a bit apprehensive about the fact that since we are in DOWNTIME phase and in the middle of XPRA execution phase should we increase the parameter and restart the system and then continue with the upgrade???
    I have also tried to run the phase many times but the same error persists.
    Please can anyone help me to come out of this problem.....
    Thanks & regards,
    Rozal

    Hello Rozal,
    You are correct XPRAS is a downtime 2 phase, but actually your system is up and running. It was started way back in phase "STARTSAP_NBAS" its just that you cannot use your system productively. XPRAS executes the XPRAS methods in the running system.
    Its absolutely safe, you can change the parameter take a restart and continue further.
    - Niraj

  • Error while doing EHP4 upgrade in downtime phase

    HI .
    Iam facing the below error while doing the EHP4 upgrade , in downtime phase.
    Checks after phase MAIN_SWITCH/STARTSAP_TRANS were negative!
    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=Hydhtc4526D, GWSERV=sapgw04, SYSNR=04  LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.136.162.30:3304' not reached TIME Mon Jun 06 18:17:46 2011 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.136.162.30:3304 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER System start failed
    Please help me in resolving this error.
    Sanketh.

    Hi,
    Upgrade tool is trying to start the system but system is not coming up. Try to start system manually and see if system comes up or not. If not then check logs in work directory for why system is not coming up.
    Thanks
    Sunny

  • Upgrade to Solution Manager 7.1 stopped in phase DEPLOY_ONLINE_DEPL

    Dears,
    we are upgrading our Solution Manaher from Ehp1 for Nw 70, to Nw.71.
    While on the ABAP tab is in progress the phase MAIN_NEWBAS\TABIM_UPG on the J2EE tab we are blocked in phase DEPLOY_ONLINE_DEPL.
    As suggested from the Ehpi screen we read note 1399846, but our case is different so the note is not usable.
    First in the logs we have the message:
    Mar 5, 2012 4:54:26 PM [Info]: Processing request to deploy queue sapjup-queue.
    Mar 5, 2012 4:54:26 PM [Error]: Login not performed yet. JSPM not initialized.
    Mar 5, 2012 4:54:26 PM [Error]: Could not process deploy queue sapjup-queue request.
    Mar 5, 2012 4:54:26 PM [Error]: java.lang.NullPointerException: while trying to invoke the method  com.sap.sdt.jspm.model.JspmDataModelIF.save() of an object loaded from field com.sap.sdt.jspm.deployment.queuemanager.QueueManager.dataModel of an object loaded from local variable  this
    Mar 5, 2012 4:54:26 PM [Error]: Login not performed yet. JSPM not initialized.
    That's different respect to the Oss note, then second we did not start manually the JSPM.
    How we can go ahead ?
    We did not find any Oss Note for this error.
    Regards

    after a reboot of the system and a restart of the upgrade process the
    error changed and it was as described in note 1399846.
    So we applied the workaround suggested, but now we have a new error.
    If we restart the upgrade process doing first startsap(so starting both Abap+Java), the upgrade process for the J2EE tab complains  the stack provided and used till now (we are already in the DOWNTIME phase) does not match the system status.
    If we restart the upgrade leaving the Abap+java instances down the upgrade process complain  the SDM is nit 'is not
    able to connect to the system.
    I read somewhere It's possible to disable the upgrade process for the Java stack, in order to complete that one for the ABap stack.
    Then for the Java Stack we could use the normal JSPM, but I'm not able to find the relative Oss note.
    Any advise ?

  • 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

  • EHP4 error in ABAP Down time phase

    Hi All,
    I am installing EHP4, currently the system got stuck in downtime phase .Facing the SQL error
    "22859 - ORA - 22859: invalid modification of columns in DDLs   "
    2EETP345 TATEMENT for 2EETP345
    2EETP345 : error in DDL , name tab 2EETP345  not activated
    We also got a solution for this through SAP note : 1160950
    They have recomended to implement this correction note in the system, but since we are in Shadow phase, we are not allowed to get into the system and through shadow system we are able to connect only via DDIC,SAP* user.But with these users we are not able to implement SNOTE
    So we even tried to unlock the physical system using the command : ./SAPup unlockshd <SID>
    Its throwing an error :
    "SAPup error unable to set envronment variable"
    Please help to resolv this issue

    hi Sunny,
    Here it is :
    gbahev99:dh2adm 112% ./SAPehpi -help
    Enter the path of your root directory [/import/basis/EHG/D2/EHPI/abap]:
    Root directory = /import/basis/EHG/D2/EHPI/abap
    Reexecuting ./SAPehpi with adapted environment and restart=3.
    Usage: SAPehpi [parameter options] [functional options] [functions]
                parameter options:
                          rootdir=<upgrade directory path>
                          gt=SCROLL/SERVER
                          uaport=<port number>
                          hm=<n>
                          cdpath=<CDROM path>
                          toc=<CD archive>
                 functional options:
                          DEBUGON
                 functions:
                          -V[ERSION]
                          startshd/stopshd
                          unlockshd/lockshd
                          set stdpar/rswpar/shdpar
                          set ddicpwd/shdddicpwd
                          set dbopsys/adjprp/sapmodi
                          analyse table <table-name>
                          reset prepare
                          showinput <file>
                          readCD/readKernel
                          export type=SPDD/SPAU ta=.. rel=.. log=..

  • Take very long time in phase DEPLOY_ONLINE_DEPL when install EHP1

    Dear all,<br><br>
    I need help for anyone that read my thread. I get trouble when install SAP EHP1 for SAP NetWeaver 7.1 at our client server, in phase DEPLOY_ONLINE_DEPL(Downtime Step). The phase take very long time. It has been more than 5 hours, but there is no progress. Now, the ABAP Stack has been in MAIN_NEWBAS/GETSYNC_MODPROF_STARTED, to wait process from JAVA stack. I have check the log file drive :\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log:<br>
    <!LOGHEADERSTART/> <br>
    <!HELPManual modification of the header may cause parsing problem!/> <br>
    <!LOGGINGVERSIONhttp://2.0.7.1006/> <br>
    <!NAMEE:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_23_15_59_39\deploy_2010-08-23_15-59-53.log/> <br>
    <!PATTERNhttp://deploy_2010-08-23_15-59-53.log/> <br>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d%6s]:%m)/> <br>
    <!ENCODINGUTF8/> <br>
    <!LOGHEADEREND/> <br>
    Aug 23, 2010 3:59:53 PM Info :DC API is trying to connect to ':50004' <br>
    The content of log file not change after more than 5 hours, still like that. Is it normal ? Or any something miss ?<br>
    My dead line will come tommorrow, please help me
    Regards

    And this the content of log file at drive:\usr\sap\DXI\EHPI\java\log:<br>
    Aug 23, 2010 3:59:37 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. Aug 23, 2010 3:59:37 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 23, 2010 3:59:37 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter action=deploySlot Aug 23, 2010 3:59:37 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter connect=standard Aug 23, 2010 3:59:37 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter errorStrategy=skipDepending Aug 23, 2010 3:59:37 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter rule=all Aug 23, 2010 3:59:37 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect. Aug 23, 2010 3:59:37 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 23, 2010 3:59:37 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:152) [Thread[main,5,main]]: Trying to connect JSPM. Aug 23, 2010 3:59:37 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 23, 2010 3:59:38 PM [Info]: com.sap.sdt.util.proc.Process.start(Process.java:164) [Thread[main,5,main]]: E:\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp e:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm -boot=win -port=6250 -properties=jspm-srv_config.txt -startJSPM Aug 23, 2010 3:59:39 PM [Info]: java.lang.Thread.dumpThreads(Thread.java:-2) [Thread[ProcessReader,5,main]]: >> Current log directory is E:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\log\log_2010_08_23_15_59_39. Aug 23, 2010 3:59:40 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.finished(AbstractToolConnector.java:373) [Thread[Process(E:\usr\sap\DXI\EHPI\jvm\jre\bin\java -ea -Xmx1024m -cp e:\usr\sap\DXI\DVEBMGS00\j2ee\JSPM\bootstrap\lib\sdt_jspm_bootstrap.jar Jspm),5,main]]: JSPM terminated with exit code 0. Aug 23, 2010 3:59:41 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:721) [Thread[main,5,main]]: Connected to host jktbtrsapx1 on port 6250. Aug 23, 2010 3:59:53 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:164) [Thread[main,5,main]]: JSPM was started successfully. Aug 23, 2010 3:59:53 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:207) [Thread[main,5,main]]: Trying to log in with user SAP*. <br><br>
    Please help me

  • Urgent -- SOLMANUP -- Problems in Phase DEPLOY_ONLINE_DEPL

    Hello,<br>
    i'm trying to update my SOLMAN from 7 EHP1 to 7.1 (Running Linux (x86)/Oracle DB)  with SOLMANUP<br>
    I'm hanging in the downtime phase now: DEPLOY_ONLINE_DEPL (Java EE)... <br>
    It looks like it's a password-problem, no doubt, but where can i set or check the passwords in the downtime pahse ?<br>
    <br>
    i tried to start SDM for checking the password but i can't start the SDM Server. <br>
    Please could anyone give me some advices how to check/change the passwords to go ahead with SOLMANUP here.<br>
    <br>
    Thanks and best regards,<br>
    <br>
    Christian
    <br>
    PS: here the detailed information:<br>
    <br>
    The  SDTgui gives me the following Error:<br>
    Phase Error Report: Review the error report information and troubleshoot the proble<br>
    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_CSM_20111212155700.713.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.02.8.0.3. Current JSPM log directory is /usr/sap/CSM/DVEBMGS70/j2ee/JSPM/log/log_2011_12_23_09_46_38. The following SAP Note 1399846 may contain solution for the problem.<br>
    You can find more information in the log file /usr/sap/CSM/SOLMANUP/java/log/DEPLOY_ONLINE_DEPL_DDB_08.LOG.<br>
    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 /usr/sap/CSM/SOLMANUP/java/log/TroubleTicket_12.txt to your message.<br>
    <br><br>
    The log-file mentioned:<br>
    rksapv02:csmadm 229> more /usr/sap/CSM/SOLMANUP/java/log/DEPLOY_ONLINE_DEPL_DDB_08.LOG<br>
    <!LOGHEADER[START]/><br>
    <!HELP[Manual modification of the header may cause parsing problem!]/><br>
    <!LOGGINGVERSION[2.0.7.1006]/><br>
    <!NAME[/usr/sap/CSM/SOLMANUP/java/log/DEPLOY_ONLINE_DEPL_DDB_08.LOG]/><br>
    <!PATTERN[DEPLOY_ONLINE_DEPL_DDB_08.LOG]/><br>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/><br>
    <!ENCODING[UTF8]/><br>
    <!LOGHEADER[END]/><br>
    Dec 23, 2011 9:46:38 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initializeAbstractPhaseType.java:754) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE
    _DEPL has been started.
    Dec 23, 2011 9:46:38 AM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDeplo
    ymentManager.
    Dec 23, 2011 9:46:38 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter action=deploySlot
    Dec 23, 2011 9:46:38 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter connect=standard
    Dec 23, 2011 9:46:38 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter errorStrategy=skipDepending
    Dec 23, 2011 9:46:38 AM [Info]:                   com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]:   Parameter rule=all
    Dec 23, 2011 9:46:38 AM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.checkParameters(PhaseTypeDeploymentManager.java:558) [Thread[main,5,main]]: Checking phase parameters action, connect.
    Dec 23, 2011 9:46:38 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.
    Dec 23, 2011 9:46:38 AM [Info]:     com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.deploy(SAPJupJSPMRapiAdapter.java:475) [Thread[main,5,main]]: Starting deployment.
    Dec 23, 2011 9:46:38 AM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:128) [Thread[main,5,main]]: Trying to connect JSPM.
    Dec 23, 2011 9:46:38 AM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:137) [Thread[main,5,main]]: JSPM is not connected, trying to start it.
    Dec 23, 2011 9:46:38 AM [Info]:                                                com.sap.sdt.util.proc.Process.start(Process.java:164) [Thread[main,5,main]]: /usr/sap/CSM/SOLMANUP/jvm/jre/bin/java -ea  -Xmx1024
    m -cp /usr/sap/CSM/DVEBMGS70/j2ee/JSPM/bootstrap/lib/sdt_jspm_bootstrap.jar  Jspm -boot=unx  -port=6250 -properties=jspm-srv_config.txt -startJSPM
    Dec 23, 2011 9:46:39 AM [Info]:                                                     java.lang.Thread.getStackTrace(Thread.java:1513) [Thread[ProcessReader,5,main]]: >> Current log directory is /usr/sap/CSM/DV
    EBMGS70/j2ee/JSPM/log/log_2011_12_23_09_46_38.
    Dec 23, 2011 9:46:39 AM [Info]:                                                     java.lang.Thread.getStackTrace(Thread.java:1513) [Thread[ProcessReader,5,main]]: >> Closed input stream
    Dec 23, 2011 9:46:39 AM [Info]:                                                     java.lang.Thread.getStackTrace(Thread.java:1513) [Thread[ProcessReader,5,main]]: >> Closed input stream
    Dec 23, 2011 9:46:39 AM [Info]:     com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.finished(AbstractToolConnector.java:374) [Thread[Process(/usr/sap/CSM/SOLMANUP/jvm/jre/bin/java -ea  -Xmx1024m -cp /
    usr/sap/CSM/DVEBMGS70/j2ee/JSPM/bootstrap/lib/sdt_jspm_bootstrap.jar  Jspm),5,main]]: JSPM terminated with exit code 0.
    Dec 23, 2011 9:46:40 AM [Info]:      com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:731) [Thread[main,5,main]]: Connected to host rksapa00 on port 6250.
    Dec 23, 2011 9:46:40 AM [Warning]:   com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.discardMsg(AbstractToolConnector.java:777) [Thread[JSPM,5,main]]: Discarding message $com.sap.sdt.sltool.rapi.conne
    ctor.MsgData@15e8e5a7
    Dec 23, 2011 9:46:45 AM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:140) [Thread[main,5,main]]: JSPM was started successfully.
    Dec 23, 2011 9:46:45 AM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:185) [Thread[main,5,main]]: Trying to log in with user SAP*.
    Dec 23, 2011 9:46:45 AM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:191) [Thread[main,5,main]]: JSPM detect non deployable components login request
    property is set to "false".
    Dec 23, 2011 9:47:00 AM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:200) [Thread[main,5,main]]: JSPM successfully logged in with user SAP*.
    Dec 23, 2011 9:47:00 AM [Info]:              com.sap.sdt.util.net.AbstractCharacterCommLink.read(AbstractCharacterCommLink.java:140) [Thread[CharacterCommLink,5,main]]: Socket closed
    Dec 23, 2011 9:47:00 AM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.handleMsgClosed(AbstractToolConnector.java:561) [Thread[JSPM,5,main]]: Reporting failed commlink.
    Dec 23, 2011 9:47:02 AM [Info]:         com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForJSPMTermination(JSPMConnector.java:483) [Thread[main,5,main]]: JSPM stopped.<br>
    Dec 23, 2011 9:47:02 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.<br>1
    Dec 23, 2011 9:47:02 AM [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 pass
    word is correct and the system is up and running.
    JSPM version is 7.02.8.0.3. Current JSPM log directory is /usr/sap/CSM/DVEBMGS70/j2ee/JSPM/log/log_2011_12_23_09_46_38.
    Dec 23, 2011 9:47:02 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:722) [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.
    Dec 23, 2011 9:47:02 AM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:714) [Thread[main,5,main]]: JSPM could not log in to the Java se
    rver with user SAP*. Probably the server is not running or the provided credentials are not correct.
    Dec 23, 2011 9:47:02 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 /usr/sap
    /trans/EPS/in/SMSDXML_CSM_20111212155700.713.xml.
    Dec 23, 2011 9:47:02 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.
    Dec 23, 2011 9:47:02 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.
    Dec 23, 2011 9:47:02 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2011/12/23 09:46:38.
    Dec 23, 2011 9:47:02 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2011/12/23 09:47:02.
    Dec 23, 2011 9:47:02 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:24.026.
    Dec 23, 2011 9:47:02 AM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
    Edited by: Christian Hammel-Woitusch on Dec 23, 2011 10:30 AM

    well - now i'm having a new problem - the SDM Server won't start.
    i've already found another forum topic here: SDM not starting integrated only standalone
    i'm going through the points there...   
    @Nicolas
    thank you for this useful information!
    @Sunny
    i tried to start JSPM but it recognizes that there's already some stuff in progress... so taht seems to be fine.
    @Ajitabh:
    thank you for those notes - i already read one of them...  where do i get the information wich NW Version applies fpr my Upgrade - means which componentis used here?

  • 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

  • Upgrade Fails in downtime Phase - MAIN_SWITCH/PARMVNT_XCNV

    Dear All,
    We are working on the upgrade from ECC6.0 to ECC6.0 with EHP4 and now running in the downtime phase. In the downtime phase, the upgrade stopped in the phase of MAIN_SWITCH/PARMVNT_XCNV and stated that to check the logs of MVNTXCNV.ELG. In the log file it stated that
    MVNTXCNV.ELG
    MVNTTABS ERRORS:ddlntabs and RETURN CODE in PD000825.FSO
    SQL -error Duplicate name:SRT_MONLoG_DATA2 in DDL st
    SRT_MONLOG_DATA2
    error in DDL nametab for "SRT_MONLOG_DATA2 not activated
    Then I have searched in SMP and in SDN and came to know that we need to implement the notes of
    Note 1399438 - System upgrade stops in phase XCNV
    Note 1310677 - System upgrade terminates in phase MAIN_SWITCH/PARMVNT_XCN
    Hence, I have started the instance manually and unlocked the tp to login as different user for applying this note ( Because we cannot apply note usign DDIC ) . Then able to login into the system and downloaded the notes as well,
    While implementing the when I try to create a request - it immediately throwing a short dump and dump states that
    TRINT_INSERT_COMM_HEADER
    SQL error in the database when accessing a table
    Database error text: POS(40) too few values
    Internal call code: RSQL/INSR/EO70C
    Please check the same in SM21
    In system logs the logs says that
    Runtime error DBIF_RSQL_SQL_ERROR
    Short dump created
    Database error -1200 at PRE access to table E070c
    POS (40) Too few values
    Instead of creating a new request and tried to use own request but the results are same,  Also i tried to change the client settings from automatic recording of changes and also changes w/o automatic recording of changes - but both are giving the same output.
    Is there any other possibility to get rid off this issue?  Any suggestions are highly appreciated
    Regards
    Vijay

    Its fixed and I have just implemented the note 589296 - Solved our issue
    select * from "SAPFSO"."DDXTT~" where TABNAME = 'SRT_MONLOG_DATA2'
    or
    select * from "SAPFSO"."DDXTT" where TABNAME = 'SRT_MONLOG_DATA2'
    Check it approximately it should return with the FLAG value as F
    update "SAPFSO"."DDXTT~" set modeflag = 'A' where TABNAME = 'SRT_MONLOG_DATA2'
    Thanks for your support
    Regards
    Vijay

  • Error in the PREP_GENCHECKS/NTACT_CHK phase

    Hello,
    I am getting an error in the PREP_GENCHECKS/NTACT_CHK phase during the "Checks" roadmap step in SAP Ehpi 700, while installing EHP4 for ERP 6.0.
    This is the error it talks about:
    ERROR> *** ERRORS during NAMETAB CHECK found ***
    Analyze the logfile NTCHK.ELG to determine the nametab, that caused the error. Call transaction se11 for the corresponding DDIC object. Choose menu Utilities -> Runtime Object -> Check. If you repeat the phase and there is still an error, see also note Nr. 179334 for additional information.
    This is what I found in NTCHK.ELG file:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CHKANT and RETURN CODE in PN400701.EV2
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETP399XRead table "M_DEBI                        ": pgntab call: table not found.
    2AETP399 Table "M_DEBI                        ": unknown error -9
    2EETP399XRead table "M_ORDE                        ": pgntab call: table not found.
    2AETP399 Table "M_ORDE                        ": unknown error -9
    2EETP399XRead table "M_PRSM                        ": pgntab call: table not found.
    2AETP399 Table "M_PRSM                        ": unknown error -9
    2EETP399XRead table "M_ZCRD                        ": pgntab call: table not found.
    2AETP399 Table "M_ZCRD                        ": unknown error -9
    2EETP399XRead table "M_ZCST                        ": pgntab call: table not found.
    2AETP399 Table "M_ZCST                        ": unknown error -9
    2EETP399XRead table "M_ZESS                        ": pgntab call: table not found.
    2AETP399 Table "M_ZESS                        ": unknown error -9
    2EETP399XRead table "M_ZEST                        ": pgntab call: table not found.
    2AETP399 Table "M_ZEST                        ": unknown error -9
    2EETP399XRead table "M_ZINC                        ": pgntab call: table not found.
    2AETP399 Table "M_ZINC                        ": unknown error -9
    2EETP399XRead table "M_ZKTX                        ": pgntab call: table not found.
    2AETP399 Table "M_ZKTX                        ": unknown error -9
    2EETP399XRead table "M_ZMA1                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMA1                        ": unknown error -9
    2EETP399XRead table "M_ZMAC                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMAC                        ": unknown error -9
    2EETP399XRead table "M_ZMAI                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMAI                        ": unknown error -9
    2EETP399XRead table "M_ZMAJ                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMAJ                        ": unknown error -9
    2EETP399XRead table "M_ZMNH                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMNH                        ": unknown error -9
    2EETP399XRead table "M_ZMNI                        ": pgntab call: table not found.
    2AETP399 Table "M_ZMNI                        ": unknown error -9
    2EETP399XRead table "M_ZPER                        ": pgntab call: table not found.
    2AETP399 Table "M_ZPER                        ": unknown error -9
    2EETP399XRead table "M_ZUOM                        ": pgntab call: table not found.
    2AETP399 Table "M_ZUOM                        ": unknown error -9
    1 ETP111 exit code           : "12"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CHKANT and RETURN CODE in PN410701.EV2
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    As mentioned in SAP note 179334, when I tried to activate these table pools in the ABAP dictionary (SE11), it gave me an error "Maintain size category in SE13". After maintaining the size category and putting it in an SAP standard package, I tried to activate again in SE11. But now I am getting another error - "Table M_ZUOM: active nametab could not be read. Length of VARDATA field cannot be changed."
    How do I activate these table pools and get on with the EHP4 installation?
    I am on SAPKB70018, so I don't need to apply the note 695195.
    Thanks,
    Ajay

    Hi
    > As mentioned in SAP note 179334, when I tried to activate these table pools in the ABAP dictionary (SE11), it gave me an error "Maintain size category in SE13". After maintaining the size category and putting it in an SAP standard package, I tried to activate again in SE11. But now I am getting another error - "Table M_ZUOM: active nametab could not be read. Length of VARDATA field cannot be changed."
    >
    > How do I activate these table pools and get on with the EHP4 installation?
    As you are now getting error that length of VARDAT field cannot change. Then check on database level and if it does not contain any data then change field length manually as per  in logs. Then try again
    Thanks
    Sunny

  • Duration between Preprocessing and Downtime phase

    Hello All,
    We are currently upgrading our system from SAP ECC 6.0 EHP4 to EHP5. To reduce the performance issues caused to our production system due to the preprocessing phase running inthe background during productive use, we are planning to complete the Preprocessing phase over one weekend and start the Downtime phase during the subsequent weekend.
    Though logically I think we can do it, can anyone confirm if there could be any issues by seperating the end of the Preprocessing phase and start of the downtime phase by a week?
    Let me know what precautions we need to take in case if this is possible.
    Thanks
    D

    Hello Jorge,
    Sorry for the delay in my response, SCN was not letting me logon. SSO error. Yes you can start the downtime phase later. Just take care that there is a change freeze so that no changes/transports being moved to production.
    Hope this helps.
    Regards
    Dee

  • Error while executing SDM process phase with action DEPLOY_SLOT

    Hi,
    I am upgrading CRM 2007 to CRM 7.0 and got an error in Java side.
    Following is DEPLOY_SLOT_1_DON_01.LOG
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG]/>
    <!PATTERN[DEPLOY_SLOT_1__DON_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    May 20, 2009 4:15:48 AM  Info:
    May 20, 2009 4:15:48 AM  Info: ============================================
    May 20, 2009 4:15:48 AM  Info: =   Starting to execute command 'deploy'   =
    May 20, 2009 4:15:48 AM  Info: ============================================
    May 20, 2009 4:15:48 AM  Info: Starting SDM - Software Deployment Manager...
    May 20, 2009 4:15:49 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
    May 20, 2009 4:15:51 AM  Info: SDM operation mode successfully set to: Standalone
    May 20, 2009 4:15:52 AM  Info: Initializing Network Manager (50017)
    May 20, 2009 4:15:52 AM  Info: Checking if another SDM is running on port 50018
    May 20, 2009 4:15:53 AM  Info: -
    Starting deployment -
    May 20, 2009 4:15:53 AM  Info: Error handling strategy: OnErrorSkipDepending
    May 20, 2009 4:15:53 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    May 20, 2009 4:15:53 AM  Info: Update strategy: UpdateLowerVersions
    May 20, 2009 4:15:53 AM  Info: Starting deployment prerequisites:
    May 20, 2009 4:15:55 AM  Info: Loading selected archives...
    May 20, 2009 4:15:55 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA'
    May 20, 2009 4:16:43 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA'
    May 20, 2009 4:16:48 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA'
    May 20, 2009 4:16:50 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA'
    May 20, 2009 4:17:00 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA'
    May 20, 2009 4:17:02 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA'
    May 20, 2009 4:17:13 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA'
    May 20, 2009 4:17:24 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA'
    May 20, 2009 4:17:31 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA'
    May 20, 2009 4:17:35 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA'
    May 20, 2009 4:17:37 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA'
    May 20, 2009 4:18:02 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA'
    May 20, 2009 4:18:04 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA'
    May 20, 2009 4:18:08 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA'
    May 20, 2009 4:18:09 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA'
    May 20, 2009 4:18:10 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA'
    May 20, 2009 4:18:13 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA'
    May 20, 2009 4:18:20 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA'
    May 20, 2009 4:18:26 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA'
    May 20, 2009 4:18:43 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA'
    May 20, 2009 4:18:45 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA'
    May 20, 2009 4:18:50 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA'
    May 20, 2009 4:18:51 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA'
    May 20, 2009 4:18:56 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA'
    May 20, 2009 4:19:03 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA'
    May 20, 2009 4:19:10 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA'
    May 20, 2009 4:19:12 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
    May 20, 2009 4:19:43 AM  Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
    May 20, 2009 4:19:43 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
    May 20, 2009 4:19:45 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA'
    May 20, 2009 4:19:48 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA'
    May 20, 2009 4:19:49 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA'
    May 20, 2009 4:20:55 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA'
    May 20, 2009 4:21:00 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA'
    May 20, 2009 4:21:39 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA'
    May 20, 2009 4:23:18 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA'
    May 20, 2009 4:23:24 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA'
    May 20, 2009 4:23:27 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA'
    May 20, 2009 4:23:33 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA'
    May 20, 2009 4:23:37 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA'
    May 20, 2009 4:23:54 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA'
    May 20, 2009 4:23:58 AM  Info: Loading archive '
    nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA'
    May 20, 2009 4:23:59 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA'
    May 20, 2009 4:24:00 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA'
    May 20, 2009 4:24:02 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA'
    May 20, 2009 4:24:05 AM  Error: Error while loading selected archives.
    May 20, 2009 4:24:05 AM  Error: Prerequisites were aborted.
    May 20, 2009 4:24:13 AM  Error: Error while loading selected archives.
    May 20, 2009 4:24:13 AM  Info: Summarizing the deployment results:
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Precondition violated: C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial:
    nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Initial: C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA
    May 20, 2009 4:24:13 AM  Error: Processing error. Return code: 4
    It appears to me that somehow there is a component conflict:
    May 20, 2009 4:19:12 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
    May 20, 2009 4:19:43 AM  Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
    May 20, 2009 4:19:43 AM  Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
    Is it advisable at all to manually delete the above LMTOOLS03_01.SCA from the location and try again or this will lead to more errors?
    Please help ASAP, thanks a lot,
    Shival

    Following is the trouble ticket information:
    Trouble Ticket Report
    Upgrade to Enhancement Package 1 SR1 for SAP NetWeaver/ SAP Business Suite 7 SR1
    SID................: CD1
    Hostname...........: nbg-dev-cd1
    Install directory..: c:/usr/sap/CD1
    Upgrade directory..: C:\usr\sap\jupgrade
    Database...........: SAP DB
    Operating System...: NT
    JDK version........: 1.4.2_15 Sun Microsystems Inc.
    SAPJup version.....: 1.5.6
    Source release.....: 700
    Target release.....: 700
    Current usages.....: AS;EP;EPC;BP-CRM;JCRM;AAS
    ABAP stack present.: true
    The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
    Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
    Cannot execute Java process for deployList with parameters C:/usr/sap/jupgrade/tmp/SLOT.DEPLOY.LST.
    Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.
    More information can be found in the log file C:\usr\sap\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
    Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
    com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
    com.sap.sdt.ucp.phases.PhaseException
    Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
    DEPLOY_ONLINE
    UPGRADE
    NetWeaver Upgrade
    SAPJup
    Java Upgrade

  • Error in Import JAVA DUMP phase in Solution Manager installation.

    Hi,
    when i am installing Solution manager i am getting error in import java dump phase on windows and oracle database. i installed java 1.4.2_09 . plz anybody give the solution. Its very urgent.
    Thanks,
    Venkat.

    Hi,
    1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
    2. Add JAVA_HOME = Java path in environment variable.
    3. What is the exact error, you got it, post error here.
    Regards,
    Srini Nookala

Maybe you are looking for