Upgrade NW04 to NW04S

Hi Brad,
We are doing the Upgrade of Portal but it is on phase 72/118 for 4 days. Is it normal?
There is no error reported.
Regards,
Nivia

Hi Nivia,
I remembered something this morning, and verified in my migration/upgrade notes from last year.
I too had problems in my "deploy online" phase.
I had to update the oracle jdbc driver to the last 10.2.0.2 one.
You may give that a try (update the oracle jdbc driver) if the j2ee restart does not help you.
Brad

Similar Messages

Upgrading Portal from NW04 Sp14 to NW04S SP 9

Hi,
We are preparing to upgrade our EP 6 , NW04 SP 14 highly available installation to NW04S SP 9. It seems JSPM is the tool that comes with NW04s SP 9 which runs the upgrade for existing NW04s systems. However NW04 SP14 does not have this tool it only has SDM. Would be grateful if someone could tell me how to start off the upgrade? Do we need to deploy the JSPM from NW04s SP9 via SDM first on existing system? or is there another tool to start this upgrade?
Tarek

Hi,
1.Is this SP25 upgrade from SP24 will support the IE8 and Firefox 3.5
without any issues for webdynpro application running as of now?
For this you can refer SAP note 1098009, 1296463 and 960549.
2.is it required to upgrade ESS and MSS and anything on ERP side along
with Portal upgrade to SP25
Yes, you should upgrade ESS/MSS to keep it in sync with NW SP level. You can check below link for SP level of ESS/MSS with NW patch level and backend system patch level:
[Link|https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES]
3.After upgrade NWDI to SP25, all the present tracks with custom
components will work as it is?
It should work as such there is no well known issue with existing track after upgrade.
Thanks
Vijay Kalluri

What is the Upgrade program used to upgrade NW04 to NW04s

Hi,
What is the Upgrade program used to upgrade NW04 to NW04s?
Thanks Sri

<b>SAPup</b> - Program to upgrade Web AS ABAP and related components BW,XI
<b>SAPJup</b>- Program to upgrade WebAS Java and related components EP.
Vijay Kothapalli

Nw04 to nw04s

Hi,
got a couple of questions regarding nw04 to nw04s
currently we are on ep 6.0 sp14 and interested to use the features of NW04s.
1. is it an upgrade or migration from nw04 to nw04s? i hope it is an upgrade, am i right?
2. is it mandatory to upgrade all the systems in our landscape i.e. XI, BW, SRM, R3 to nw04s...or is there a facility to use only nw04s PORTAL.
3. as far as i know, nw04s and nw04, the SPs release are going in parallel.. i.e.
are the ep6.0 sp14 and nw04s portal sps5 have the same features or does nw04s portal has additional features compared to EP 6.0 SP14.
my point here is, we are only interested in upgrading portal, so is it ok to continue sp stacks of nw04 or should we shift to nw04s.
could someone please clarify
thank you

Hi,
The code developed on 2004 will work on 2004s.
Some minor changes have been made refer to the documentation for specific details
SAP NW2004s is the mySAP Business Suite edition of SAP NW 2004.it is a minor release that delivers on specific needs of the mySAP and xapps solutions delivered by SAP in 2005. the "s" stands for "mySAP Business Suite Edition".
The next major release of NW will deliver on Business Process Platform(BPP) it will be released in 2006.
Few of the New capabilities in NW2004s
1)Developing a web based user interface with Web Dynpro fro ABAP.
2)Enhancements to enabling B2B processes
3)Enhancements to business task management
4)Enhancements to business planning
5)Enhancements to enterprise data warehousing
6)mass setup of mobile devices
7)implementing a global portal
Refer the link for more info
http://help.sap.com/saphelp_nw04s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
NW04 is a 'Java version' which means you can develop applications using Java and export them to portal.
NW04s is a 'ABAP version'.Here you can develop ABAP reports and transactions and export them to portal. There you can create iViews using them.
Netweaver 04s, includes both the ABAP and Java stacks. The Sneak preview for NW04s is only for the ABAP stack, and the Sneak Preview NW04 SP15 is only the java stack. If you are using the sneak preview for ABAP, you can develop WDA applications and BSP applications, they run directly in the engine, not in a portal. But they can be embeded in an iView in some portal. You don't have to have a portal to run your application. If you are using the java side, you can develop WDJ applications and JSP applications. Same applies here, they run on the java engine, not in a portal, but can be embeded into an iView which runs on the portal. But you don't need a portal for your application to run. The portal is just a frontend UI, the apps themselves run on the underlying engine, whether its ABAP or JAVA.
Refer to the following threads for more information
Re: What is NW04 s?
Re: Differences between NW04 SP11 and NW04 SP15

