Netweaver upgrade

Hello everybody, how you doing?
i wish you can help me out...or maybe clear my concerns....well this is the fact.
we're running SAP 6.0 we have 3 servers, productive, quality and development...and we're running netweaver 7.00 Lv. 22
we're trying to upgrade SQL 2005 to 2008... and I have been requested to upgrade our netweaver version to 7.01 maybebut can't figure out how to...
i have been rolling over the MP and found on the download area there was netweaver 7.0 and 7.3 is is possible to go from .1 to .3 ??
are there any restrictions or thing i must be aware of??
sorry if I ask to much in one post, but I'm new into this basis thing..so I'll keep asking if you don't mind

Diego thanks for the response...i have reviewed the note and as far as I understand we have netweaver 7.0 SR3
as the note says SR3 contains:
SAP_BASIS 700 Lv14
SAP_ABA 700 Lv14
SAP_BW 700 Lv14
PI_BASIS 700 Lv16
and I have installed on my system
SAP_BASIS 700 Lv22
SAP_ABA 700 Lv22
SAP_BW 700 Lv24
PI_BASIS 700 Lv22
am I right??
sorry for such silly questions, but I am still learning and I need to be sure of what I am learning

Similar Messages

Phase list of Netweaver upgrade 7.0 EHP2

Hi guys,
Kindly please help me provide the phase list of the Netweaver upgrade 7.0 to EHP2. Or on what link can i see those list?
Thank you very much and have a good day ahead.
JAV

I suggest you start reading the EHP2 upgrade guide:
http://service.sap.com/instguides
--> SAP NetWeaver
--> SAP NetWeaver 7.0 (2004s)
--> Maintenance
-- Update EHP (on the very bottom
Phase list should look like below...
Initialization
Extraction
Configuration
Checks
PreProcessing
DownTime
PostProcessing
Finalization

About netweaver upgrade

Hi :
     sap ehp1 for netweaver ce 7.1 : 7.11.5
     oracle vm box : 4.1.4
     xp sp2
     After I upgrade the file "J2EEFRMW08_0-20002637.SCA" , the Application [sap.com/tcwddispwda] cannot be started.
The IE shows error msg.
I can't log in the netweaver.
Error: Application cannot be started!
Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/tc~wd~dispwda] cannot be started. Reason: it has hard reference to resource [tc~wd~webdynpro] with type [service], which is not active on the server.
Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
     at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToService(ReferenceResolver.java:717)
     at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:572)
     at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
     at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:467)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:560)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:551)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:183)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:296)
     at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:353)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:159)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.frame.ServiceException: com/sap/engine/services/webservices/espbase/server/runtime/metering/ServiceMeter
     at com.sap.engine.core.service630.container.ServiceRunner.startSingleService(ServiceRunner.java:90)
     at com.sap.engine.core.service630.container.MemoryContainer.startServiceRuntime(MemoryContainer.java:762)
     at com.sap.engine.core.service630.container.MemoryContainer.startServiceRuntime(MemoryContainer.java:744)
     at com.sap.engine.core.service630.container.MemoryContainer.startServiceRuntime(MemoryContainer.java:737)
     at com.sap.engine.core.service630.container.MemoryContainer.startServiceRuntime(MemoryContainer.java:737)
     at com.sap.engine.core.service630.container.SystemThreadProcessor.run(SystemThreadProcessor.java:87)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: java.lang.NoClassDefFoundError: com/sap/engine/services/webservices/espbase/server/runtime/metering/ServiceMeter
     at com.sap.engine.services.webservices.server.WebServicesFrame.initWSJndiContexts(WebServicesFrame.java:439)
     at com.sap.engine.services.webservices.server.WebServicesFrame.start(WebServicesFrame.java:139)
     at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
     at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
     at com.sap.engine.core.service630.container.ServiceRunner.startSingleService(ServiceRunner.java:78)
     ... 8 more

sap ehp1 for netweaver ce 7.1 : 7.11.8

NetWeaver JavaStack - NetWeaver Upgrade Question

