Error in Downtime phase STARTSAP_NBAS

Hi Experts,
Am in the middle of EHP7 upgrade from ECC6.0 with 7.4 SP 37 kernel.
Got an error saying Logon not possible (error in license check). So tried to upload the new license file via SLICENCE but got into new issue saying
The license key library has not been initialized.
I have downloaded the latest COMMONCRYPTO LIB file and updated in the kernel. SAP is not starting after applying those new files even reverted with the old crypto lib files but still the same issue.
SAP is not coming up. R3trans -d is fine. There was no log written in work directory as well.
Please assist.
Regards,
Raja. G

SAPSTARTSRV.LOG
[Thr 01] Tue Apr  8 09:18:07 2014
No halib defined => HA support disabled
CCMS agent initialization for instance type ABAP: return code 0.
CCMS agent start: return code 0.
Initializing SAPControl Webservice
Starting AutoRestart thread
[Thr 515] Tue Apr  8 09:18:13 2014
AutoRestart thread started
SapSSLInit failed => https support disabled
Starting WebService thread
Webservice thread started, listening on port 50313
Trusted http connect via Unix domain socket '/tmp/.sapstream50313' enabled.
trusted unix domain socket user is starting SAP System at 2014/04/08  9:18:17
trusted unix domain socket user is starting SAP System at 2014/04/08  9:22:27
trusted unix domain socket user is starting SAP System at 2014/04/08  9:49:49
trusted unix domain socket user is starting SAP System at 2014/04/08  9:59:04
SAPSTART.LOG
SAP-R/3-Startup Program Rel 740 V2.0 (2008/11/15)
Starting at 2014/04/09 08:45:51
Startup Profile: "/usr/sap/SID/SYS/profile/SID_DVEBMGS03_hostname"
Starting Programs
(16580712) Waiting for Child Processes to terminate.
(16580712) **** No more Child Processes to wait for.
(16580712) Parent Shutdown at 2014/04/09 08:45:51
Execute Post-Shutdown Commands
(16580712) Exiting with Return-Code 3. (No more child processes)
Regards,
Raja. G