NW04 vs NW04s

Dear all,
What is the difference between NW04 and NW04s? There appears to be some confusion here as to what is required for CRM4.0 and CRM5.0 in terms of which version of the Portal to run? We are currently implementing EP6 SP13 (part of NW04) and are wondering to to upgrade to the NW04s version of EP. Any pointers to documentation on this topic would be greatly appreciated.
Thanks, Neeta

Hi Neeta,
SAP NW2004s is the mySAP Business Suite edition of SAP NW 2004.it is a minor release that delivers on specific needs of the mySAP and xapps solutions delivered by SAP in 2005. the "s" stands for "mySAP Business Suite Edition".
The next major release of NW will deliver on Business Process Platform(BPP) it will be released in 2006.
Few of the New capabilities in NW2004s
1)Developing a web based user interface with Web Dynpro fro ABAP.
2)Enhancements to enabling B2B processes
3)Enhancements to business task management
4)Enhancements to business planning
5)Enhancements to enterprise data warehousing
6)mass setup of mobile devices
7)implementing a global portal
Refer the link for more info
http://help.sap.com/saphelp_nw04s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
NW04 is a 'Java version' which means you can develop applications using Java and export them to portal.
NW04s is a 'ABAP version'.Here you can develop ABAP reports and transactions and export them to portal. There you can create iViews using them.
Netweaver 04s, includes both the ABAP and Java stacks. The Sneak preview for NW04s is only for the ABAP stack, and the Sneak Preview NW04 SP15 is only the java stack. If you are using the sneak preview for ABAP, you can develop WDA applications and BSP applications, they run directly in the engine, not in a portal. But they can be embeded in an iView in some portal. You don't have to have a portal to run your application. If you are using the java side, you can develop WDJ applications and JSP applications. Same applies here, they run on the java engine, not in a portal, but can be embeded into an iView which runs on the portal. But you don't need a portal for your application to run. The portal is just a frontend UI, the apps themselves run on the underlying engine, whether its ABAP or JAVA.
Refer to the following threads for more information
Re: What is NW04 s?
Re: Differences between NW04 SP11 and NW04 SP15

J2EE supported versions for NW04 and NW04S

Hi ,
Can Pls anyone pointout some documents for the list of J2EE version support list( For Ex: JSP 2.0 suported in NW04S ) for NW04 and NW04S releases ?
Thanks
Praveen