Hello Gurus,
Please ignore I sound little uninitiated in this.
This is about the so called JavaStack upgrade after (?) the technical upgrade.
- What exactly is the so called Javastack in netweaver? It is not same as 'Usage Type' Java? Is this AS Java?
- What is the right time to do the JavaStack Upgrade? After technical upgrade?
- How much after tech upgrade? 2-3 weeks are ok? Will the new features of BI 7 not be available till we upgrade the javastack?
- Without upgrdaing to Javastack, will NONE of the new functionalities be available in BI 7.0?
Please help.
Regards
Manish Madhav

In continuation
To use any web based components, including the 2004s Web Application Designer, Report Designer, or Web Analyzer, you need to have BI-JAVA usage type installed.
You can still use the 2004s BEx Analyzer (Excel) without the BI-JAVA usage type.
When you install BI JAVA, it will have its own EP and AS JAVA usage types under it. You have no option with this as they are required to run BI JAVA (just like you have AS ABAP under the BI usage type).
It is recommended that you have all 4 usage types installed (AS-ABAP, AS-JAVA, EP, and BI-JAVA) as this is required for full functionality. These can be on a single system or can be 2 separate systems:
1 system:
System (AS-ABAP, AS-JAVA, BI-JAVA, EP)
2 systems:
System (AS-ABAP)
System (AS-JAVA, BI-JAVA, EP)
Note 1072576 - Frequently Asked Questions: BI Java Support Packages/patches
Hope it Helps
Chetan
@CP..

SRM-MDM Netweaver Upgrade

Does anyone know of any reason why we can not upgrade Netweaver 7.0 from SP 14 to SP20 for our server running the SRM-MDM Catalog. All of the documentation states min requirements but no max.
We are currently running SRM-MDM Catalog 2.0 SP4 Patch10 on Netweaver 7.0 SP14

Hi Mike,
Kindly go trough the below link which explains the advantages of using SRM 2.0 over 1.0 vrs.
The blog also has links in between such as:
https://websmp204.sap-ag.de/instguides
which will guide you on what to follow for the upgrades.
Hope It Helped
Thanks & Regards
Simona Pinto

BPC 7.5 for Netweaver : Upgrade SP

Hi Experts,
My co nfiguration :
BPC 7.5 for NW , SP07.
WOndowns Server 2008
I would like to Upgrade my BPC component from SP07 to the last SP.
What's the process?
After upgrading to the last SP with SPAM, do I need to UJS_ACTIVATE_CONTENT again? (with clean and delete option?)
On the windows side, I think I have to uninstall and install the new version?
Regards
Chris

Hi Chris,
It wouldn't hurt to use UJS_ACTIVATE_CONTENT to clean and then activate APSHELL after you update your BPC to the latest version.
There a few things triggered by this process like Process Chains, so if you re-create APSHELL you will ensure that it is up to date and also all the new AppSets based on it.
You might face issues with a Dimension Attribute named MBR__SEQ, if for some reason your dimensions don't have it then you may run UJA_MIGRATE_MBR_SEQ to fix it.
As you are coming from SP07 I believer there will be no issues with that.
Regarding the already existent AppSets there is no need to activate them again as far as I know.
On BPC Client you may face an issue where not all languages are available to be installed, but if you alternate between steps all languages should be displayed. This issue is present on the installer of BPC Client 7.5 SP09 up to 11.
If you don't have the AntiXssLibrary 3.1 I would recommend saving it from your current installation as it is no longer available on the Microsoft download portal. You may also follow [SAP Note 1679046|https://service.sap.com/sap/support/notes/1679046] for a workaround.
Regards,
Marcelo

Netweaver Upgrade with EPHI - PostProcesing - Sintax error

HI Experts
Im using EPHI to upgrade my BI 7.0 SPS20 to BI EHP1 SPS5. After reach the POSTPROCESSING step,
the tool ask to run SPAU check on the system.
When i execute it SPAU load, but when i try to Reset to original any obj ( i have 2 reset ) the system
dumps with the following sintax error :
" Runtime Errors         SYNTAX_ERROR
Date and Time          02.10.2009 23:00:34 "
Short text :Syntax error in program "CL_I18N_BIDI==================CP"
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
      "CL_I18N_BIDI==================CP " in include
      "CL_I18N_BIDI==================CCAU " in
       line 2: A class already exists with the name "LCL_UNITTEST_I18N_BIDI".
I check the logs in .../abap/log/ for ADJ errors but all the seems to be OK (no errors or warnings).
Could you kindly give some advices, Please
Daniel
Edited by: Daniel Ayarza on Oct 3, 2009 3:38 AM

