How to apply java support packages.

hi all,
i applied support packages for 4.7EE but i dont know how to apply java support packages.
can anyone explain about how to apply java support package for netweaver s??
from scratch anyone can explain.
regards
vijay

Hello Vijay ,
Java Support packs can be installed without using SDM also if you are on NW2004.
Process:
Eg SP18
Download the following DVDs
1. WebAS 6.40 SP18(Part 1/4): SAP Installer
2. WebAS 6.40 SP18(Part 2/4): SAPInst Control File for Oracl
3. WebAS 6.40 SP18(Part 3/4): OS Depend. parts of Java RuntiA
4. WebAS 6.40 SP18(Part 4/4): OS Indep. Parts of Java Runtime
Uncar each of them in the sequence
1,4,3,2
Once u uncr then u will get some more uncarred files
eg D:\sapinst\J2EE-RUNT-CD\SCS\NT\I386\SCS.SAR uncar it into run directory : DIR_CT_RUN ( D:\usr\sap\SRX\SYS\exe\runU)
Note: The value of DIR_CT_RUN can be found In Profile SRX_SCS01_B3BPH1W)
Run SAPINST
Note:Give RFC user as 000 DDIC
Java Support packs can be installed using JSPM if you are on NW2004s
1)Download SP Stack or SP
2)Copy the SCA files to /usr/sap/trans/EPS/in
3)Execute the JSPM go.bat from \sapmnt\SID\DVEBMGSXX\j2ee\JSPM
4) Provide SDM Password
5 ) Select the Traget SP level .
6 ) Deploy.
Also, you can find the current SP Level in http://localhost:5<instance numeber>00 and then system information.
Regards ,
Santosh Karadkar <a href="https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=3819594">Click here for further info</a>

Similar Messages

Error in Applying Java support packages through JSPM

Hi All,
While Applying support packages, Package CAF 7.00 SP 13 is through an error
help required.
                   For detailed information see the log file of the Deploy Service.
07/12/05 21:55:26 - ***********************************************************
Dec 5, 2007 9:55:26 PM   Info: End of log messages of the target system.
Dec 5, 2007 9:55:26 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 5, 2007 9:55:26 PM   Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0', grouped by software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 5, 2007 9:55:26 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:28 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:28 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 5, 2007 9:55:28 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0' : aborted
Please, look at error logs above for more information!
Dec 5, 2007 9:55:28 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:30 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:30 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 5, 2007 9:55:30 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0':
No further description found.
Dec 5, 2007 9:55:30 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:32 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:32 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 5, 2007 9:55:32 PM   Error: -
At least one of the Deployments failed -
Regards,
Prashant.

Hello Prashant.
Check this supporting SAP note 1010640. It will solve your problem.
This is typical problem when you upgrade from < SP8 to higher version.
You need to Undeploy the CAF components from the system using SDM first and then reply the patches from JSPM.
It should go with out errors.
Let us know if this worked.
*Reward points for helpful answer.
Regards,
Prashant P.

How to import all Support Packages simulteneily support Package Manager EBP

Can any body tel me how to apply all support package sumultanesoly by using support Package Manager EBP/CRM option in SPAM.
I could not able to select all pactche at a time.It selecting one patch at a time only
Regards
G Sasikanth Reddy

I solved my self by selecting highest level of patch so that its dependencies can also add to the queue.
Regards
Sasikanth Reddy

How to deploy EAR on CE server using Java Support Package Manager

Hello,
I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
Does any one has idea?
Regards,
NK

Hi,
The Java Support Package Manager is not able to deploy a single .ear file.
If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
You have to create a .SCA from an .EAR file
SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
Gerd

Error in "Test IMPORT" during applying BASIS Support Package

Hi All,
I'm applying basis support package from SAPKB70014 to SAPKB70018,
now it hangs in Import phase: TEST_IMPORT, there maybe something wrong with the import object.
For detail screenshots, please kindly have a look at URL: http://nickfiles.150m.com/Question_1.html
And for the detail import log, please have a look at http://nickfiles.150m.com/SAPPB70015.html.
I think the root cause is located in:
2EETW165 Function "TMW_TAOAGENT (TMW_TAOINTERFACE|01)" does not fit into the existing function group "(TMW_CLIENT_INTERFACES|06)".
2 ETW167 Please transport the whole function group.
But I do not know how to solve it. Could anyone help me?
Thank you very much.
Best regards,
Nick

