Upgrade CE 7.1 SP3 to SP4

Hi all,
I have a problem upgrading the version of CE 7.1 SP3 to SP4.
I have read the master guide. There are 2 options described there:
1. from SP03 to SP04 or higher manually
2. using the update management service
For the second option I need the /ceupdatemanagement tool from the <drive>\usr\sap\<SID>\SYS\exe\uc\<PLATFORM> directory. I don.t have one.
I chose the first option. It is written:
Download the update files from http://service.sap.com/swdc Download Support Packages and
Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER CE
7.1 Support Package Stacks .
5. Stop the SAP Management Console.
6. Windows: From the download folder from SAP Service Marketplace, run the update tool
update<ID>.exe to apply patches and updates to your SAP NetWeaver CE system.
Ok , when I downloaded the files I don't have a update<ID>.exe file in this download directory. Do I need to download it separately and if so, where I can download it. Is this the ceupdate tool?
Thanks in advance,
Best regards,
Vera Stoyanova

First part of the file, then all software components:
RETURN CODES OF UPDATEXE
     RC_OK               : 0
     RC_ERROR          : 1
     RC_UP_TO_DATE     :2
PRINT ALL PARAMS -- BEGIN
-updateResultsXML updateResultsXML.xml
-proxyhost proxy.tenaris.techint.net
-asUser Administrator
-systemdescriptionXML systemdescriptionXML.xml
-osUser
-pathtoj2ee D:/usr/sap/CEL/J02/j2ee
-workDir D:/usr/sap/CEL/J02/work
-testsmp false
-smpuser S0003667933
-sid CEL
-instanceName J02
-inboxdir
-gfExeDir D:/usr/sap/CEL/SYS/exe/uc/NTI386
-nomask true
-modus check
-proxyport 80
-downloadResultsXML downloadResultXML.xml
-hostname tnswep03
PRINT ALL PARAMS -- END
nomask is true
nomask is true
AS Admin PWD:
nomask is true
SMP PWD:
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: init me
osPWD is null, no need to create OSCredentials array
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: init done
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: creat env of JSPM
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: created
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: creat env of JSPM toolinfo
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: hostname: tnswep03
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: sid: null
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: insatance: J02
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: pathtoj2ee: D:/usr/sap/CEL/J02/j2ee
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: workindir: D:/usr/sap/CEL/J02/work
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO:  + env, see above
com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: created
<?xml version="1.0"?>
<productDescription version="1.0">
  <systemNumber>*** not yet assigned ***</systemNumber>
  <product pvnr="01200615320900001418">
    <usageType id="4">
      <j2eeComponent technicalName="ADSSAP" release="7.10" supportPackage="3"/>
      <igsComponent technicalName="BC-FES-IGS" vendor="sap.com" release="7.10" supportPackage="3" osType="NT_I386"/>