FULL DUMP
Runtime Errors         SYNTAX_ERROR
Date and Time          02.10.2009 23:00:34
Short text :Syntax error in program "CL_I18N_BIDI==================CP"
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
      "CL_I18N_BIDI==================CP " in include
      "CL_I18N_BIDI==================CCAU " in
     line 2:
"A class already exists with the name "LCL_UNITTEST_I18N_BIDI"."
The include has been created and last changed by:
     Created by: "SAP "
Last changed by: "SAP "
     Error in the ABAP Application Program
The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program
      CL_I18N_BIDI==================CP :
     "A class already exists with the name "LCL_UNITTEST_I18N_BIDI"."
Trigger Location of Runtime Error
     Program                                 CL_GUI_ALV_GRID===============CP
     Include                                 CL_GUI_ALV_GRID===============CM05S
     Row                                     1
     Module type                             (METHOD)
     Module Name                             CHECK_FOR_BIDI_FLAG
Source Code Extract
Line SourceCde
>>>>> method CHECK_FOR_BIDI_FLAG.
     2
3   check CL_I18N_BIDI=>BIDI_CTRL_CODES_ACTIVE eq abap_true.
     4
5   data: fcat type lvc_s_fcat,
     6         bidi type lvc_s_bidi_flag,
     7         ret type i.
8
9   clear mt_bidi_flag.
    10
11   loop at m_cl_variant->mt_fieldcatalog into fcat.
    12     check not fcat-dd_roll is initial.
    13
14     bidi-fieldname = fcat-fieldname.
    15     CALL METHOD cl_i18n_bidi=>get_bidi_flags
    16       EXPORTING
17         im_dtel        = fcat-dd_roll
    18       IMPORTING
19         EX_LTR_FLAG    = bidi-ltr
    20         EX_FILTER_FLAG = bidi-filter

BW Netweaver 2004 upgrade and mySAP ERP

What makes the most sense to do the BW 3.5 and BW NetWeaver upgrade before, after or at same time as the mySAP ERP upgrade

I would upgrade before or after because it's not effected to the real data, any thing goes wrong with Cubes and ODS we can reconstruct and load the data from OLTP. Performing before would give you an edge of upgrade to NW.
Key point is to make sure Plug-ins support to the BW version.

Usage type issue with PI upgrade from 7.01 to 7.11

Hi guys,
We are currently performing an upgrade on our PI system.
We are upgrading from PI 7.01 to PI 7.11 and we've come cross an issue during the prepare phase of the install.
An error has occurred during the execution of the CHECK_SUPPORTED_SOURCE_USAGES phase.
This upgrade doesn't support upgrade of sap.com/MI usage detected on the source system.
You can find more information in the log file /usr/sap/PI3/upg/java/log/CHECK_SUPPORTED_SOURCE_USAGES_SSU_01.LOG.
Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypeCheckSupportedSourceUsages com.sap.sdt.j2ee.tools.check.NegativeResultException This upgrade doesn't support upgrade of sap.com/MI usage detected on the source system. CHECK_SUPPORTED_SOURCE_USAGES INIT PREPARE NetWeaver Upgrade SAPJup Java Upgrade
When reporting problems to SAP Support, attach the trouble ticket file /usr/sap/PI3/upg/java/log/TroubleTicket_01.txt to your message.
We've looked through the main upgrade notes and they mention which usage types are supported, but they do not mention explicity what usage are not supported, and how to proceed with the upgrade if your system does have one of these non-supported usage types.
Considering our system does contain usage type MI, does this mean that we cannot upgrade our current PI system to 7.11?
Please help!
Thanks,
Steph

Hello
Please see note #1247043 Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1 - section "Upgrade: source system must be a dedicated PI system".
It is not possible to upgrade an existing system with the usage type MI. Even if you delete the usage type MI (if this is possible) the upgrade will not be possible.
Regards
Mark

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.

Difference between NetWeaver 2004 and NetWeaver 7.0 or 7.1