Hi Nick,
This is the solution to your Issue..
Note 1156706 - Function TMW_TAOAGENT (TMW_TAOINTERFACE 01) does not fit...
Other SAPnote you can read .. for your help..
Note 42379 - SPAM aborts at step TEST_IMPORT
Note 1092979 - TMW_TAOAGENT: Repairing function group after SAPKB70013
Hope it will solve your issue ....
All teh best !!

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#

Applying BASIS support package 14 on IDES (DB2 & Windows)

Hi all,
   I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSALC ".
at happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSALC " in include "LSALCU65
   " in
line 1:
"Function "SALC_INFO_GET_TREE" not found in Function Library."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Can anyone of you help me on this issue.
AWAITING REPLY
Thanks

>    I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
There are a few known issues with KB70014, those are documented in
Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Markus

RSPOR_SETUP = Different ABAP and Java support packages.

Hi all,
We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
Different ABAP and Java support packages. Combination of support packages invalid
And with some more clicking we find this:
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
   ABAP Support Package:                  13
   Java Support Package:                   0
On the Java stack we see (among others) these components:
sap.com       BI-IBC       7.00 SP12 (1000.7.00.12.0.20070509050058)
sap.com       BI_MMR       7.00 SP12 (1000.7.00.12.0.20070507084106)
sap.com       BI_UDI       7.00 SP12 (1000.7.00.12.0.20070507084125)
sap.com       BI-BASE-S       7.00 SP12 (1000.7.00.12.11.20080324092518)
sap.com       BI-WDALV       7.00 SP12 (1000.7.00.12.1.20071105133039)
sap.com       BI-REPPLAN       7.00 SP12 (1000.7.00.12.3.20080104101916)
So I believe all components are correctly installed.
What are we doing wrong?

Hello.
Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
I hope I can be helpful.
Thanks,
Walter Oliveira.

How to Apply GP India Packages in peoplesoft

Hi All,
Can you please tell me how to apply GP INDIA packages (Rule & Non-Rule) in detail?
Thanks in Advance.
Regards,
Siva Prasad B