Praveen,
Both NW04 and NW2004s are J2EE 1.4 compliant. You can get these details by accessing PAM [here|http://service.sap.com/pam]
Check this [wikipedia link|http://en.wikipedia.org/wiki/Java_EE_version_history] as well for more information.
And Java EE is supported in NW7.1
Chintan

Differences between NW04 and NW04s

Hello SAPians,
Can anybody explian me the diffrences between NW04 and NW04s. Or please tell me, where I can find regarding this information.
Thanking you.
Regards,
Ajaykumar

hi
good
NW04->
The Support Platform is an open platform to develop and run small utilities (known as plug-ins) that perform support-oriented activities on any and all components of SAP NetWeaver. The Support Platform is included NW04 SP13 and higher.
Plug-ins generally perform tests or create reports. A plug-in might check the configuration of the system, check if permissions are set correctly, or check the name of your current Web AS version. You can create plug-ins for any task that can be performed by a Java program.
Each plug-in is a single Java class, and groups of plug-ins are deployed to the Support Platform in JAR files. The Support Platform comes with a collection of out-of-the-box plug-ins; developers can write their own plug-ins, which administrators can then deploy and run.
The Support Platform can monitor the entire Web AS system on which it runs, and can run plug-ins on any of the Java processes in the cluster. The Support Platform provides a user interface for deploying plug-ins, displaying available plug-ins, running them and displaying the results.
NW04s -> This is an advance version of NW04 server.
thanks
mrutyun^

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?

Webdynpro error after upgrade NW04 to NW04s sp9

Hi,
I created some WD in NW04 using JDI. After upgrade to NW04s i got error messages in the program. The messages look like:
Error com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved (or is not a valid type) for the argument stateChangeInfo of the method wdDoApplicationStateChange LeaveReqComp.java OJL_TEST_Dpoczelfbedwebdynreqbelastingdienst.nl/gen_wdp/packages/nl/belastingdienst/zelfbed line 203
Hope somebody can help me solve my problem.
Kind regards,
Maarten.

Hi Maarten
I am also facing similar sort of problem when i am trying to import the local web dynpro DC into 2004s that was build n exported from 2004 and when i try to build it in 2004s i get error
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo cannot be resolved for the argument stateChangeInfo of the method wdDoApplicationStateChange
com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeReturn cannot be resolved for the argument stateChangeReturn of the method wdDoApplicationStateChange
were u able to solve the problem if yes please help me in that case
thanks !
Asif

Upgrade + migration from nw04 on windows 2000 to nw04s on windows 2008

Dear all,
I need to upgrade and migrate my nw04 java system from windows 2000 to nw04s on windows 2008.
From the PAM I can see that NW04 is not supported on windows 2008 and that nw04s (7.0) is not supported on windows 2000.
So, which is the correct upgrade path? Do I need an intermediate win 2003 server which is supported from both the releases?
Thanks and regards in advance
Federico

Hello my friend
This will be a very interesting project for sure. As you know, kernel 640 is not supported on win2008 and 700 is not supported on win2000, so here there must be a win2003 as a transition platform for this upgrade+ migration, not to mention migration from 32bit to x64 is also involved. You didn't mention the DB versions in source and target systems, as well as the SAP product you're trying to go with. Here's a brief checklist right now for what I can think of, once you're back with more details then let's make it intact:
I assume your source OS/DB is win2000SQL2000 32bit, target one is win2008SQL2008 x64.
1. Install a win2003 x64 server and SQL2000 32bit;
2. Install a new SAP instance same as your source system release in 32bit compatible mode;
note: if the system being migrated is BW, then be aware of that you might want to bring new features in SQL2008 of row compression and table partitions.
3. Detach the source DB from old SQL2000, and attach it to new SQL2000; some post configuration for DB copy will be required (STM tool). Now you've finish a migration from win2000 to win2003 32bit;
4. Start upgrading NW04 to 7.0, 640 to 700, find details in upgrade guide; Now you have your 700 instance on win2003 x64+SQL2000 32bit;
note: since release 701(700 EHP1) is available now, which you might want to upgrade instead of 700.
5. Change the collation 850BIN2 for SQL2000 32bit, detach DB;
6. Since migration from 32bit to x64 cannot be done smoothly, now you have to uninstall everything and reinstall win2003 and SQL2008 x64, followed by a new 700 or 701 instance;
7. Attach the source DB, post configuration for DB copy will be required (STM tool); Now you have your 700 or 701 instance on win2003 x64+SQL2008 x64;
8. Detach the SQL2008 DB;
9. Now go to your target win2008 OS, install SQL 2008 x64 and new 700 or 701 instance;
note: there might be some restrictions for NW 7.0 on win2008, go with the latest release (SR3 or newer).
10. Attach DB to this final OS/DB version: win2008 x64+SQL2008 x64, post configuration for DB copy will be required (STM tool).
Helpful?
Regards,
Effan

Upgrade from NW04 to NW04s

Hi,
We have a NW04 WAS 6.40 and we would like to upgrade it to a NW04s.
How can we perform it?
Has anyone some idea about which packages are necessary and how long does it take?
Thanks in advance!

Hi Christophe:
You can choose NW04 that is already in GA or you can choose NW04s that is currently in ramp-up; If you are going to start your implementation you can take full advantage and start using NW04s directly getting more value from the new functionalities of WAS 7.00.
You can get additional information from https://service.sap.com/rampup
Read this from the Marketplace:
SAP NetWeaver 2004s is the mySAP Business Suite edition of SAP NetWeaver 2004. It is a minor release that delivers on specific needs of the mySAP and xApps solutions delivered by SAP in 2005. The "s" stands for "mySAP Business Suite Edition". SAP NetWeaver 2004s will initially be made available through the ramp-up of the mySAP Business Suite Solutions. SAP NetWeaver is a comprehensive platform comprising former components like SAP EP or SAP BI, which do not longer carry an individual release number.
For customers looking to implement SAP NetWeaver during 2005 in the course of integration or development projects, or in the context of an ESA roadmap strategy, an implementation of SAP NetWeaver 2004 is recommended, as this is the current default release. An implementation of SAP NetWeaver 2004s is only recommended where new capabilities made available with SAP NetWeaver 2004s are absolutely required (e.g. Web Dynpro ABAP, new BI capabilities, MI - mass client administration).
Hope this helps!
Best Regards,
Federico

Checklist after upgrade from EP NW04 to NW04s?

Hi, Gurus:
what should be checked after EP NW04 upgradd to NW04s?
iview display
business struture
system connection
assigned role
any other should be paid attention to?
Br,
Nikko

Hi,
quick summary :
verify TREX connection / indexing
business package
SSO between user --> portal and portal --> R/3
Test systems in system landscape
Verify Url generator config
Verify services in monitoring
Local and online editing (test some office files)
Password rules in configtools
Logoff link
Notification/subscription emails (connection to mail server)
Backup online/offline (test the backups for a restore)
As said before, all custom services/programs, etc.
You need to rebuild them with the new 2004s developper studio (with 2004s api).
Brad

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

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

Could you please share us the solution?

Connect ECC 6.0 with EP NW04, BW NW04 and CRM 4.0

Hello All,
We have R/3 Enterprise 47 x 200, we have connected to it the EP version NW04, BW version NW04 and CRM version 4.0 so, we need to upgrade only the R/3 to the new ECC 6.0 without upgrading the other components.
My questions is if anyone knows if, Is it possible connect those old version to the new ECC 6.0 and where can I found this information?
I was looked into marketplace, help.sap and in this forums but I didn't found anything so if you can help me to solve it, I will be very grateful.
Thanks in advance,
Alfonso

EP6.0 will work perfectly fine with ECC6 but as previous posters have pointed out, technically its not a supported landscape.
You would have little problem with simple transactional, BSP access etc but you would need to be careful about the use of any business packages you might want to use. You would need business packages appropriate to the backend version you have (particularly for ESS/MSS) and then you would need to validate whether they actually work with EP6.0.
Bit of risk as its not supported.
Haydn

ABAP Dynpro available in NW04 and NW04s

Hello:
Is ABAP Dynpro available in NW04 as well as in NW04s? I think that WebDynpro (Java) is already available in NW04 but I was not sure about ABAP Dynpro.
Can anyone help me verify this?
Thank you...
George Lu

WD ABAP is fully useable in WAS 7.0(NW 2004s). There are reminants of WD ABAP in WAS 6.40(NW 2004). You can access the WD objects, but you may have some problems. But to answer, WD ABAP is only in 2004s.
Regards,
Rich Heilman

Upgrade NW04 to NW04S

Similar Messages

Maybe you are looking for