I am little confused and curious to know the recent changes happening in SAP.
Can you please tell me the differences between NetWeaver 2004 and NetWeaver 7.0 or 7.1
NetWeaver 2004 is named because SAP has released it in 2004
and then we have XI 3.0, XI.7.0(that is PI right) , EP6.0 etc as individual components have different versions released in NewtWeaver suite.
But what is this NetWeaver 7.0.
We have EE5 or ECC6 and WebAs 6.4 or GUI 6.4 or recently GUI 7.o or WebAs 7.0.
How does all these differe, is individual component of NetWeaver upgraded with higher versions or total NetWever is upgraded with a higher version.
Can any one please tell me the exact difference between versions.
If some one has ECC6 installed in their environment does it mean that they have Netwaver components like XI, EP, MDM.. etc are installed or its only R/3, BI etc...
How it works exactly?
Thanks,
Kiran.

Pretty much everything is explained in here:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf">SAP NetWeaver Process Integration 7.1 Overview of New Capabilities</a>
I think there's a weblog with a concise list somewhere, but I dont have the link saved.
Hope that helps.
James.

Error in START_J2EE_INITIAL phase of PI7.1 Ehp1 Upgrade

START_J2EE_INITIAL_TJI_02.LOG
com.sap.sdt.j2ee.phases.PhaseTypeControlEngine com.sap.sdt.ucp.phases.PhaseException Could not start AS Java instance with name J2EE and number 03 of the standard system. START_J2EE_INITIAL DOWNTIME UPGRADE NetWeaver Upgrade SAPJup Java Upgrade
dev_server0 log
F [Thr 26215] Tue Dec 1 20:22:27 2009
F [Thr 26215] *** WARNING => SfCFramework::registerNatives: failed for com.sap.conn.rfc.driver.CpicDriver [sfxxifrw.hpp 165]
M
M [Thr 21075] Tue Dec 1 20:22:46 2009
M [Thr 21075] ***LOG Q0I=> NiPConnect: 127.0.0.1:3305: connect (79: A remote host refused an attempted connect operation.) [nixxi.cpp 2777]
M [Thr 21075] *** ERROR => NiPConnect: SiConnect failed for hdl 25/sock 72
    (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3305) [nixxi.cpp    2777]
std_server0. log
Service [com.sap.security.core.ume.service] start ================= ERROR =================
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:3305' not reached
TIME        Tue Dec 1 20:17:29 200
RELEASE     711
COMPONENT   NI (network interface)
VERSION     39
RC          -10
MODULE      nixxi.cpp
LINE        2777
DETAIL      NiPConnect: 127.0.0.1:3305
SYSTEM CALL connect
ERRNO       79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER     3
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:446)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
     at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=SAPJup ASHOST=localhost SYSNR=05 PCS=1
In this phase it is trying to starup the instance with 03 sys no, but std_server0 log shows that ume service is trying to connect
to instance with sys-no 05 ( shadow).
I also refered to the wiki link,
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=JSTSG&title=(SLTG)(SAPJUP)+Problems-P1&decorator=printable
where it says the DDIC password needs to be same in both 000 and the ume store client ( eg 030), which i checked in our case
and the DDIC password is the same,
Experts please help, helpful answers will be fully rewarded with points.
Thanks,
Govind
Edited by: Govind Prathi on Dec 2, 2009 5:24 PM
Edited by: Govind Prathi on Dec 2, 2009 5:27 PM

Hi Govind,
please post the /work/dev_jcontrol trace file.
maybe the following link helps you to analyze your problem regarding RFC_ERROR_COMMUNICATION
http://help.sap.com/saphelp_nw70/helpdata/EN/20/361941edd5ef23e10000000a155106/content.htm
Please have a look in dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation. The following document describes, how tracing can be switched on/off:
http://help.sap.com/saphelp_nw70/helpdata/en/f6/daea401675752ae10000000a155106/content.htm
Be sure that j2ee_admin user is not locked.
Check /etc/services for '127.0.0.1:3305'
please also be sure that the UME.Properties settings in com.sap.security.core.ume.service are correct:
Please start offline configtool, goto cluster_data - server - cfg - services and check the property sheet
com.sap.security.core.ume.service
please also update ume.r3.connection.master.ashost with hostname of your portal server.
then restart your JAVA instance.
Is this dual stack (ABAP+JAVA) ?
Does your system is running on High Availability server?
Gerd
Edited by: Gerd Schuster on Dec 2, 2009 5:09 PM
Edited by: Gerd Schuster on Dec 2, 2009 5:20 PM

