SUM for applying support package stack
Dear SAP Guru's,
We are trying to apply a support pack maintenance stack sp04 on a PI 7.3 with EHP1 system using SUM
In the road map step "Specify Credentials" we have got a error saying "could not detect executable directory from profiles for system XID"
Recently we have upgraded our system from 7.0 to 7.3 with ehp1, after the upgrade we have observed that the start profile is merged with instance profile.
A screen shot of the error message is attached.
DIR_EXECUTABLE in our system is /usr/sap/<SID>/DVEBMGS00/exe and the same is available as profile parameter in the instance profile.
Kindly help us to solve this error and continue the update
Thanks,
Balaji S
Hello Balaji,
As per SAP note 1557404
Profile Merging During Update with Regard to Certain Target Releases
The Software Update Manager (SUM) asks you during an update if you want
to merge the start profile with the instance profile and if you want to
switch to a new file system structure.
Only use this option when updating to SAP NetWeaver 7.3 including
enhancement package 1.
Do not use this option if you update to SAP Business Suite 7i2011 (based
on SAP NetWeaver 7.0 EHP3), otherwise subsequent software logistic
processes might not work properly.
Check if sapstartsrv has been defined to start with START profiles
and if these do not exists as they are merged with the instance profiles.
If so, the option here could be replace the START profiles with Instance
profiles. Also please check if sapstartsrv processes on the OS are
running with START profiles, if yes, you need to restart them after
modifying sapservices file so that they get started with the instance
profiles. Once this is done, issue should be gone.
regards,
Paul
Similar Messages
-
Syntax Error while applying support package stack 8
I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors SYNTAX_ERROR
Date and Time 23.07.2009 14:09:27
Short text
Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
Error in the ABAP application program.
The current ABAP program "SAPLSCR2" had to be interrupted because it con
a statement that cannot be executed.
In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
errors occur:
"The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
"d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
"PTEXT"."
Author and last person to change the include are:
Author "SAP "
Last changer "SAP "
Error analysis
The following syntax error was found in the program
CL_DYNPRO_PROPERTY_BAG========CP :
"The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
"d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
"PTEXT"."
Trigger Location of Runtime Error
Program SAPLSCR2
Include LSCR2U47
Row 31
Module type (FUNCTION)
Module Name RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *" REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *" REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *" REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *" REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *" REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *" REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *" REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16 l_prop_list type prop_list,
17 l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23 clear l_prop_list.
24 clear l_prop.
25 l_prop-name = sprop_c_tag_textfield_name.
26 l_prop-syntax = sprop_c_syntax_content .
27 l_prop-value = p_textfield.
28 append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>> call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32 exporting
33 prop_list = l_prop_list
34 importing
35 properties = l_string.
36 * Property-Eintrag zusammensetzen
37 clear l_prop.
38 l_prop-name = sprop_c_tag_textfield.
39 l_prop-type = sprop_c_type_string.
40 l_prop-syntax = sprop_c_syntax_content .
41 l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43 read table p_prop_list transporting no fields
44 with key name = l_prop-name.
45 if sy-subrc = 0.
46 modify p_prop_list index sy-tabix
47 from l_prop.
48 else.
49 append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu -
Post Processing Steps after Support Package Stack Application
I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server). We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems. We also applied the J2EE stack and appropriate SCA files to the NWDI server.
After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them). Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE. Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files. We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type. Is there a checklist or something that anyone has for steps to perform after the application of the support packs?I think I'm missing something. Now I see the code and DC's inside the DTR. However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them). Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR. What things can I look at to determine what I'm missing here?
Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA. We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR. After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws). When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
Message was edited by:
Eric Vota -
Hi all,
I want to request SAP the latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0, is it possible & how to do it?
Thanks,
Toan DoHi Toan,
It's possible to order them or download them from SAP Marketplace
http://service.sap.com/swdc
Regards
Juan -
Support Package Stacks Best Practice
Good morning all,
We're at the start of a mySAP ERP implementation and we'd like to set a strategy as regards how we implement SP Stacks.
We are only using the base mySAP ERP functionality; we're not using the HR, Retail, Public Services extensions. Because of this, I'd like to know what is the best practice for applying SP Stacks in our environment.
Do we need to install the SPs for the HR, Retail, etc.. extensions to keep the SP Stack consistent, or do we simply install only the base SPs that we require?
Any help is greatly accepted.
Thx,
Arwel.Hi Kobby,
Thanks for your information.
The Support Package Stacks for 7.0 version is 15
I would like to know the Stacks for SAP Solution Manager - 4.0
Version.
Thanks and Regards,
Sateesh.Kandula -
Support Package Stack NetWeaver vs. ERP
When I use Maintenance Optimizer to get the latest Support Package Stack (13) from my ERP system (ECC 6.0), it does not get the latest kernel and Basis support packages. After applying, the Early Watch report still shows the kernel is out of date. However, if I go through Service Marketplace and get the latest NetWeaver Stack (16), it gets the latest kernel and Basis package. After applying, Early Watch states that the Kernel is up to date. How should the support package stacks for an ECC 6.0 system be applied - both ERP and NetWeaver stacks or ERP stack only which is not the latest?
Hi,
Its Your requirement, So its better you should opt it for.
Mostly the ecc6 would contain all the components even like sap_hr and others,
but your nw stack doesn't have this.
Also you have to select the kernal like you have to make the appropriate settings in the selection page
which will get you the kernal files in the stack.
Regards,
Vamshi. -
MAM Not Working After Applying Support Package
We have been lived with MAM 2.5 with SP16 for almost a year now. We recently applied support package 19 for ABAP and J2EE stacks but MAM stopped working right after that. To fix the problem we had to do the following steps:
1. Disable all SyncBO
2. Regenate all SyncBO
3. Run Replicate Database
4. Enable all SyncBO
5. Delete MAM 2.5 client by WebConsole for all PDA (over 100 devices)
6. Re-Assign MAM 2.5 client back to PDA from WebConsole
My question is do we have to perform those steps above every time we are applying new support package? If it is a case, it's very time consuming because we have to manually perform step 5-6 for every users.
Does anyone have seen or experience this scenario before? Your comment is highly appreciated.
Regards,
Dai LyHi Karthik,
Let me clarify on "Not working"
It showned synchrozation successuffly but no data transfer between client and middleware and vs. For instance, the user never receive any new work orders, or their times never got transfered back to R/3. Even though, there is no error on the client.
It appear that step 1-4 are required otherwise, you get ABAP Runtime error (using ST22):
Runtime Error CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 02/07/2007 08:12:27
After we performed step 1-4 but there were data transfer between client and R/3. The only way to get it working, we had to delete client and re-assign MAM 2.5 back to each users.
No, we didn't apply client patch SP19. We are still using SP16.
As we speak, everything is working because we had to re-assign MAM 2.5 for every users. but I hope we don't have to do this next time we apply another Support Package.
Thanks.
Dai Ly -
Maintenace optimiser, support package Manager, Support package stack
HI all,
Could you please enlighten me the differences among
Maintenance Optimizer,support package Manager, Support package stack
And the purpose and most importantly the documentation to be able to use them
in case of implementation phase (In case of a fresh ECC 60 Production version)
Thank youMaintenace optimiser is used in solution Manager to Approve the Patch that you need to download fron Service market place
Support package stack is the collection of patch for a release.
Support package Manager is SPAM/SAINT used to apply support pack.
If you want some thing else please revert back
thanksd Rishi Abrol -
Error while applying support packages
Hi,
I was applying support packges for NW 7.0 EHP2 for the components SAP BASIS/ABAP/PI BASIS & BW, the support package level was 02, I have downloaded 03,04,05,06 for all the above four components. While updating spam/saint update I got the above error, displayed below. But even while applying support packages I got a list of errrors.
1.
Category: Abap programming error
Runtime error: call_function_parm_unknown
CX_SY_DYN_CALL_PARAM_NOT_FOUND
abap program: RSSPAM07
Function parameter "IV_IMP_SCENARIO" in unknown
this first error displayed after applying SPAM/SAINT update.
2. The import was stopped, since an error occured during the phase IMPORT_PROPER, which the support package Manager is unable to resolve without your input
The following details help you to analyse the problem:
Error in phase : IMPROT_PROPER
Reason for error:
Return code:
Error Message:
Please provide any solution as soon as possible....The details of SLOG
START CMDIMPORT NG1 L 20120227162812 SHABZ BasisTrn3 20120227162811973
STOP CMDIMPORT NG1 L 20120227162813 SHABZ BasisTrn3 20120227162811973
START imp all NG1 20120227162821 SHABZ BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT NG1 H 20120227162822 SHABZ BasisTrn3 20120227162821661
STOP DD IMPORT NG1 H 20120227162839 SHABZ BasisTrn3 20120227162821661
START DD ACTIVATION NG1 A 20120227162839 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 J 20120227162839 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 J 20120227162925 SHABZ BasisTrn3 20120227162821661
STOP DD ACTIVATION NG1 A 20120227162925 SHABZ BasisTrn3 20120227162821661
START DISTRIBUTION OF DD-O NG1 S 20120227162925 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 S 20120227162925 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 S 20120227162929 SHABZ BasisTrn3 20120227162821661
STOP DISTRIBUTION OF DD-O NG1 S 20120227162929 SHABZ BasisTrn3 20120227162821661
INFO TBATG CONVERSION OF NG1 N not needed SHABZ BasisTrn3 20120227162821661
START MOVE NAMETABS NG1 6 20120227162929 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 P 20120227162929 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 P 20120227162935 SHABZ BasisTrn3 20120227162821661
STOP MOVE NAMETABS NG1 6 20120227162936 SHABZ BasisTrn3 20120227162821661
START MAIN IMPORT NG1 I 20120227162936 SHABZ BasisTrn3 20120227162821661
STOP MAIN IMPORT NG1 I 20120227163023 SHABZ BasisTrn3 20120227162821661
START TBATG CREATION OF EN NG1 n 20120227163024 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 Y 20120227163024 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 Y 20120227163034 SHABZ BasisTrn3 20120227162821661
STOP TBATG CREATION OF EN NG1 n 20120227163034 SHABZ BasisTrn3 20120227162821661
START EXECUTION OF REPORTS NG1 R 20120227163035 SHABZ BasisTrn3 20120227162821661
START tp_getprots NG1 R 20120227163035 SHABZ BasisTrn3 20120227162821661
STOP tp_getprots NG1 R 20120227163202 SHABZ BasisTrn3 20120227162821661
STOP EXECUTION OF REPORTS NG1 R 20120227163202 SHABZ BasisTrn3 20120227162821661
INFO EXECUTION OF STANDAR NG1 9 not needed SHABZ BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all NG1 0004 20120227163203 SHABZ BasisTrn3 20120227162821661
START CMDIMPORT NG1 L 20120227164418 SHABZ BasisTrn3 20120227164416991
STOP CMDIMPORT NG1 L 20120227164454 SHABZ BasisTrn3 20120227164416991
START DD IMPORT NG1 H 20120227165608 SHABZ BasisTrn3 20120227165607479
STOP DD IMPORT NG1 H 20120227170309 SHABZ BasisTrn3 20120227165607479
START DD ACTIVATION NG1 A 20120227170313 SHABZ BasisTrn3
START tp_getprots NG1 J 20120227170313 SHABZ BasisTrn3
STOP tp_getprots NG1 J 20120227171206 SHABZ BasisTrn3
STOP DD ACTIVATION NG1 A 20120227171206 SHABZ BasisTrn3
START imp all NG1 20120227171208 SHABZ BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O NG1 S 20120227171208 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 S 20120227171208 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 S 20120227171303 SHABZ BasisTrn3 20120227171207614
STOP DISTRIBUTION OF DD-O NG1 S 20120227171304 SHABZ BasisTrn3 20120227171207614
START TBATG CONVERSION OF NG1 N 20120227171304 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 N 20120227171304 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 N 20120227171307 SHABZ BasisTrn3 20120227171207614
STOP TBATG CONVERSION OF NG1 N 20120227171307 SHABZ BasisTrn3 20120227171207614
START MOVE NAMETABS NG1 6 20120227171307 SHABZ BasisTrn3 20120227171207614
START tp_getprots NG1 P 20120227171308 SHABZ BasisTrn3 20120227171207614
STOP tp_getprots NG1 P 20120227171755 SHABZ BasisTrn3 20120227171207614
STOP MOVE NAMETABS NG1 6 20120227171755 SHABZ BasisTrn3 20120227171207614
START MAIN IMPORT NG1 I 20120227171756 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP MAIN IMPORT NG1 I 20120227195335 SHABZ BasisTrn3 20120227171207614
START TBATG CREATION OF EN NG1 n 20120227195335 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
START tp_getprots NG1 Y 20120227195335 SHABZ BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP tp_getprots NG1 Y 20120227195521 SHABZ BasisTrn3 20120227171207614
STOP TBATG CREATION OF EN NG1 n 20120227195521 SHABZ BasisTrn3 20120227171207614
INFO EXECUTION OF STANDAR NG1 9 not needed SHABZ BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all NG1 0903 20120227195522 SHABZ BasisTrn3 20120227171207614 -
Support package stack 11 (Java and ABAP)
Does anybody have any experience with the latest support package stack 11 already? Are there some problems solved, and more important: are there new errors introduced?
Thanks for your help.Hi Deepu,
Thanks for your reaction. I'm familiar with this OSS note. I'm mainly curious to customer experiences who have already implemented it. This SPS will solve some of our problems, but we're a little scared for the new errors that will be introduced with it.
Guus -
Support package stacks: Do we need to import all SP in the stack?
Hi all.
We are about to import Support Package Stack 13 into our ERP 6.0 system. The SPS includes a lot of support packages for software components such as IS-OIL, IS-UT and other IS-* components.
These components are inactive in our system, and are not used. However, I know that the recommendation is to import the complete stack.
I am therefore having some doubts if it is wise to import the IS-* related support packages.
Please advise.
Regards,
ThomasThank you for your feedback.
However, I would like to ask if the only argument is to follow SAP recommendation? What risks are we running if we do not implement the IS component support packages?
As the IS-* components are not active, I don't see how not importing these support packages will cause "inconsistence" in the system. Also, it would reduce the total number of support packages that needs to be included.
I am generally positive to following SAP's recommendations, but in this case we are are in a situation where we need to lift the SAP system from SPS 8 to SPS 13 in one operation. That includes a massive amount of support packages, and possibly a lot more time than the timeframe we have available.
Regards,
Thomas -
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,
Cheungdefaulttrc.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# -
AccAD 2.2: Support Package Stack 02 available
Hello,
Support-Package-Stack 02 for AccAD 2.2 seems to be released now. At least I can see it in the Download area on SMP :o)
But there are no notes about it yet.
Will there be Release notes for SPS02, which bugfixes and new features are in it?
Best regards,
Stephan RoßmanithHi Stephan,
The official release is expected for November 15th in which the exepcted updates user manual and release notes should also be available within a weeks timeframe.
All the Best,
Smadar -
Support Packages stack ERP HR level
Hi,
I am requesting information about what the ERP HR stack level is for the common SAP ERP 6.0 Support Package Stack level 17 which is comming out week 13, 2010?
Regards,
Jesper
SAP Project Manager from DenmarkDear customer,
I am sorry but this is not a Service Marketplace issue. Would you please be so kind to place this question in the Area of the BASIC Team or to open a ticket under component BC-UPG
Thanks and best wishes
Dragana Manojlovic
SAP Senior Support Consultant II -
DDIC_ACTIVATION ERROR WHILW APPLYING SUPPORT PACKAGES
Hi all,
While applying support package(KB62019),i got error(DDIC_Activation)..
How to resolve it?
Thanks in advance.Hi,
Which support package are you applying ? Have a look at these notes: 782140 and 447925.
Search for SAPKB62019 in this note and you will get a solution to that. The note refers to some more notes. Please follow the instuctions in the note carefully.
Cheers,
Sunil
PS: Reward points for helpful answers.
Maybe you are looking for
-
I just update itunes for latest version. Now I can't open it on windows 7- 64 bits. I get an erro: Cant find the entry point of the procudere sqlite_wal_checkpoint.. Windows error 127. What can I do...???
-
A whole lot of ITUNES files appear to have been imported into my Iphoto... I am not able to delete or trash them. They show up throughout the library. Anyone know how to get rid of them?
-
Hi Can you please inform me whether its possible to stop the posting in a cost center after it has exceeded the budget, like we do it for internal orders, if yes then kindly infrom me the way (transaction codes) by which we could do that. Regards Ash
-
I am trying to locate a phone, but it keeps telling me the device is offline. What does that mean and why won't the phone track.
-
Java.lang.OutOfMemoryError solved (was NOT a leak)
Alright I'm just posting this to hopefully save someone some time in the future. This was a bug that dragged out for over a year. An application would be deployed to a production app server and low and behold OutOfMemoryError's would start to be thro