NW2004s Upgrade

All ,
I need some user experiences / advice from all regarding the NW04s SR1 upgrade .
1) We are in the blue print phase of an ESS / MSS / LSO implementation through NW04s SR1  with EP7.0 .SO is there any risk in upgrading right now or is it advisable after going live ( we are going live in couple of months ).Let me know what is the best practice .
2) Also share any specific problems faced during the upgrade from NW04s SR1 ( SP 6) to SP 8 .
Pls share your thoughts
Aneez

COuld any one share their thoughts
Aneez

Similar Messages

  • NW2004s Upgrade Project Plan

    Hello Gurus,
    Need to make an Excel/ MS Project based NW2004s Upgrade Project Plan, which covers all major activities with approximate durations.
    I understand, it will largely depend on any customer's specific landscape, yet assuming some existing BW version, R/3, EP, CRM and non-SAP systems in any landscape, there can be a fairly common 'template' for making such plan.
    Can somebody guide on where such a plan can be found?
    Regards
    Manish Madhav

    Hi,
    There are some documents like
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b4f8c290-0201-0010-8695-95342ff06094
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1094f43d-20c1-2910-c08c-928cecc93e04
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6b87e090-0201-0010-e1ad-ca4d412e6535
    /people/tommy.alexander4/blog/2007/04/15/planning-for-a-combined-sap-upgrade-and-technology-refresh
    but not an XLS template
    Eddy
    PS. Reward useful answers and earn points yourself

  • "In process" version of All data targets after NW2004s upgrade

    Hi All,
    After upgrade to NW2004s, all of data targets are showing in "In Process" version.
    Datas are getting loaded successfully and reports are working fine.
    Why this is that??
    Full Points will be awarded.
    Thanks,
    Harry

    Hi Harry,
    'In Process' =  New.
    To Make the 'In Process' to 'Active'
    -->Double click on 'In Process (Func.)' and select 'Active'.
    -->Then you will see only Active Version.But it is not harm if you keep Version as 'In Process' .You can see Revised version as 'Active' right.
    The main difference between 'In Procee' and 'Active' is, both are same. But 'In process' means New Active version.
    -Sreekanth

  • BI NW2004s Upgrade Question

    Hello All,
    We recently upgraded our BI systm to NW 2004s. It was a pure technical upgrade with only ABAP stack. We have not migrated into the new functionality and we are just using the old functionality. I have a few questions on adding other components to our system like BI java portal etc. We do not use EP.
    1.  We would want to add BI java and portal components we have a three syetem landscape Dev, Test and Prod. Our intention is to use the BI portal which comes with BI java and EP components automatically. so do we have to install the BI java and EP components on each of the three sytems? or
    2.  Can we  install BI java and EP components  on a standalone server and tie our Dev, test and Prod to that portal?
    I would apprecaite your response.
    Thanks in advance
    D!!!!

    1)Each NetWeaver 7.0 (2004s) BI system needs its own BI Java usage type which again needs its own Enterprise Portal usage type. That means you can bring different BI systems together in one overall NetWeaver 7.0 (2004s) or 6.0 EP but technically each NetWeaver 7.0 (2004s) BI instance also has its own EP installed underneath for technical reasons. For endusers of course you bring it all together in one Enterprise Portal on top .
    2)This depends on the expected load on SAP NetWeaver Portal and on the existing system landscape:
    One server, if the BI system only uses types AS-ABAP and AS-Java on one server.
    Two servers, if the BI system and SAP NetWeaver Portal (used as Enterprise Portal) use usage types AS-ABAP and AS-Java on two separate servers.
    Hope it Helps
    Chetan
    @CP..

  • Trex Installation  in Nw2004s upgradation

    Hi all,
    We have recently upgraded from Ep 6.0 to Nw 2004s , In EP 6.0 we don't have  Trex and we want to  activate during upgrade , but we didn't found   during upgrade.
    How to Activate it now.

    Hi Subash,
    refer these links
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fd472c46-0a01-0010-f8b8-ac1b1de8a6f0
    /thread/69267 [original link is broken]
    /thread/87836 [original link is broken]
    Configuring Trex Search in KM-Portal
    Regards,
    Tamil K

  • JPREPARE not found, to do Portal upgrade to NW2004S

    Hi all
    I am trying to upgrade Enterprise Portal EP6SP17 (NW2004) to  NW2004S-SR1 on HP-UX-PARISC-64bit/Oracle following the instructions in the Upgrade guide for 'Netweaver 2004S Java'. 
    On Page no.28 it is mentioned to start JPREPARE to prepare and verify the system for upgrade.  I could not locate the executable JPREPARE on  'NW2004s upgrade Master' CD.
    Has anyone faced the same problem in locating  JPREPARE on the media? If yes, on which DVD they found this executable? I look for feedback from anyone who did NW2004 to NW2004S Portal upgrade on any platform.
    Thanks in advance....
    Nagesh

    Thanks Siva,
    That worked too.  I was trying to run 'startserver' first before running 'startgui' and getting a different error message. But that is not required.
    For the benefit of others I am writing down the steps here:
    From the /usr/sap/jupgrade folder:
    1. Run ./PREPARE and leave it running.
    2. Run ./startgui  (from a different unix session)
    to be able to run PREPARE successfully.
    Nagesh

  • Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE

    Hello Expert,
    I have a problem when a try to execute the upgrade in the phase
    DEPLOY_ONLINE,
    <<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
    Trouble Ticket Report
    Upgrade to SAP NetWeaver'04s
    SID................: J2E
    Hostname...........: sapepd
    Install directory..: d:/usr/sap/J2E
    Upgrade directory..: D:\SAPEPD\saploc\jupgrade
    Database...........: Microsoft SQL Server
    Operating System...: NT
    JDK version........: 1.4.2_11 Sun Microsystems Inc.
    SAPJup version.....: 1.1.101
    Source release.....: 630
    Target release.....: 700
    Current usages.....: EP;AS;DI
    ABAP stack present.: false
    The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
    Error while executing SDM process phase with action DEPLOY_SLOT. See
    D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
    Cannot execute Java process for deployList with parameters
    D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.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
    D:\SAPEPD\saploc\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
    D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
    DEPLOY_ONLINE
    UPGRADE
    NetWeaver Upgrade
    SAPJup
    Java Upgrade
    <<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
    THE FILE: DEPLOY_ONLINE_DON_01.LOG
    BEGIN DEPLOY_ONLINE_DON_01.LOG----
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
    <!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
    #1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
    #1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#action#DEPLOY_SLOT#
    #1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#connect#standard#
    #1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
    #1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
    #1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
    #1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
    #1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##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:
    j2sdk
    jre
    bin
    java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
    usr
    sap
    J2E
    JC00
    SDM
    program
    bin
    SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.LOG#
    #1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##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:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.OUT#
    #1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
    #1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
    #1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
    #1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
    #1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
    #1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.LOG for details.##
    #1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
    #1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
    #1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
    #1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
    #1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    *************END  DEPLOY_ONLINE_DON_01.LOG*******************
    FILE ************** DEPLOY_SLOT_0__DON_01.LOG
    BEGIN  DEPLOY_SLOT_0__DON_01.LOG----
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:33 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:33 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:33 PM  Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:33 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
    Jul 18, 2007 3:18:33 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:33 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:36 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:33 -  ***********************************************************
    07/07/18 15:18:34 -  Start updating EAR file...
    07/07/18 15:18:34 -  start-up mode is lazy
    07/07/18 15:18:34 -  EAR file updated successfully for 172ms.
    07/07/18 15:18:34 -  Start deploying ...
    07/07/18 15:18:34 -  EAR file uploaded to server for 500ms.
    07/07/18 15:18:36 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
                         Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
                              com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    07/07/18 15:18:36 -  ***********************************************************
    Jul 18, 2007 3:18:36 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:36 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:36 PM  Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
    Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 18, 2007 3:18:36 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:36 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:36 PM  Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
    Jul 18, 2007 3:18:36 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
    Jul 18, 2007 3:18:36 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:36 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:39 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:36 -  ***********************************************************
    07/07/18 15:18:36 -  Start updating EAR file...
    07/07/18 15:18:36 -  start-up mode is lazy
    07/07/18 15:18:37 -  EAR file updated successfully for 375ms.
    07/07/18 15:18:37 -  Start updating...
    07/07/18 15:18:37 -  EAR file uploaded to server for 422ms.
    07/07/18 15:18:39 -  Successfully updated. Update took 1641ms.
    07/07/18 15:18:39 -  Deploy Service status:
    07/07/18 15:18:39 -    Application : sap.com/tcwdtools
    07/07/18 15:18:39 -   
    07/07/18 15:18:39 -    sap.com/tcwdtools  - WEBDYNPRO
    07/07/18 15:18:39 -    sap.com/tcwdtools monitoring configuration  - MONITORING CONFIGURATION
    07/07/18 15:18:39 -  ***********************************************************
    Jul 18, 2007 3:18:39 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:39 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:39 PM  Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:39 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:40 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:40 PM  Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
    Jul 18, 2007 3:18:40 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
    Jul 18, 2007 3:18:40 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:40 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:40 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:40 -  ***********************************************************
    07/07/18 15:18:40 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
    07/07/18 15:18:40 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
    Jul 18, 2007 3:18:40 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:40 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:40 PM  Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
    Jul 18, 2007 3:18:40 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:41 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:41 PM  Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:41 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
    Jul 18, 2007 3:18:41 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:41 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:49 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:41 -  ***********************************************************
    07/07/18 15:18:41 -  Start updating EAR file...
    07/07/18 15:18:41 -  start-up mode is lazy
    07/07/18 15:18:42 -  EAR file updated successfully for 1000ms.
    07/07/18 15:18:42 -  Start deploying ...
    07/07/18 15:18:43 -  EAR file uploaded to server for 891ms.
    07/07/18 15:18:48 -  Successfully deployed. Deployment took 5375ms.
    07/07/18 15:18:48 -    Application : sap.com/tc~workflowmodeler
    07/07/18 15:18:48 -   
    07/07/18 15:18:48 -    /Application/WorkflowModeler  - LOGGING CONFIGURATION
    07/07/18 15:18:48 -    com.sap.workflowmodeler.modeler  - LOGGING CONFIGURATION
    07/07/18 15:18:48 -    workflowBean  - EJB
    07/07/18 15:18:48 -    WorkflowConnection  - EJB
    07/07/18 15:18:48 -    Modeler  - WEB
    07/07/18 15:18:48 -    sap.com/tc~workflowmodeler monitoring configuration  - MONITORING CONFIGURATION
    07/07/18 15:18:48 -  ***********************************************************
    Jul 18, 2007 3:18:49 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:49 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:49 PM  Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:49 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:49 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:49 PM  Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
    Jul 18, 2007 3:18:49 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
    Jul 18, 2007 3:18:49 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:49 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:49 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:49 -  ***********************************************************
    07/07/18 15:18:49 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
    07/07/18 15:18:49 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
    Jul 18, 2007 3:18:49 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:49 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
    Jul 18, 2007 3:18:50 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:50 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:50 PM  Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
    Jul 18, 2007 3:18:50 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
    Jul 18, 2007 3:18:50 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:50 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:50 -  ***********************************************************
    07/07/18 15:18:50 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
    07/07/18 15:18:50 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
    Jul 18, 2007 3:18:50 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:50 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
    Jul 18, 2007 3:18:50 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:51 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:51 PM  Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:51 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
    Jul 18, 2007 3:18:51 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:51 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:52 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:51 -  ***********************************************************
    07/07/18 15:18:51 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
    07/07/18 15:18:52 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
    Jul 18, 2007 3:18:52 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:52 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:52 PM  Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
    Jul 18, 2007 3:18:52 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:52 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:52 PM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
    Jul 18, 2007 3:18:52 PM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    Failed deployment of SDAs:
    development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
    Please, look at error logs above for more information!
    Jul 18, 2007 3:18:52 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:52 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:52 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 18, 2007 3:18:52 PM  Error: -
    At least one of the Deployments failed -
    Jul 18, 2007 3:18:53 PM  Info: Summarizing the deployment results:
    Jul 18, 2007 3:18:53 PM  Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
    Jul 18, 2007 3:18:53 PM  Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
    Jul 18, 2007 3:18:53 PM  Error: Processing error. Return code: 4
    END  DEPLOY_SLOT_0__DON_01.LOG----
    I SAW the SDN forum and talk about the question
    Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
    but this one doesnu00B4t work
    best regards
    Luis Moreno

    Hi
    I resolved the issue by undeploying the TestSuiteUUIE  component using SDM.
    Thanks
    Naresh P.

  • Upgrade Ep6 to NW04s portal - deploy error

    I am upgrading our EP 6 system to NW04s w/Portal. Java AS only. No ABAP. In the DEPLOY_ONLINE phase it is stopping after about 2 hours.
    When I restart it, from the logs it appears to be restarting from the beginning instead of where it stopped. But I can't find the true cause of why it's stopping in the first place.
    My arch logs are not full and my tablespaces are ok, so the DB didn't fill up with anything more than it should.
    The logs show that most items were deployed, even though with warnings.  2 errored out, although I can't find why in the detailed logs:
    Aug 4, 2006 12:10:42 PM  Info: Summarizing the deployment results:
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ADSSAP08_0-10003001.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIIBC06_0.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/BIWEBAPP06_1.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIMMR08_0-10002782.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BIUDI08_0-10002781.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5***03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUA03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5BUY02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5COM02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5DCO02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5ESS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5HRA03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5INV02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5MTC02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PLA02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PRS02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5PSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5QIN02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SAL02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/BPERP5SUP02_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAF08_0-10003464.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFKM08_0-10003478.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/CAFUM08_0-10003472.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPPSERV08_0-10003474.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPWDC08_0-10003557.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/EPBC208_0-10003489.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/FSCMBD03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/ISHERCSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMKWJIKS08_0-10003021.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCBC08_0-10003491.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCM08_0-10003492.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/KMCCOLL08_0-10003493.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMPORTAL08_0-10003487.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/LMTOOLS08_0-10003486.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/NETPDK08_0-10003351.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/RTC08_0-10003494.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/RTCSTREAM08_0-10003488.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPCRMDIC03_0.sca
    Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPEU08_0-10003026.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPCUIGP03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPASR03_0.sca
    Aug 4, 2006 12:10:42 PM  Error: Aborted: /usr/sap/put/PD1upg/data/archives/SAPESS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPMSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/SAPPSS03_0.sca
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UMEADMIN08_0-10003471.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/UWLJWF08_0-10003490.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCBASE08_0-10003602.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCFLEX08_0-10003616.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/VCFRAMEWORK08_0-10003624.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITGP08_0-10003617.SCA
    Aug 4, 2006 12:10:42 PM  Info: OK: /usr/sap/put/PD1upg/data/archives/VCKITXX08_0-10003615.SCA
    Aug 4, 2006 12:10:42 PM  Warning: Warning: /usr/sap/put/PD1upg/data/archives/WDEXTENSIONS08_0-10003618.SCA
    Aug 4, 2006 12:10:42 PM  Error: Processing error. Return code: 4

    Hello,
    We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
    We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already? 
    Is this a bad support package that SAP released?

  • BW Upgradation Project from BW 3.5 t o BI 7.0

    Dear SDNS,
                             We got an requirement to do an upgradation project for BW 3.5 to BI 7.0... This is the first time am involving for Upgradation..Am An BW Technical Consultant.. Can anyone one sugggest at scratch level wat are the roles should play by BW Technical consultant.. And Wat are the activities whould done by BW technical consultant.. An can anyone tell me.. How many SAP Consultants should involve in this Project.. i.e like how many Basis Consultants and how many ABAP Consultants should involve.. Who plays the Vital Role for Upgradation...
    Can anyone send me the Documents Related for BIW Upgradation for BW 3.5 to BI 7.0.. If anyone send me screen shots related to BW Tehcnical Consultant work it would be helpful.....
    My E-Mail - [email protected]
    Answering Getz Appreciated,
    Thanks & Regards,
    Aluri

    Hi
    I have some checklist ,do not exactly remember from where i got it but its really usefull
    There is no standard SAP checklist as it used to exist in 3.x for nw2004s upgrade and trust the master data guide available on market place is not upto the mark and expectations
    So Heads up..
    /message/2979584#2979584 [original link is broken]
    /message/2765713#2765713 [original link is broken]
    /message/2979576#2979576 [original link is broken]
    /message/3214476#3214476 [original link is broken]
    /message/3024448#3024448 [original link is broken]
    You may wish to have a look at draft portrayed below,rest you learn when you drive
    Lessons Learnt - Upgrade
    1)Convert Data Classes of InfoCubes. Set up a new data class as described in SAP OSS Note 46272.
    2)Pay attention to the naming convention. Execute the RSDG_DATCLS_ASSIGN report.
    3)Run the report RSUPGRCHECK to activate objects.
    4)Upgrading ABAP and JAVA in parallel may cause issues. If there is no custom development on J2EE instance, it is recommended to drop the J2EE instance and re-install the latest J2EE instance after the upgrade.
    5)Apply SAP OSS Note 917999 if you include the Support Patch 6 with the upgrade or you will get the error at PARCONV_UPG phase. When you upgrade to a product containing Basis 700, the phase PARCONV_UPG terminates. You included Basis Support Packages up to package level 6 (SAPKB70006) in the upgrade. The job RDDGENBB_n terminates with the error RAISE_EXCEPTION. In addition to this, the syslog contains the short dump TSV_TNEW_PAGE_ALLOC_FAILED. The program SDB2FORA terminates in the statement "LOOP AT stmt_tab". An endless loop occurs when the system creates the database table QCM8TATOPGA.
    6)Apply the OSS note 917999 if you get the following error during PARCONV_UPG phase: PARCONV_UPG terminates with TSV_TNEW_PAGE_ALLOG_FAILED
    Critical OSS Notes:
    819655 – Add. Info: Upgrade to SAP NW 2004s ABAP Oracle
    820062 - Oracle Database 10g: Patchsets/Patches for 10.1.0
    839574 – Oracle database 10g: Stopping the CSS services ocssd.bin
    830576 – Parameter recommendations for Oracle 10g
    868681 – Oracle Database 10g: Database Release Check
    836517 – Oracle Database 10g: Environment for SAP Upgrade
    853507 – Usage Type BI for SAP Netwaevers 2004s
    847019 - BI_CONT 7.02: Installation and Upgrade Information
    818322 – Add. Info: Upgrade to SAP NW 2004s ABAP
    813658 - Repairs for upgrades to products based on SAP NW 2004s AS
    855382 – Upgrade to SAP SEM 6.0
    852008 – Release restrictions for SAP Netweaver 2004s
    884678 - System info shows older release than the deployed one
    558197 – Upgrade hangs in PARCONV_UPG
    632429 – The upgrade strategy for the add-on BI_CONT
    632429 - The upgrade strategy for the add-on FINBASIS
    570810 - The upgrade strategy for the add-on PI_BASIS
    632429 - The upgrade strategy for the add-on SEM-BW
    069455 - The upgrade strategy for the add-on ST-A/PI
    606041 - The upgrade strategy for the add-on ST-PI
    632429 - The upgrade strategy for the add-on WP-PI
    Post upgrade Steps :-
    1. Read the Post Installation Steps documented in BW Component Upgrade Guide
    2. Apply the following SAP OSS Notes
    47019 - BI_CONT 7.02: Installation and Upgrade
    558197 - upgrade hangs in PARCONV_UPG, XPRAS_UPG, SHADOW_IMPORT_UPG2
    836517 – Oracle Database 10g: Environment for SAP Upgrade
    3. Install the J2EE instance as Add-in to ABAP for BI 7.0 and apply the Support Patch that equivalent to ABAP Support Patch.
    4. Run SGEN to recompile programs.
    5. Install the Kernel Patch.
    6. Missing Variants - (also part of test script)
    look at the RSRVARIANT table in SE16. If it is empty, then you will definitely need to run RSR_VARIANT_XPRA
    program - RSR_VARINT_XPRA
    OSS -953346 and 960206 1003481
    7. Trouble Shootauthorizations
    820183 - New authorization concept in BI
    I think the above material is sufficient but in case you face any issues feel free to revert back
    Reward suiatble points

  • Documentation for Upgrading the Roles/Authorisatiosn

    Hi,
    I have upgraded my BW 3.5 system to BW 7.0(NW2004 to NW2004s Upgrade)
    Please let me know the link where i can get the documentation for the following activities
    1. Generatin of Roles/Authorisation --The document which tell me teh step by step activites of changing the authorisations for the new System
    2. Converting the objects in Bw 3.5 to 7.0 --Like changing the Infocubes, infoobjects to Version 7.0

    Hi,
    Check in this link:
    http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
    For alerts refer this:
    The following predefined user roles are available for customizing and administration:
    • SAP_BC_ALM_CUST for customizing authorization.
    • SAP_BC_ALM_ADMIN for administration authorization. The administrator has the authorization for all activities. He or she can also read and confirm alerts for other users. In addition, the administrator can execute report RSALRTPROC to delete, escalate, and deliver alerts as well as to delete logs.
    • For the sending of alerts via external communication methods (e-mail, sms, fax) and for inbound processing, an RFC user has to be created on the central alert server with the role SAP_BC_ALM_ALERT_USER. The authorization objects contained in this role are S_OC_SEND and S_RFC.
    • Accessing alert inbox the userid has to have the role SAP_XI_MONITOR.
    • SAP_ALM_ADMINISTRATOR - Alert Management Administrator Give this rights
    Refer the SAP_XI_ADMI topic and see the roles.
    http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
    Refer link for user roles: http://help.sap.com/saphelp_nw2004s/helpdata/en/74/03b140ade49c2ae10000000a155106/content.htm
    Roles needed for IR and ID:
    Role: SAP_XI_Developer
    SAP_XI_DEVELOPER (Composite)
    SAP_SLD_DEVELOPER
    SAP_XI_DEMOAPP
    SAP_XI_DEVELOPER_ABAP
    SAP_XI_DEVELOPER_J2EE
    Role: SAP_XI_Configurator
    SAP_XI_CONFIGURATOR (Composite)
    SAP_SLD_CONFIGURATOR
    SAP_XI_BPE_CONFIGURATOR_ABAP
    SAP_XI_CONFIGURATOR_ABAP
    SAP_XI_CONFIGURATOR_J2EE
    SAP_XI_DEMOAPP
    Regards,
    Nithiyanandam
    Edited by: Nithiyanandam A.U. on Feb 18, 2008 2:31 PM

  • Upgrade NW 2004 - 2004s

    1. We are currently working with ECC50 - NW2004 but we would like to upgrade to NW2004s to be able to use new features like Web Dynpro for ABAP and Guided Procedures in ECC50. I already found detailed upgrade information but I would like to get a feel for the amount of time it will take to get a NW2004 -> NW2004S upgrade project completed successfully. Can it be compared with an upgrade like 4.6C -> ECC50? If you take installation, regression testing, user acceptance testing etc. into account: do we talk about days, weeks or months?
    2. Is there a way to keep ECC50 - NW2004 (application server) as is but install NW2004S in a way that we can use it in ECC50?
    kind regards,
    Angelique Heutinck
    [email protected]

    We will start developing an offline Adobe interactive form with email functionality for ECC 5 on very short terms. We have to decide asap what client/server configuration we will use for this new functionality. We will also develop an online interactive form and an offline form with upload/download functionality for ECC 5. We will have to setup a client/server configuration that supports all 3 scenario's. 
    The main reason we would like to have NW2004S available for ECC 5 is because we would like to develop the forms in Web Dynpro ABAP instead of Java. Guided Procedures is a "nice to have" too, but not really important at this moment.
    At this moment we think we have 3 options:
    1. Investigate if we can make an Adobe solution in WDA for ECC 5 with our current setup
    2. Upgrade ECC 5 - NW 2004 -> NW 2004S to get WDA functionality available
    3. Install ADS for NW 2004 to be able to create Adobe solutions in ECC 5, then we will have to develop in WDJ
    1. We have the following configuration up and running: NW2004S - CRM 5 and ADS installed: both Java and ABAP stack work properly. We are wondering if we could develop an Adobe interactive form in Web Dynpro ABAP in CRM 5 using BAPI's to retrieve the data from ECC 5 and put it on the form for display or update purposes. Also we have questions about the email functionality: do forms have to be send by email via a mailserver from ECC 5 via CRM 5 and back or can this be done directly from and to ECC 5 or is it not possible at all? Also we don't know if we can develop an online interactive form for ECC 5 via CRM 5. The current setup is not a real option for us right now as we see far too many uncertainties. Does somebody can give us some answers on the possibilities we are looking for?
    2. My assumption is that upgrading ECC5 to ECC6 can be compared with upgrading 46C to ECC5. If my assumption is correct, this would mean an upgrade project with a 6 months leadtime within our company. If my assumption is wrong, please let me know. This upgrade will happen some day, but it has not been planned for 2007. So unfortunately, for us this is not an option at the moment because we cannot wait that long. I was hoping an upgrade of NW2004 -> NW2004s was not that time consuming but I guess this can be compared with a SAP upgrade project like 46C -> ECC 5.
    3. Installing Adobe Document Services for NW2004 is not our preferred solution but we think it is the safest/easiest solution at this moment to get started with Adobe interactive forms for ECC 5 on short terms. We will have to develop in Web Dynpro for Java, so be it.
    WDA is not a must but if we can find a client/server setup which gives us the possibility to build in WDA for ECC 5 functionality, that would be great. That's why I dropped the question on SDN. I want to be sure we choose the best option possible at this moment for us.
    kind regards
    Angelique

  • BI7 Upgrade - Data Classes and Unicode Conversion

    It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
    NW2004s upgrade
    Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
    Please advice.

    It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
    NW2004s upgrade
    Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
    Please advice.

  • What is Analysis Authorizations in BI 7.0?

    Hello BW Gurus,
    Greetings!!!!
    Please forward the relevant documents (<b>Analysis Authorizations and also about data migration from 3.0 to 7.0</b> ) to the ID- <b>[email protected]</b>
    Points will be rewarded..
    Best Regards,
    Priya

    Hi Priya,
    These would be great help to you,
    Upgrading to SAP NetWeaver 7.0 BI - The Details doc.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
    Please check these blogs for full details:
    /people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools?page=last&x-showcontent=off&x-order=date [original link is broken]
    https://weblogs.sdn.sap.com/pub/wlg/4668?page=last&x-order=date [original link is broken] [original link is broken] [original link is broken]
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6a19f233-0e01-0010-6593-c47af5a8df3b
    Some Insights..
    NW2004s Upgrade - Front-End Migration Strategy
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=2331907
    Migration of Data Sources
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=3369391
    Migration - Web Templates from 3.x to NW2004s
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=2052465
    Migration question
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=2935414
    Migration Transformation NW2004s Datasource
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=3034054
    Analysis Authorization Migration Question
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=2537477
    NW2004s Data flow
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=3447826
    Visual composer migration
    https://forums.sdn.sap.com/click.jspa?searchID=3914335&messageID=3775098
    Rfer thez threads.. u will get good idea..
    /thread/439486 [original link is broken]
    /thread/377643 [original link is broken]
    Migrate Transformations
    /message/3034624#3034624 [original link is broken]
    /thread/178564 [original link is broken]
    For Data Flow:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/f00e2696d24c5fe10000000a155369/content.htm
    /people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools
    Assign points if it helps,
    Regards,
    Mani

  • BW-BPS Functionalities!

    Can anyone tell me if we still have the missing functions which are part of SEM-BPS are not included in BW-BPS (NW2004s)
    Offsetting Entry
    Accumulate Balances
    Depreciation
    Net Present Value
    Internal Rate of Return
    Time Lag Functions
    Valuation
    Allocation
    Rounding
    Currency Translation (Account-Based)
    Thanks in Advance,

    Hello bw expert online,
    referring to this question see the answer from Mary Huang to your other thread here: Re: SEM Upgrade and NW2004s Upgrade.
    Regards
    ML

  • Weblogic jsf portal deploy error

    Hello, I am trying to deploy a JSF Portlet. After some time i managed to reach where i get this error when i am loading the portlet in browser.
    >
    <28.02.2008 17:07:20 EET> <BEA-101214> <Included resource or file "/portal/framework/skeletons/portal
    al/gridlayout.jsp" not found from requested resource "/portal/Portal.portal".>

    Hello,
    We are having the exact same issue when DEPLOY_ONLINE encounters WDEXTENSIONS08_0-10003618.SCA as part of the NW2004s upgrade process.
    We just submitted an OSS message to SAP about it --- but I am wondering if you have received a solution already? 
    Is this a bad support package that SAP released?

Maybe you are looking for

  • Adding multiple items at once to a SharedCollection

    I'm playing around with Cocomo for the first time. I like it a lot, but haven't yet got enough understanding of the API. So I'm sure I'm missing something obvious. Anyway. I want to build an application that share an array of items between clients. T

  • Can I purchase an iphone3g and then use it with the apple golf app as a golf gps without having to be on a cell plan or data plan?

    If I purchase an iPhone 3g, can I then use it with the apple golf app without having cell or data service?

  • Hard disk does not show in finder

    WE had a system failure with our server instance a month back and since then, one of my internal HD's will not show in finder. It's also causing carbon copy pro to fail when trying to find it. I have verified it can be seen in the disk utility and fr

  • Include html content in jsp

    Hi , I have the html data and need to include in the jsp . eg : String htmldata = " <html><body>testdata </body></html>"; how can i display this htmldata in the jsp . I mean I need this data in html format ( testdata ) and should not see all html tag

  • Testing

    Hi SAP guru, Can u please help me in knowing the testing of following scenarios. 1.IDOC to file scenario 2.File to HTTP Thanks & Regards Vijaya