Similar Messages

  • 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

  • Upgrade to ERp6 phase STARTSAP_NBAS error: DDIC login fails

    Hi
    During an upgrade from 4.7  to ERP6  I get the following error
    message in phase STARTSAP_NBAS:
    SYSTEM START failed, code -2
    -2: the test rfc did not work.
    Try to log on to the system with user DDIC
    When I try to log on to the system as user DDIC, I get the following
    error message:
    DB-Error -0
    SAP* can log in .The password I submit is correct. I have not changed this password at
    any time.
    Any ideas are most welcome

    Hi,
    DB-Error -0 indicate problem with kernel, try to upgrade kernel.
    check Note 760175 - 6.20: Logon not possible (after DB export or system copy)
    regards,
    kaushal

  • Upgrade phase STARTSAP_NBAS error: SYSTEM START failed

    During an upgrade from BW 3.5 to BI 7.0, I get the following error
    message in phase STARTSAP_NBAS:
    SYSTEM START failed, code -2
    -2: the test rfc did not work.
    Try to log on to the system with user DDIC
    When I try to log on to the system as user DDIC, I get the following
    error message:
    DB-Error -0
    The same thing happens when I try to log on as SAP*. I am certain that
    the password I submit is correct. I have not changed this password at
    any time.
    I have included SAP_BASIS support package 14 into this upgrade, and
    this requires kernel version 133 at least (Note 822379). This kernel
    was copied into the usr\sap\put\exenew directory before the upgrade
    began. However, the system still seems to run on kernel version 111.
    I have tried to put the 133 kernel into
    F:\usr\sap\BWS\SYS\exe\nuc\NTAMD64 so that it is copied into
    F:\usr\sap\BWS\SYS\exe\run during system startup, but then all my work
    processes die. The gateway also seems to be down using this kernel.
    Please help!
    Regards,
    Thomas

    Hi.
    I made a stupid mistake.. the kernel I was using was unicode, but I should use a non-unicode kernel..
    Regards,
    Thomas

  • 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 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 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

  • PI 7.1 upgrade error in GETSYNC_PROFILES_CHANGED phase

    Hello
    Currently I am upgrading an XI 7.0 system to PI 7.1. The downtime phases have just started and I've hit an error in the phase 'GETSYNC_PROFILES_CHANGED'; the error is 'Not enough space for string replacement'. Based on the phase name, and the previous phases, it looks as if the error is something to do with the profiles. The relevant upgrade logs have no useful info in them except for the string space message.
    I have done the usual SDN, SAP Marketplace and Google searches but could not find an answer to my problem. I have also opened a high priority call with SAP but they have not come up with an answer yet. Does anybody have any useful advice?
    The system being upgraded is running on Windows 2003 Server R2 64bit, has an Oracle 10.2.0.4 DB, and the source system was XI/PI 7.0 SP15.
    Thanks.

    Hello Rohit
    Freespace is more than sufficient:
    C:\ = 5.2GB (O/S)
    D:\ = 18.9GB (Oracle & SAP)
    E:\ = 8.53GB (Oracle)
    Andrew
    Edited by: Andrew Turvey on May 28, 2009 3:48 PM

  • 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

  • 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 in preprocessing phase

    Hi All ,
    We are facing error in preprocessing phase of upgrade to EHP 7 ,Let me know if anyone can help us in this critical situation
    System details:Oracle 11gr2,Linux x86-64 ,
    Below is the error :
    During the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RFCDEST_CREATE_S2OX in
    Pre-processing of the SUM we are facing below error.
    1 ETQ233 Calling function module "FUNCTION_EXISTS" by RFC
    2 ETQ373 parameter "FUNCNAME" = "RFC_DESTINATION_CREATE"
    1 ETQ234 Call of function module "FUNCTION_EXISTS" by RFC succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ359 RFC Login to: System="XXX", AsHost="sapXXXpas" Nr="12",
    GwHost="sapa10pas", GwService="sapgwZZ"
    2 ETQ232 RFC Login succeeded
    4 ETQ010 Date & Time: 20140912043336
    1 ETQ233 Calling function module "RFC_DESTINATION_CREATE" by RFC
    2 ETQ373 parameter "DESTINATION_NAME" = "SAP_UPGRADE_ORIG_SYSTEM"
    2 ETQ373 parameter "USER" = "DDIC"
    2 ETQ373 parameter "HOST" = "sapXXXpas"
    2 ETQ373 parameter "SYSTEMNR" = "11"
    2 ETQ373 parameter "CHECK" = "X"
    1EETQ235 Call of function module "RFC_DESTINATION_CREATE" by RFC failed
    (error-status "3")
    2EETQ360 RFC of "RFC_DESTINATION_CREATE" failed:
    2EETQ361 code/exception : 3
    2EETQ362 key : CALL_FUNCTION_NO_DEST
    2EETQ399 RFC destination SAP_UPGRADE_ORIG_SYSTEM does not exist.
    Regards
    Bharat
    Mob No: 91 9008804153

    Hi Reagan ,
    The issue was taken to SAP development security team :::Below is the  weird issue ::
    Firstly ,for the authorizations to work correctly, all authorization tables must be in a consistent state as below :
    ust04, ust10c, ust10s, ust12, usrbf2, usrbf3.
    If we  want to maintain authorizations, also usr04, usr10, usr12 are  required.
    But here , a mismatch of tables usrbf2 and usrbf3  in 2 instances are the reason for the stuck in the upgrade :::
    SQL> select count(*) from sapsr3.USRBF2 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    2997
    SQL> select count(*) from sapsr3.USRBF3 where MANDT = '000' and BNAME =
    'DDIC';
    COUNT(*)
    1
    SQL>
    SQL> select count(*) from sapsr3shd.USRBF2 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    673
    SQL> select count(*) from sapsr3shd.USRBF3 where MANDT = '000' and
    BNAME =
    'DDIC';
    COUNT(*)
    1
    This issue was resolved by SAP and then upgrade went fine ,This is not an issue with password of DDIC !!!!!
    Regards
    Ram

  • Error during upgrade phase JOB_RSUPGCUA_SHD

    Hi Everyone,
    We are in the process of completing a combined ERP 6.0 Upgrade / Unicode Conversion.  Our starting release is ECC 5.0 (ABAP only) and we are running Oracle 10.2.0.2 on AIX 5.3. 
    We are receiving the following error in phase JOB_RSUPGCUA_SHD:
    1 ETQ201XEntering upgrade-phase "JOB_RSUPGCUA_SHD" ("20080812163717")
    2 ETQ366 Connect variables are set for shadow instance access
    4 ETQ399 System-nr = '56', GwService = 'sapgw56'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=1
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ010 Date & Time: 20080812163717
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ230 Starting RFC Login to: System = "ENP", GwHost = "aix12j1", GwService = "sapgw56"
    4 ETQ359 RFC Login to: System="ENP", Nr="56", GwHost="aix12j1", GwService="sapgw56"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    2EETQ235 Call of function module "SUBST_START_BATCHJOB" by RFC failed (error-status "10")
    2EETQ261 Start of batchjob "RSUPGCUAGEN111" failed
    1EETQ203 Upgrade phase "JOB_RSUPGCUA_SHD" aborted with errors ("20080812163717")
    We originally had some issues with the shadow system not starting in phase START_SHDI_FIRST.  The source of the problem was the value of paramter ipc/shm_psize_40 in the instance profile of the shadow system.  When we ran "sappfpar check" on the profile, the output indicated that the paramter was too small.  We backed up the profile, increased the parameter to the value "sappfpar check" recommended and then stopped the shadow system via "SAPup stopshd."  We then repeated the phase.  The shadow instance was started successfully and the upgrade proceeded with subsequent phases.
    We encountered the error above several phases later.  The shadow instance is started and I am able to login with user DDIC.  As detailed in the error message above, function module SUBST_START_BATCHJOB is aborting with error code 10.  Based on what I can interpret from source code of the function module, this seems to indicate that there is a problem with the program values.  The SM21 log indicates that "Program name RSUPGCUAGEN111 is invalid." 
    What do we need to do to get past this error?
    Thanks in advance for any assistance,
    Tommye

    for our case it was that the shadow instance was not completely stsarted, some processes were down, cause the ipc pool 40 was too small, i found the error in the killed work processes.
    Probleme resolved as susch. i hope it will help someone.
    Regards

  • Support Pack upgrade error in Import Phase

    Hello,
    Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
    Could you please help me on this? I tried and still searching solution for this..But no luck...
    Os is : AIX and
    Log File:                /usr/sap/trans/log/SAPIB70013.xxx
    Main import
    Transport request   : SAPKB70013
    System              : xxxx
    tp path             : tp
    Version and release: 372.04.71 700
    child process 934006 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_OBJECT_COLLECTION==========CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1212554 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDR_APPLICATION_WINDOW=====CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1171520 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_EVENT_SOURCE========CI
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1331412 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    insert / update sequence failed due to an error in DBI.
    maybe there's a concurrent process which inserted this table entry at the same time.
    insert / update sequence failed due to an error in DBI.                       
    maybe there's a concurrent process which inserted this table entry at the same time.
    child process 1310922 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_END
    tabname:    WDY_APP_PROPERTY
    len (char): 64
    key:        DEMO_UIEL_DROPDOWN_BY_IDX     DEMO_VIEW
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 018446 - 999999 not imported because the child processes died for unknown reason
    child process 1310924 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_report_interface
    fcode:      CLOSE_LINE_MODE
    tabname:    SOURCE
    len (char): 40
    key:        CL_WDY_MD_OUTGOING_EVENT======CT
    retcode:    1
    SQL error -913 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
    child process 1286192 terminated -> setting rc=12 for this import portion
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    import portion 009158 - 018411 not imported because the child processes died for unknown reason
    import portion 018412 - 018527 not imported because the child processes died for unknown reason
    import portion 018528 - 999999 not imported because the child processes died for unknown reason
    sap_dext called with msgnr 1:
    db call info -
    function:   db_xrtab
    fcode:      RT_MI_LOAD
    tabname:    ECSCR_DATA
    len (char): 106
    key:        EC_TEST_DATA                  00000000P10                           IECATTDEFAULT
    retcode:    1
    SQL error -904 accessing  : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
    Main import
    End date and time : 20100909034914
    Ended with return code:  ===> 12 <===
         |   ######################################                     
    Thanks and Regards,
    Sankar
    SAP BASIS Consultant

    Hi,
    Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          10.09.2010 09:41:37
    Short text
         Function module "POSS_UIREQ_OPT_SUBMIT" not found.
    What happened?
         The function module "POSS_UIREQ_OPT_SUBMIT" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSTXC" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
          not caught in
         procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         The program "SAPLSTXC" contains the CALL FUNCTION statement.
         The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
         No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
         All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attenti
        upper/lower case and underscores ("_").
        or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
        the lock object may not have been activated
        (ABAP/4 Dictionary).
    When i tried to check function module it is not there..
    Could you please help on this?
    Regards,
    Sankar Basis Consultant

  • Error in ABAP_Import Phase

    Dear Guru's,
    We are facing some issue on ABAP Import phase, out of 29 Import Monior jobs 2 jobs gets failed.
    Error in Import_ABAP Phase, 2 jobs failed
    Loading of 'DD03L' import package: ERROR
    Loading of 'SACONT01' import package: ERROR
    could anyone suggest me, what could be done to resolve this issue.
    regards,
    Guna

    Hi,
    Thanks for your information.
    We tried with retry option, still in same position.
    We're doing solution manager 7.0 installation on AIX 5.
    (DB) INFO: SACONT01 deleted/truncated #20100429153529
    (DB6) Using LOAD API for table SACONT01
    (RFF) ERROR: invalid checksum in data file "/hm/cdmedia/solman7.0/51033518_Expor
    t2/EXP3/DATA/SACONT01.001"
                 current table was "SACONT01"
    (DB) INFO: disconnected from DB
    /usr/sap/SM1/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/SM1/SYS/exe/run/R3load: END OF LOG: 20100429153530
    Suggestions appreciated.
    regards,
    Guna

  • Error in ACTIVATE_CURRENT_USAGES phase of portal upgrade (NW04 to NW04s)

    hello gurus,
    i am upgrading Netweaver 04 to netweaver 04s (Enterprise Portal)
    oracle upgrade from 9.2.0.7 to 10.2.0.1 successfully
    but i am getting error in 78 phase out 100 in java upgrade program management
    ACTIVATE_CURRENT_USAGES
    i am unable to track the cause.......
    log file is shown below
    kindly help......
    its urgent
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\jupgrade\log\ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!PATTERN[ACTIVATE_CURRENT_USAGES_ACU_07.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC1908C2000000000029014A8CD1000432D6B5DD7008#1181797662421#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:713)#Java###Phase has been started.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002A014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:714)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask#
    #1.5#C000AC1908C200000000002B014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#inputFile#ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002C014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:338)#Java###  Parameter =#2#taskName#ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000002D014A8CD1000432D6B5DDAE88#1181797662437#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.checkParameters(PhaseTypeExecuteTask.java:191)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
    #1.5#C000AC1908C200000000002E014A8CD1000432D6B5F009C0#1181797663640#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C200000000002F014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildConfiguration(ConfigurationBuilder.java:297)#Java###Configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks_WIN.xml#
    #1.5#C000AC1908C2000000000030014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.cfg.ConfigurationBuilder.buildGlobalConfiguration(ConfigurationBuilder.java:251)#Java###Global configuration has been built from input file .#1#D:/usr/sap/jupgrade/config/ExecuteTasks.xml#
    #1.5#C000AC1908C2000000000031014A8CD1000432D6B5F13A70#1181797663718#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#2#com.sap.engine.offline.OfflineToolStart#
    #1.5#C000AC1908C2000000000032014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2#  #C:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true#
    #1.5#C000AC1908C2000000000033014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2#  #D:
    usr
    sap
    jupgrade
    log
    ACTIVATE_USAGE_AS_ACU_01.OUT#
    #1.5#C000AC1908C2000000000034014A8CD1000432D6B5F178F0#1181797663734#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#2#
    #1.5#C000AC1908C2000000000035014A8CD1000432D6B5F1B770#1181797663750#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#2#java.exe#
    #1.5#C000AC1908C2000000000036014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#2#java.exe#64#
    #1.5#C000AC1908C2000000000037014A8CD1000432D6B6B9BE78#1181797676859#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:735)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC1908C2000000000038014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.generateResultProcessingException(AbstractExtProcessOperation.java:579)#Java###Could not activate usage AS. Could not execute 'C:
    j2sdk1.4.2_09
    jre
    bin
    java.exe -cp d:/usr/sap/W60/SYS/global/sltools/sharedlib/launcher.jar;d:/usr/sap/W60/SYS/global/sltools/sharedlib; com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain d:/usr/sap/W60/SYS/global/sltools/sharedlib;D:/usr/sap/W60/SYS/global/security/lib/tools;D:/usr/sap/w60/jc00/exe/classes12.jar -activated -sid=W60 -dsn=jdbc/pool/W60 -ssprops=D:/usr/sap/W60/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/W60/SYS/global/security/data/SecStore.key -log=D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS.LOG -prod_name=NetWeaver -usage_name=AS -usage_vendor=sap.com -action=true', return code '64'. You can check the file(s) 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.OUT', 'D:
    usr
    sap
    jupgrade
    log/ACTIVATE_USAGE_AS_ACU.ERR' to which the output of the process has been redirected.##
    #1.5#C000AC1908C2000000000039014A8CD1000432D6B6B9FCF8#1181797676875#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.execute.AbstractExtProcessOperation.execute(AbstractExtProcessOperation.java:176)#Java###Error while processing the result.##
    #1.5#C000AC1908C200000000003A014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.PhaseTypeExecuteTask.execute(PhaseTypeExecuteTask.java:173)#Java###Error while executing PhaseTypeExecuteTask with input file ExecuteTasks.xml and task ACTIVATE_CURRENT_USAGES.##
    #1.5#C000AC1908C200000000003B014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:779)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES#
    #1.5#C000AC1908C200000000003C014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:780)#Java###Start time: .#1#2007/06/14 10:37:42#
    #1.5#C000AC1908C200000000003D014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:781)#Java###End time: .#1#2007/06/14 10:37:56#
    #1.5#C000AC1908C200000000003E014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:782)#Java###Duration: .#1#0:00:14.453#
    #1.5#C000AC1908C200000000003F014A8CD1000432D6B6BA3790#1181797676890#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/ACTIVATE_CURRENT_USAGES##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:783)#Java###Phase status is .#1#error#
    waiting for solution
    thankx in advance....
    shoeb

    Could you please share us the solution?

Maybe you are looking for

  • HELP! - Getting RAW footage into Offline RT jpeg project

    I hoping someone can write down a brief explanation of the steps needed to do this final step in the edit process. I imported all my footage as an Offline RT jpeg format so it wouldn't take up so much space on the HD. Now I'm completely finished edit

  • Can't get my Ipod to connect to the Wifi?

    Never had this issue before it has always connected fine. Now all of a sudden I can't get it to connect at all. I have reset the network and went through all the steps and still nothing. Everything else connects to the wifi such as computer, kindles,

  • Lp - problems with multiple files ?

    Does anyone know of or have experienced problems with the lp command and multiple files on Solaris 5.6?. Currently when trying to print issuing one lp command for 164 files from within a script i.e lp file1 file2 file3..... file164, a request id is r

  • Where can I get Concerts to view on my I-touch

    Anyone know where I can download concerts to view on my I-touch? Peace..

  • Print problem with InDesign CS5 and Power RIP-X

    When I try to print an InDesign page using PowerRIP I get a big X across the page that is not in the document. Any ideas as to why and how I can fix this?