Similar Messages

  • After upgrade the MDM 71 Sp3 to SP4 the MDS dos not startet

    Hello,
    I have an problme after a update from MDM 7.1 SP3 to SP4. The update was finished successful but my MDM Server (MDS) stopped after the starting wiht follow message
    Starting: /usr/sap/TBD/MDS10/exe/mds-r - Wed Mar  3 10:16:31 CET 2010
    SunOS Q4DE8NSYM07 5.10 Generic_141415-04 i86pc i386 i86pc
    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) unlimited
    stack(kbytes) 10240
    coredump(blocks) unlimited
    nofiles(descriptors) 4096
    memory(kbytes) unlimited
    -rwxr-xr-x   1 tbdadm   sapsys   179664288 Feb 13 20:52 /usr/sap/TBD/MDS10/exe/mds-r
    Application Started.
    mds Version 7.1.04.120
            Built on 2010-Feb-13
    Client Interface Version 7.1.04.07
            - Interface CRC=0x9229b868
    MDS Admin Interface Version 7.1.04.07
            - Interface CRC=0xb7b7fe03
    MDS Public Interface Version 7.1.04.03
            - Interface CRC=0xd7594919
    Web Interface Version 7.1.04.11
            - Interface CRC=0xb8de6193
    Application Stopped.
    Application Started.
    [INFO] <MDM/Servers/MDS/MDSCommon/XCSGlobalFunctions.cpp:415> "User authentication method: Repository"
    increasing thread stack from 0 kB to 1024 kB...
    Loading shared library: ncs.so ...
    ncs.so loaded.
    increasing thread stack from 0 kB to 1024 kB...
    increasing thread stack from 0 kB to 1024 kB...
    increasing thread stack from 0 kB to 1024 kB...
    Ending: /usr/sap/TBD/MDS10/exe/mds-r (rc=134) - Wed Mar  3 10:16:57 CET 2010
    When I start it again it dosn't work. With th update with my development System I had no problem.
    Have anybody an idea?
    Thanks
    Thomas

    Hi,
    I would suggest you to re-install MDM server again.
    Also refer, SAP Note 1432315 for upgrading MDM 7.1 SP3 to MDM 7.1 SP4.
    Go through section, B4. Update MDM Servers.
    Again, I would suggest you to go through this SAP Note 1432315
    Also refer SAP Note, Note 1359600 - MDM stopped communicating after upgrading to 7.1.03 or Higher.
    It tells that it is something related to TCP Port/firewall restriction Change. Please check this SAP Note for more details.
    Kindly mark the thread as Answered as your Problem solved so that others can benefit if they have similar issue.
    Thanks and Regards,
    Mandeep Saini
    Edited by: Mandeep Singh Saini on Mar 3, 2010 12:55 PM
    Edited by: Mandeep Singh Saini on Mar 3, 2010 4:57 PM

  • Upgrading from SP3 to SP4

    Hi Folks,
    I am upgrading from WLP8.1 SP3 to SP4 on Solaris Box.
    I got this error when I try deploying the EAR file in SP4 on solaris box.
    I followed the same steps upgrade from e-docs.
    1. created new domain
    2. Upgraded DB schema(executed upgrade_db_schema_to_81_SP4.cmd
    3. Updated portal app & portal libraries using work shop
    4. Built the EAR file
    5. Deploying the EAR file.
    I am not sure if I miss any steps.
    But when I deploy the EAR file I got this error.
    <Jul 8, 2005 7:11:58 PM EDT> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application trainApp.
    weblogic.management.DeploymentException:
    Exception:weblogic.management.ApplicationException: activate failed for content.jar
    Module: content.jar Error: Exception activating module: EJBModule(content.jar,status=PREPARED)
    Unable to deploy EJB: ValueBean from content.jar:
    [EJB:011028]The DataSource with the JNDI name: contentDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.

    Hi all,
    I got this error when I was trying to hit my home page.
    Am I missing some libraries?
    javax.servlet.ServletException: com/bea/p13n/security/internal/P13nContextThreadLocal
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:344)
    at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:531)
    at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:383)
    at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:4061)
    at weblogic.servlet.internal.WebAppServletContext.handleThrowableFromInvocation(WebAppServletContext.java:3834)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3780)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

  • Is it possible to upgrade trial version of CE 7.1 SP3 to SP4?

    Hi
    Is it possible to upgrade trial version of CE 7.1 SP3 to SP4? if I try to follow the upgrade guide the upgrade<id>.exe as well as ceupdatemanagement.exe are not available.
    Please help.

    Look at the bright side, only iOS 5.1.1 and earlier had the older Google Maps App that I find easier to read on the traffic.  It does mean a lot of Apps you can't update, so be careful.  I'm in the same boat.

  • Help needed on upgrading portal application from sp3 to weblogic portal 10

    Hi Guys
    I have an application which is currently running on BEA Weblogic Portal 8.1 sp3. We need to upgrade our application from 8.1 sp3 to BEA Weblogic 10 version.
    (1) Is there any way for upgradation from 8.1 sp3 to portal 10 directly or do I need to upgrade it from sp3 to sp4 and then from sp4 to portal 10? Pls clarify?
    (2) How reliable are the BEAs automated scripts for retaining the personalization/customization of my application on sp3 to upgraded version i.e portal 10?
    (3) I believe, we do not need to do any coding/design changes/architectural changes into my application for this upgrade.
    Any help on this will be highly appreciated
    Thanks
    Jameel

    1) I believe only sp4 and later to weblogic 10 is supported (http://www.bea.com/content/news_events/white_papers/BEA_WL_Portal10_ds.pdf)
    so yes i think you need to upgrade from sp3 to a later version of the service pack
    2) You tell us :)
    3) Depends on your application and the features you have used. E.g. I believe Content management has changed between sp3 and what 10 supports.
    regards
    deepak

  • Upgrade sequence WAS 640 SP3 unix

    Can I upgrade to SP9 after I have installed Portal SP3?
    If I can't upgrade to SP9 after installing portal, can I simply delete the intance under usr/sap/JC00, upgrade WAS 640 to sp9 and then reinstall portal?
    Thanks
    John

    Hello John, I do not think deleting the portal will be necessary.  I am in the process of upgrading the portal now (currently upgrading the WEB AS to SP9).  All be it, I am doing it on Windows 2000MSSQL Server but I think it should be fairly the same.  Here's the process we kind of worked out in another thread,
    /community [original link is broken]
    1) Install Web AS 6.30 SP3
    2) Upgrade Web AS 6.30 to SP9
    3) Install EP 6.0 SP3
    4) Upgrade EP 6.0 SP3 to SP9
    5) Follow Directions in note 720298
    5) Install KMC 6.0 SP4
    6) Upgrade KMC 6.0 SP4 to SP9
    I will keep you posted on how everything went.

  • Weblogic 6.1 server upgrade from SP2 to SP3

    Hi All
    We have weblogic server 6.1 SP2 installed on the solaris machine. Now we
    have to upgrade our weblogic server 6.1 SP3. We also have downloaded the installable.
    But that installable seems to over-write the previous weblogic server & installs
    the server afresh. Is there any patch kinda thing available which allows me to
    upgrade from SP2 to SP3 ? I don't want a fresh new install of SP3 server.
    thanks in advance
    -Kiran Rane

    Upgrade installer from SP2 to SP3 is only available for paid BEA
    customers. You need a login at http://support.bea.com
    Kumar
    kiran rane wrote:
    Hi All
    We have weblogic server 6.1 SP2 installed on the solaris machine. Now we
    have to upgrade our weblogic server 6.1 SP3. We also have downloaded the installable.
    But that installable seems to over-write the previous weblogic server & installs
    the server afresh. Is there any patch kinda thing available which allows me to
    upgrade from SP2 to SP3 ? I don't want a fresh new install of SP3 server.
    thanks in advance
    -Kiran Rane

  • The Connection Server does not start after an upgrade to BO4.1 SP3

    Hello guys,
    The Connection Server does not start after an upgrade to BO4.1 SP3
    We are in process to upgrade our Business Objects environments to BO4.1 SP3
    The first 2 environments , the upgrade went fine. But the third environment de connection server won’t start.
    When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).
    Our OS is AIX
    Uncaught Exception in SilentScope: [CS] Ser
    verInitialization::InitManager::Initialize: 0.007^^
    The CS initialization failed within the CS server. Aborting
    trc file: "connectionserver_BIO.ConnectionServer_ncs.trc", trc level: 1, release: "720"
    Gerd

    Hi Amine
    The File seems ok
    File from the failing connection server
    -rw-rw---- 1 bioadm bosys 43993 Apr 11 11:29 boconfig.cfg
    File from our test system
    -rw-rw---- 1 bitadm bosys 43892 Apr 14 10:56 boconfig.cfg
    I created a new connectieserver(by the copy function), but the new server won't start.
    Regards
    Gerd
    Log
    |89d4a6e0-2a89-7a05-3020-a51d517ab872|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] Unhandled exception raised during CS initialization.
    init_srv.cpp:95:-: TraceLog message 3
    |4dcf04b1-1e1d-df13-48ad-a67f06e29864|2014 04 14 11:54:30:113|+0200|Error| |<<|E|X|connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] ServerInitialization::InitManager::Initialize: 0.003
    |77ad78f4-37f7-3013-3b50-85cce9fbe7b8|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] The CS initialization failed within the CS server. Aborting.

  • Reg:upgrade ERP to EHP5 SP3

    Hi all
    I am every new to this patches and up gradation concept .Here is the scenario .
    Current EP is at Stack Level 17.
    If we upgrade ERP to EHP5 SP3, the Net weaver Stack Levels should be at SP22 for BI and EP.
    If we donu2019t update EP and BI to stack 22, some inconsistencies can be induced in the system landscape because of ERP upgrade.
    how to check and analysis the impact in ESS Module because of applying any patches in EP server for EHP5 .
    Can any one please help me out ,how to work on it .
    Thanks In Advance
    Deepika
    Edited by: deepika_indian on Jul 1, 2011 11:47 AM

    Hi,
    I would suggest you to upgrade portal as well, as it contain ESS patches and this should be in sync with ECC version.
    You can check same in below link as well:
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES
    Thanks
    Sunny

  • Continual reboot after win2k sp3 or sp4 install

    Works w/ win2k sp2. With sp3 or sp4 installed reboots after logon screen (CtlAltDel) appears. BSOD quickly followed by splash screen of "Out of Range" message. Couldn't read BSOD message. Works fine after un-install sp* from safe mode. Fails when disp adapter set to VGA or SVGA modes. Fails w/ either PCI(STB) or AGP(GeForce2 MX-400). Un-installed display driver - still fails outside of safe mode.
    Any help is appreciated!  Thanx. -mw13j

    Try increasing your RAMs Voltage by 0.1v and do a clean format on your C: partition before installation or you could just update through Windows Update where everything is updated through windows 1st before rebooting.

  • Upgrade BO XI 3.1 sp3 to sp4

    Hi,
    As mentionned in the subject, we would like to upgrate our BO XI platform.
    We currently use the 3.1 sp3 (version number is 12.3.0.601) and the target is 3.1 sp4.
    I read in the SAP documentation that  "sp4 installation is supported on top of Fix pack 2.10 or lower or Fix pack 3.4 or lower".
    I'm not sure to clearly understand this advice, so my two questions are :
    1. With my current version, do I have to install a fix pack before installing sp4 ?
    2. Is it possible to uninstall sp4 ?
    (I understood that fix packs and service pack must be uninstalled in the reverse order in wich they were installed)
    Thanks !
    David

    Hi,
    1. No you dont - you can upgrade directly
    2. Yes it is. During Installation of SP4 one or more .zip Files will be generated in your BO_INSTALL_DIR. I think they are called something like "SP4_PATCH.zip". Unless you dont delete them manually, you can un- install SP4.
    Regards
    -Seb.

  • Upgrading BOXI 3.1 SP3 to BOXI 3.1 SP4

    Hi Folks,
    Currently we are using BOXI 3.1 SP3 and Netweaver 7.1c in our Project. Our Client is planning to move from Netweaver 7.1 c to Netweaver 7.3. This move is not a upgrade they are going to remove Netweaver 7.1 c first and then installing Netweaver 7.3 freshly.
    SAP has suggested to upgrade from BOXI 3.1 SP3 to BOXI 3.1 SP4 for Netweaver 7.3.
    will this upgrade impact existing environment? If yes, please provide me necessary precautions to minimize the efforts.
    Regards,
    Anil

    Hi,
    if you have an integration from your SAP Portal to BOE i would recommend you take a backup of the web.xml file for openDoc and InfoView. Afterwards you can start the installation of SP4.
    Regards
    -Seb.

  • Upgrade problem CE 7.1 SP3 to SP4  (ESP_FRAMEWORK)

    Hi all,
    I have a problem upgrading the version of CE 7.1 SP3 to SP5.
    Deproying component 'sap.com/ESP_FRAMEWORK' is aborted .
    Please Help me . How to Resolve this problem?
    My system is NW CE 7.1 Productive Edition SP03 , win2003 x64.
    @Following is Detail.
    1.I downloaded the SP05(from SP03) files from SMP.
    2.I had start the update tool ( CEUPDATE69_0-10005101.EXE ) .
    (I could'nt use [Update Management Service tool] ,because of my network environment is using 'http proxy user/password'.)
    3.When deployment phase ,following error was occured.
    Details message(s):
    Software component ESP_FRAMEWORK deployment messages:
    Deployment of archive \\vmces10\sapmnt\trans\EPS\in\ESPFRAMEWORK05_0-20001918.SCA for component sap.com/ESP_FRAMEWORK aborted
    Detailed message: 1. Contains Aborted deployment component: sdu id: sap.com_tc~esi~esp~app sdu file path:
    E:\usr\sap\CES\J00\j2ee\cluster\server0\.\temp\tc~bl~deploy_controller\archives\62\ESPFRAMEWORK05_0-20001918_SCA1211224546031\DEPLOYARCHIVES\sap.com~tc~esi~esp~app.sda
    version status: HIGHER deployment status: Aborted description:
      1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/tc~esi~esp~app application.
       ERRORS: * Application Model Builder: Content is not allowed in prolog., file: sap.com~tc~esi~esp~app.sda#META-INF/application.xml, column 1, line 1
       , severity: error * Web Model Builder: Content is not allowed in prolog.
       , file: sap.com~tc~esi~esp~app~web.war#WEB-INF/web.xml, column 1, line 1, severity: error Hint: 1) Given application file is not valid one.
    Deployment of archive \\vmces10\sapmnt\trans\EPS\in\ESPFRAMEWORK05_0-20001918.SCA --> sap.com~tc~esi~esp~wsil.sda for component sap.com/tc~esi~esp~wsil
    is rejected because deployment of other component it depends on is rejected
    Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~esi~esp~app contained in software archive: sdu id: sap.com_ESP_FRAMEWORK
    Deployment of archive \\vmces10\sapmnt\trans\EPS\in\ESPFRAMEWORK05_0-20001918.SCA --> tc~esi~uddi~sr~proxy~ear.sda for component sap.com/tc~esi~uddi~sr~proxy~ear
    is rejected because deployment of other component it depends on is rejected
    Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~esi~esp~app contained in software archive: sdu id: sap.com_ESP_FRAMEWORK
    Deployment of archive \\vmces10\sapmnt\trans\EPS\in\ESPFRAMEWORK05_0-20001918.SCA --> sap.com~tc~esi~esp~app.sda for component sap.com/tc~esi~esp~app aborted
    Detailed message: 1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/tc~esi~esp~app application. ERRORS: * Application Model Builder: Content
    is not allowed in prolog., file: sap.com~tc~esi~esp~app.sda#META-INF/application.xml, column 1, line 1, severity: error * Web Model Builder: Content
      is not allowed in prolog., file: sap.com~tc~esi~esp~app~web.war#WEB-INF/web.xml, column 1, line 1, severity: error Hint: 1) Given application file is not valid one.
    See Deploy Controller log E:\usr\sap\CES\J00\j2ee\JSPM\log\log_2008_05_20_03_52_08\deploy_2008-05-20_04-07-44.log for details.
    Thanks in advance,
    Best regards,
    Seot

    Hi Vani
    thanks again.
    -->1. Do you have the value of the key UpdatePolicyURL?
    I think UpdatePolicyURL doesn't have relation to SP applying.
    What meaning is it?
    -->2. I assume you do have an SID.
       'SID'  means SAP support market place's ID ?
       I had just registered OSS message.
    -->Also, could you please chk this doc?
       yes. I proceedured patching with this doc.
    *additional logs are following
    JSPM_MAIN_1_01.LOG
    Deployment of archive F:\sp5\BIWDALV05_0-20001925.SCA --> bi~alv~common.sda for component sap.com/bi~alv~common is rejected because deployment of other component it depends on is rejected
    Detailed message:
              1. Aborted deployment archive:
    sdu id: sap.com_tc~esi~esp~app
    contained in software archive:
    sdu id: sap.com_ESP_FRAMEWORK
    See Deploy Controller log E:\usr\sap\CES\J00\j2ee\JSPM\log\log_2008_05_26_22_49_27\deploy_2008-05-26_22-59-15.log for details.
    <br><b>Overall deployment messages:</b>
    Deployment finished with error.
    May 26, 2008 11:20:06 PM [Error]: Deployment of queue STI-1211809786655 completed with error Deployment finished with error.
    JSPM version is 7.10.5.0.24. Current JSPM log directory is E:\usr\sap\CES\J00\j2ee\JSPM\log\log_2008_05_26_22_49_27.
    deploy_2008-05-26_22-59-15.log
         695. Client path 'F:\sp5\ESPFRAMEWORK05_0-20001918.SCA --> sap.com~tc~esi~esp~app.sda'
         Sdu info :name 'tc~esi~esp~app', vendor 'sap.com', location 'SAP AG', version '7.1005.20080201145918.0000', software type ('J2EE', sub type ''), dependencies :[( name 'tc~esi~esp~lib', vendor 'sap.com') , ( name 'tc~esi~esp~api', vendor 'sap.com') ]
              Deploy status is 'Aborted'
              Description:'1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/tc~esi~esp~app application.
    ERRORS:
    * Application Model Builder: Content is not allowed in prolog., file: sap.com~tc~esi~esp~app.sda#META-INF/application.xml, column 1, line 1, severity: error * Web Model Builder: Content is not allowed in prolog., file: sap.com~tc~esi~esp~app~web.war#WEB-INF/web.xml, column 1, line 1, severity: error
    Hint: 1) Given application file is not valid one.'.
    regards.
    seo

  • TM 7.1 upgrade from SP3 to SP4

    Dear all,
    We have TM 7.1 system installed.
    We are currently running on EHP1 Netweaver 7.1 version with SP03.
    We want to upgrade our system to SP4 , where could i find detail upgrade guide , or list of patches i need to
    apply to upgrade the TM system.
    Regards,
    RR

    Hi Basisrr,
    Below are some details which might be helpful to you.
    To get the information and Snote:- https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065738
    To down load the installation Patch:- service.sap.com/sp-stacks or Service.sap.com/swdc
    Transaction to install :- SPAM
    Please revert if you need more information on the same.
    Best Reghards,
    Vikram

  • Upgrade from sp3 to sp4

    Dear all,
    Help me please with the following trouble i found during the subj.
    I had a directory with the BEA Platform installed. As a first step of the 'upgrade' procedure the platform has been uninstalled, then I killed all the directories left(where $BEAHOME points). I installed fresh sp4 in the old $BEAHOME, created new Basic Platform domain and tried to deploy existing portal application on it: updated portal libraries for portal application, rebuilt app and began redeployment process.
    So, i've got exception:
    <Error> <HTTP> <myhostname> <portalServer> <main> <<WLS Kernel>> <> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "MyAppName".
    javax.servlet.ServletException: FRAMEWORK
         at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:919)
         at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:883)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:822)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3333)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3290)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3276)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3259)
         at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5949)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:862)
         at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2127)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2168)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2115)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3082)
         at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    Caused by: java.lang.NoSuchFieldError: FRAMEWORK
         at com.bea.netuix.servlets.manager.PortalServlet.<clinit>(PortalServlet.java:160)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1026)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
         ... 19 more
    >
    So, the question is: what could it be and how to fix such problem.
    Thanks

    Howdy,
    Sorry to raise this thread for the dead but it's the exact problem I'm experiencing. Google has a whopping 3 hits, 2 of which are linked to this thread.
    So hopefully the OP is still hanging around, or someone else has the answer.

Maybe you are looking for