Hi Siva,
For any country, the procedure is to
RULES:
1. Run the Rules scripts (named typically as cc999999_imp.dms; cc is Country code; 999999 is the package/Bundle ID)
2. Run the Compare process part for Rules package from PIA
3. If no errors found, run the Upgrade process from the PIA (the same page)
Anyhow, I strongly recommend you to read 'Using Utilities' in this book(http://download.oracle.com/docs/cd/E20215_01/hr91pbr1/eng/psbooks/hgpy/book.htm).
Edited by: Rao on Sep 20, 2011 8:03 AM

How to find and apply new Support Packages?

Hi to everyone.
The system is SAP R/3 Enterprise (may 4.7 ext2?)
The spam version is 6.20/0020
i have to update the support packages, so i went on https://websmp107.sap-ag.de/swdc, but i dont know what SP i have to download.
the situation is (so i have to update all of them?):
SAP_BASIS     620     0059     SAPKB62059
SAP_ABA     620     0058     SAPKA62058
SAP_APPL     470     0018     SAPKH47018
SAP_HR     470     0058     SAPKE47058
EA-IPPE     200     0004     SAPKGPIB04     .
PI     2003_1_470     0002     SAPKIPZH52
PI_BASIS     2003_1_620     0002     SAPKIPYH52
ST-PI     2005_1_620     0002     SAPKITLQG2
EA-HR     200     0015     SAPKGPHB15
LSO     200     0018     SAPK-200PIINLSO

For eg. for 4.6C you have upto 52 in BASIS ,ABAP,and cross application components.
you download 43..44..52 and using SPAM you can upload from front end or you can uncar them on the App.server.
However, during the course of implementing patches, during the SPDD and SPAU phase system gives the option to retain the changes that are made to standard programs / objects / tables etc or to reset the objects to SAP standard objects. It is during these changes only that the functional consultant has to study the program/changes which are done and the impact of the changes.So when you come through this SPDD or SPAU phase you have to make sure from your ABAPers and functional consultants regarding whether to reset all to original or retain the changes.This is crucial otherwise you will impair your business unknowingly.
Click on the info button beside the support pack name and see the dependencies.
The order of applying patches will be BASIS,ABAP,Cross application components,HR etc...
And finally it's not the case that we should go for applying a support pack because it's available at SAP market place.

Java Add-in System Copy - same Java Support Package levels ?

Hi,
I'm looking at performing a standard SAP Netweaver 04 SAP Web Application Server system "refresh" procedure. I plan to copy the production system ( SAP WAS 640 ABAP+Java addin )to an already installed QA system that was installed originally exactly the same as Prod. Both have the same components installed and the ABAP stack Support package levels are identical. What I've found is that the Java Add-in Support package levels vary. Is it possible to perform the system copy "refresh" if the Java components differ. ( Prod J2EE is 640 SP13, QA is SP14 and Adobe & ESS/MSS components differ ).
I've looked through the system copy guides and the NW04 SR1 system copy OSS note 785848, but can't find anything about this situation.
Hopefully someone else out there can tell me if it's possible, without first patching Production to the same levels as the QA system being overwritten.
Regards,
Brian.

Hello,
u can do that w/o applying the patch ..but after doing system copy u have latest SP13 as of u r PRD server instead of SP14 in QA....if required then u can apply it again in QA....SP14.
So if u not got my point then tell me...
thanks..
reward points..

How can I get Support Packages for SAP NSP 2004s?

Hi together,
I have installed the SAP NetWeaver 04s Sneak Preview.
How can I get the support package stacks (SP 6 and SP 7)?
I have only a small OSS-User for 'Freie Berater' (Free Consultants). With that OSS-User it is not possibel to download the the support package stacks SAP Support Portal.
Kind regards, Eva

Hi Daniel,
the sp-level is 5. You can find it via system/status/ in the section 'SAP System data' (klick at the detail-icon).
Web Dynpro for ABAP works with that version. But I would like to have the newest sp-level. Our Web Dynpro teacher gave us some example sources and said that some of them might need sp 6. But I didn't test it.
I have another question: Have you worked in the MARK project a few years ago? There was a collegue named Daniel Kotte.
Kind regards, Eva

SPAM--How to cleanup new support packages list

Hi,
When i run SAPM T-code and click on "New Support Packages" ,it diaply
too many packages with status "not imported"..
i need to remove all of them make this empty.
How would i remove them from the list?
Thanks
Ram

Good afternoon, Ram - While in SPAM, you can go to "Environment --> Electronic Parcel Service --> Goto --> Inbox". Then you can put a check mark next to the support packages that you want to delete. This removes the support package from the queue, so if you want it back in you would have to reload the data file and cofile and then in tcode SPAM go to "Support Packages --> Load packages" and either load them again from your desktop or ftp the files to the "/usr/sap/trans" directory and use SAPCAR to unpack them again.
I hope this helps!
Regards,
Blair Towe

How to apply ERP enhancement packages?

Any document around? Please help. Thanks!

Hi ,
I want to install EHP3 on My ERP system.
Installation document on EHP3 says that .
1. Make sure that you have installed at least SAP Solution Manager 4.0 Support Package 13.
2. Update the Solution Manager Content to at least ST-ICO 150 Support Package 13.
But My Solman system 4.0 has only SP level 7. and ST-ICO -level : 6.
Is it possible to download the EHP3 from My solman server (SP7).
Please guide me how to download EHP3 for ECC6.
Thanks and Regards
Thirumal.

How to apply java .class to html?

For java .class file, I am sure I follow exactly what the tutorials said to apply it to htm file but it just doesn't work. I applied it by adding the applet element with the .class file as the attribute. Is that wrong? I googled for it and an article said it is probably because of wrong .class file name. I am very sure it is not the case for me and it must not be upper or lower case thing. Any hint to fix it?
My code is like this:
<applet code="file_name.class" name=file_name archive=file_name.jar height="x" width="y"></applet>

try this:
<applet code="whatever.class" width=100 height=100>
</applet>
Works for me.

How to apply java support packages.

Similar Messages

Maybe you are looking for