How to migrate content from BW 3.1 to NetWeaver 7.0

Hello all out there,
For a couple of years I have been successfully using SDN, finding always the right answer to my questions, however in my late assignment things have not been running that smoothly.
This is my first posting to SDN and I hope any of you out there can give me a hand.
My Case:
We are planning to upgrade from BW 3.1 directly into NetWeaver 7.0
Our previous research within our planning phase has taking us to read:
Everything under the Marketplace NetWeaver Upgrade portal (https://websmp204.sap-ag.de/upgradenw70)
Upgrade Master Guide
Many docs in SDN
My Question:
Based on our research, we have a good understanding about the technical upgrade path and the creation of a new landscape. However anything we have read explains about how to migrate our actual Queries, ODS, Web Templates, Infocubes, Update Rules, InfoObjects, etc to the new environment.
Could you please point me to the right literature, how to guide, migration path, etc; explaining how to migration content from BW 3.1 to NetWeaver 7.0
Thanks
Alejandro

Hi,
This is more a question for the BI forums.
Anyway, have a look at
service.sap.com/upgrade-bw
BW3.0B upgrade to BI 7.0 question about BI Content 3.1
/thread/367125 [original link is broken]
/thread/150068 [original link is broken]
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
Eddy
PS. Which type of SDN Ubergeek/BPX suit are <a href="/people/eddy.declercq/blog/2007/05/14/which-type-of-sdn-ubergeekbpx-suit-are-you">you</a>?
Deadline: June 15th

Error CHECK_INSTANCES_DETECTED While upgrading EP 7.0 to 7.3

Hello Experts,
I am trying to upgrade EP 7.0 to 7.3. I am getting the following error in the configuration stage:
There is a mismatch between the dialog instances detected by the maintenance procedure and the dialog instances read from Configuration Manager. Possible reasons can be: Dialog instances were removed before starting the maintenance procedure and SAP Note 871523 was not applied afterwards. Some of the dialog instances were not up and running when the procedure was started. Dialog instances detected by the maintenance procedure: JC00 on <Host> with profile:/usr/sap/<SID>/SYS/profile/<SID>_JC00_<Host> Dialog instances read from Configuration Manager: none You can find more information in the log file /usr/sap/<SID>/upg/java/log/CHECK_INSTANCES_DETECTED_CID_01.LOG.Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypeCheckDialogInstances com.sap.sdt.util.diag.DiagException There is a mismatch between the dialog instances detected by the maintenance procedure and the dialog instances read from Configuration Manager. Possible reasons can be: Dialog instances were removed before starting the maintenance procedure and SAP Note 871523 was not applied afterwards. Some of the dialog instances were not up and running when the procedure was started. Dialog instances detected by the maintenance procedure: JC00 on <Host> with profile:/usr/sap/<SID>/SYS/profile/<SID>_JC00_<Host> Dialog instances read from Configuration Manager: none CHECK_INSTANCES_DETECTED INIT PREPARE NetWeaver Upgrade SAPJup Java Upgrade
I have gone through the note provided and it isnt applicable for me. Also i have reverified whatever solution thats given in the note too. All the things are intact in our system. Please could you share your thought of how to go solving this error.
Regards,
Srinivas

Hi,
Take a look at http://scn.sap.com/thread/1973294.
Regards,
Alex

Solution Manager 3.2 upgrade to version 7.0

Hello All,
I am in the Solution Manager 3.2 upgrade to version 7.0.
In phase IS_SELECT "Upgrade Assistant" asks to add a few files update
components (Attachment: screens). Two of them (ST-SER and CPRXRPM) I
managed to find and read.
However, in the SAP Service Marketplace I can not find the new Add-On'ów:
ST and ST-ICO.
(For example:
ST - 400,
ST-ICO - 150_700)
Can I skip them in this step and leave the current versions?:
ST - 320 level 19
ST-ICO - 150_620 level 10
Best regards,

Those are part of the normal "upgrade" package - I wonder which DVDs you used to start the upgrade...
SAP Solution Manager 4.0 Upgrade (2) 1 of 11
etc.
Are you trying to do a Netweaver upgrade? This won't work...
Markus

Netweaver upgrade

Similar Messages

Maybe you are looking for