Java Support Pack Stack - what about additional patches?

Hi Guys,
I have applied Java SP stacks many times before so this is not a technical question as such.
We download the entire SP Stack and apply it via JSPM. But this only updates the system to that stack with patch level 0. For instance, if I apply SP Stack 3, then all the components will have SP3 patch 0. SAP releases bug fixes from time to time in the form of additional patch files like SP3 patch level 1, 2, 3, etc. for individual components but these are obviously not part of the downloaded stack but need to be downloaded separately for each component.
My question is, is it a good strategy to apply the entire stack as downloaded so this makes all the components to patch level 0 in that stack and then also download all of the latest patch files for each component within that SP level and apply all of them in the next run?
So I think this should fix all the bugs that SAP has fixed using these patch files so this would save us a lot of time which usually goes wasted in encountering the bugs, finding solutions and maybe even going to SAP just to find out that the latest patch files are released which already contain these fixes.
So, can someone tell me whether this is a good idea to do it this way? Or is there any downside to this?
Thanks and Regards,
Shitij Bagga

Hi,
You can apply eaither ways there woun't any problem.
i mean you can apply directly patch with SP leve or apply the SP level with patch 0
When ever if we apply the patch for any SP level, it over write all the file with patch file
Thanks,
Sreeni.

Similar Messages

  • What is the best way to apply Support Pack Stacks among satellite systems

    Hi,
    We have differenst systems liek R3, SCM,CRM,XI, BW  and EP. We would like to apply teh support pack stack 12.
    Which land sacpe need to be applied with the stack first?
    R3 or other satellite systems? Is there any recommendation available from SAP on this?
    Thanks in advance
    Jnaneswar.P

    Thanks for your reply Nick101. I see my example was oversimplified. When I say "multiple groups of contacts over multiple users" I'm really referring to N groups of contacts over N users.
    So I need to add Fred, who can access and sync Bob's contacts, Sally's contacts, and Common contacts, as well as Fred's contacts. Can I do it with OS X server?
    You mention you keep your and your partner's contacts administered locally. What keeps you from administering them through OS X server as well?
    I am guessing this can all somehow be accomplished with multiple contact accounts, but I can't find any information on the web explicitly describing this.

  • Support Pack Stack

    hi,
    can any body please tell
    what is support pack stack?
    is it contains patchs for ABAP and JAVA stacks or only for JAVA?
    can we patch for java individual component?
       i know how to apply through JSPM.
    thanks inadvance,
    regards,
    raju.

    Raju,
    The SP Stacks are sets of Support Packages and patches for the respective product version that must be used in the given combination.
    They are for ABAP and Java.
    In general, when applying support packages, you always have to apply the complete Support Package Stack.
    Patches to a specific Support Package can be installed individually.
    For example, if you are on SP Stack 12 and need Support Package 14 for a certain component, you have to apply the complete Support Package Stack 14.
    If you just need a patch for Support Package 12 of a certain component, you can just apply the patch, as long as it is Support Package 12.
    More details here https://service.sap.com/sp-stacks
    Thanks,
    Dieter

  • Errors in Runtime workbench after support pack stack 12

    We have installed support pack stack 12 and now the runtime workbench - component monitoring is not working.  I get a page of errors.  here are some of the errors
    Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:250: cannot resolve symbol symbol : method getTestModel () location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel CompTestModel testModel = cmMainModel.getTestModel(); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:283: cannot resolve symbol symbol : method getTextFromCore (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_tray_0.setTitle( cmMainModel.getTextFromCore("component_monitoring") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:391: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_0.setValue( cmMainModel.getText("all_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:415: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_1.setValue( cmMainModel.getText("red_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:439: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_2.setValue( cmMainModel.getText("redYellow_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:486: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_0.setText( cmMainModel.getText("go_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:647: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_1.setText( cmMainModel.getText("tree_view_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:662: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel String label = cmMainModel.getText("switchToTableView"); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:703: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_2.setText( cmMainModel.getText("ccms_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:808: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_group_1.setTitle( cmMainModel.getText("searchResults_group") );
    I have done the java support pack again to make sure it was installed properly.
    Thanks,
    Dede Logan

    Well after the SAP XI server was restarted and I tried to go back into the runtime workbench and then into the Component Monitoring I am getting another error.
    Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:74: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:79: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ 2 errors .
    does anyone know how to correct this error or what the cause of the error.
    dede

  • Unable to Deploy Java Support Packs :(

    I have an XI System Running on DB2 UDB (NW2004S), and it has ABAP and Java, and the Kernal patch was 83, so I upgraded to 102, and then ABAP Support packs were completed, but when i was trying to Deploy Java Support packs it gave me an error that its unable 2 restart the Cluster in Safe mode, so when i again tried loggin on to JSPM, SDM was stopped, and it asked me to restart and login to JSPM, and im trying to start SDM, and its trying for more than 300 Seconds and erroring out , so I tried launching  the Config tool, and its unable 2 connect to DB , and it says Password Expired, how do i go about Fixing this Issue????? But i remember when i was trying to bring up SAP, Schema password SAPSID was expired and application was unable 2 talk to Database, so i reset the password and updated it /sapmnt/SID/exe/global/dscdb6.confg file,Do we have any place where we need to update in JAVA as well.. im not aware of it ..
    Regards,
    Ershad Ahmed.

    Hi Ahmed,
    yes, usually there is also a Java schema which is different to the ABAP schema. The default name is sap<sid>db (all lower case - but it should not be case sensitive). You may find out the schema when you query for number of tables per schema beginning with sap: SELECT tabschema, count(*) FROM syscat.tables WHERE tabschema LIKE 'SAP%'
    Regards
    Ralph Ganszky

  • ABAP + Java Support Pack installation

    When updating support packs in an ABAP+Java environment (ECC 6.0), is there any reason why one could not do the Java Support Packs first, followed by the ABAP support packs?  We are trying to update our support packs as efficiently as possible, and would like to update our java support packs first, followed by the ABAP stack a few days later.
    In regards,
    Michael

    Hi!
    There can probably not be a general answer to that question. There are some functionality where ABAP and JAVA are closely linked and where you'll most likely run into problems if the levels do not match.
    Technically there is no problem as applying the SP-Stack for Java and applying SPs for ABAP are independent (technical) tasks, but you will have to VERY carefully check the dependencies and carefully test this in a QA-environment.
    If you want my advice: Try to find a 'big shot' solution where you do all in one move.
    Regards,
    Jörg

  • Update Java Support Package Stack in JSPM

    Hi all,
    When i update Java Support Package Stack in JSPM i can't start the dispatcher
    [Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 920] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
    When i goto the log-file of the dispatcher (server.0.log):
    E:
    usr
    sap
    P01
    DVEBMGS01
    j2ee
    cluster
    dispatcher
    bin
    services
    log_configurator
    log_configurator.jar
    Loading model: {parent,local,references}
    The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
         at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
    #1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
    #1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
    Somebody know how to solve this problem?
    Thanks in advance,
    Cheung

    defaulttrc.0.trc"
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[0, 2, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.1.trc]/>
    <!NEXTFILE[defaultTrace.1.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
    #1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

  • Basic Configuration and Support Pack Stacks

    Hi everyone,
    Just a general question about the Solution Manager 7 "basic configuration" stuff.
    Are you required to perform the "Basic Configuration" everytime after you apply a new support pack stack to solution manager?
    Or is it a one off, after the initial installation?
    Cheers
    Shaun

    Hello,
    https://websmp109.sap-ag.de/~sapidb/011000358700001927282008E has some information about your question.
    Only some parts of SOLMAN_SETUP must be run everytime, other parts are optional. For an overview please visit the link.
    Best regards,
    Miguel Ariñ

  • Setup SM 4.0 to allow me to approve support packs/stacks for download

    I need a doc or a procedure to setup Solution Manager for approving support packs/stacks for download.  I havn't had much luck finding a good one.

    Have you configured Maintenance Optimizer , if not use the following link to see the documentation  for configuring MOPZ
    https://websmp105.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000689877&
    From the above link click on <b>SAP Tutor on Maintenance Optimizer</b> this will show you how to use Maintenance optimizer and <b>Step by Step Configuration of Maintenance Optimizer SP Stack 09</b>  will help you to configure Maintenance Optimizer. ( scroll down to bottom to see the links)
    Thanks
    Prince Jose

  • List of notes part of an EHP1 Support Pack Stack

    Hi, is it possible to get a list of SAP notes included in a specific Support Pack Stack in Solution Manager?

    Hi,
    You can generate a side effect report of the support pack which will give you brief overview of all the changes included in the support pack.
    Thanks
    Sunny

  • Transport failure in QAS system after support pack stack 9 upgrade

    We have a DEV->QAS>PRD ECC system landscape. Recently we upgraded our DEV, QAS and PRD system to support pack stack 9 (with Kernel level 137). After the upgrade, we got transport failure in QAS where it shows pink colored down arrow which shows unable to open import queue when I click on it under stms import overview. If I put back the old kernel (Level 69), transport works just fine. DEV is the TP domain controller. When I run the RTPTEST in QAS, it show sthe follwing info:
    RFC Destination
    Destination CALLTP_WindowsNT
    tp Path E:\usr\sap\QAS\DVEBMGS02\exe\tp.EXE
    tp Executable Size: 10.352.432 bytes
    RFC Ping Error when opening an RFC connection
    tp Call
    RFC Link Error when opening an RFC connection
    tp Version
    DB Connect
    Offline Call Error when opening an RFC connection
    I will greately appreciate any input to resolve this issue.
    Thanks

    You need to upgrade two component of your kernel  tp and R3trans
    Also perform an additonal test with new kernel
    cd /usr/sap/trans/bin
    tp connect <SID> pf=TP_DOMAIN_<SID_DC>.PFL
    If you have issue to connect it means there is some issue with tp tool and/or connectivity
    Cheers !
    Manish

  • Latest support pack stack

    Hi ,
    Our system is on  SAP_APPL           604         0003       SAPKH60403       Logistics and Accounting
    Curretnly which one is the latest support pack available and where do we monitor this regularly . i.e Please provide the patch where we can monitor and continously update with latest SAP support stacks.
    regards
    Chandresh

    > Curretnly which one is the latest support pack available and where do we monitor this regularly . i.e Please provide the patch where we can monitor and continously update with latest SAP support stacks.
    You have three possibilities:
    1. Check manually using
    http://service.sap.com/patches
    --> Support Packages and Patches - Entry by Application Group
    --> SAP Application Components
    --> SAP ERP
    --> SAP ERP ENHANCE PACKAGE
    --> EHP4 FOR SAP ERP 6.0 / NW7.01
    --> Entry by Component
    --> Central Applications
    --> SAP APPL 6.04
    --> Support Packages
    2. create a maintenance optimizer task to update your system and check which new SPs are available
    3. Check
    http://service.sap.com/sp-stacks
    --> SP Stack Schedule
    And look when SP4 will be available (SAP EHP4 for SAP ERP 6.0)
    The first approach is good for a quick look but it's not advised to separately install only one component. There may be dependencies to other components and you will have then hard time to satisfy them manually.
    According to the schedule SP4 for SAP_APPL 604 is available in second week of october.
    Markus
    Markus

  • IXOS workflow template 4.7 support pack stack 24 problem

    We are upgrading to the above support pack.  Using a customized workflow template created by IXOS we have uncovered a problem.  When an entry is put into the sap inbox we have option of REJECT EXECUTION after which a menu is displayed with other actions.
    The REJECT EXECUTION no longer works.  In debugging the workflow we get to  RH_TASK_ATTRIBUTES_RUNTIME but not to RH_GET_TASK_START_EVENTS.
    Any ideas?
    Thanks
    Jean Wright

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • Automatic Transport Requests and Support Pack Stacks using CHaRM

    Hi Experts,
    Could you please give your valueable inputs on below Requriements :
    1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    would be helpful if any one could send the documentation on above requirements.
    Regards,
    Vijaysateesh

    Hi,
    >
    > 1. All Transports Requests needs to be Automatically moved from Solution Manager using CHaRM.
    Yes. You can schedule a periodic job (say for example daily 6M) to import all released transport requests from  QAS to PRD of a maintenance cycle/project. This is the task "Import Transport Request(Backround)" given in task list (tcode-SCMA) of a maintenance cycle.
    > 
    > 2. Automatic Support Package Stacks needs to be updated using Solman - CHaRM
    I haven't done this. But this is the  task "Import Support Package" given in task list (tcode-SCMA) of a maintenance cycle.
    I hope there is no specific documents for these. It's the same documents related to ChaRM.
    Regards
    Sanjai

  • NW MI 7.1 has only ABAP stack. what about JAVA stack ?

    Hi,
    Recently i installed NW MI 7.1 EHP1 system. It has only ABAP stack. But for MI configuration i hope we require JAVA stack too.
    Hence can we use some other standalone JAVA system for the MI front end configuration ? If so please tell me what are the usage types are required for that Standalone JAVA.
    Thanks & Regards,
    Bala

    Hi,
    EPC or standard AS Java usage types would be required for MI configuration.
    Suggest you to go through the Master guide at https://service.sap.com/~sapidb/011000358700000391152007E.pdf
    Also more info at http://service.sap.com/instguides ->SAP Netweaver -> Netweaver Mobile 7.1
    Regards,
    Srikishan

Maybe you are looking for

  • Will only give print option of "current frame" for a six page PDF document opened from link in Safari.

    I'm new to Mac having just moved from a PC.  The TD Ameritrade site provides statements as PDF documents which are opened by clicking on a link.  The document is displayed in a pop-up window and there is no problem viewing all pages by scrolling.  Bu

  • Removal t

    Hi All?Iv been having major probs lately with my sound card and software. I get these messages when i load mediasource. [size="3" face="Times New Roman">)your music library is corrupted and cannot be recovered Mediasource will now revert to your most

  • Error Message Classes for Leave Request

    Hi, I've checked every error message class I can think of but can't find the warning message: "Absence cannot be partial-day, so clock times have been removed." which is displayed in Leave Request. Does anyone know which class it is in so I can stop

  • How Build a SAP NetWeaver BW 7 Business Inteligence Competence Center

    Dears, According to you, what are the skills needed to build a 'Standard' Business Inteligence competence center using SAP NetWeaver BW 7 ? What developping people must know to face off major business and user requests ? Best regards Didier

  • Filesharing in AirPort

    Hi All, when I upgraded to AirPort Express I lost connection to other computers in my home network. They are not visible and the alias I used before to connect is not working. The WiFi is working properly when connection to internet. It is the filesh