BRAIN 605 when calling Workload analysis in Solman 4.0 EHP1

Hello!
I am running an solution Manager system with release 4.0 EHP1 (brandnew).
I have the problem that some BI functionalities on the SMD do not work correctly.
´For example I am calling the following application:
E2E Analysis -> select a system -> klick on workload analysis -> chose the second tab Application Server ABAP. Here for example in the workload summary I get the folloing eror message:
Technical Information for Message:
The requested query 0CCMSMTPH/0CCMSMTPH_WA_Q0001_H does not exist on the current server
Notification Number BRAIN 605
Other queries like for example the User load are working. Does someone have an explanation? How can I check if the query really is not existing of if it has a problem?
Regards
Bernd

done- I had to run the report CCMSBI_SETUP_E2E, CCMSBISETUP is not enough

Similar Messages

WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection

Hi all SDNers,
Help is needed on error "WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection".
This error occured on RCA -> Extractor FWK administration and go to managed system (PI) and from the log, i can see some extraction failed due to error message " Error when opening an RFC connection"
consequently, JAVA performance data is not appearing in RCA -> workload analysis but work fine for ABAP and adapter engine.
I've followed below notes and perform the troubleshooting step by step by still to no avail:
Note 1332428 - Missing data in service sessions from BI/CCDB
Note 1257308 - FAQ: Using EarlyWatch Alert
Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP27
Note 1265070 - Diagnostics - Setup of Managed Systems
Note 1010428 - End-to-End Diagnostics
http://wiki.sdn.sap.com/wiki/display/SMSETUP/WorkloadAnalysis-Noapplicabledatafound
steps that have performed:
restarted agent
enlarge RFC resource cap for solmandiag and none
delete entire SID in SMSY and pull again from SLD, re-setup managed system
restart PI system
i've spent 2 days on troubleshooting this issue but lack of information in SMP and SDN, even in google.
in table E2E_EFWK_STATUS and extractor E2E_JAVA_EXTRACTOR_IF, i see all WLI_ID ended with RC 96, MESSAGE = Error when opening an RFC connection and LASTRECORDS = 0
I strongly believe this is the issue that causing no applicable data found for JAVA data.
fyi, we are on SOLMAN EHP1 SPS27.
Any kind advise is most welcome.
Thanks,
Nicholas Chang

Gosh! at last i found the solution!!
I appreciate those who tried to help and i''m sharing the solution as i believe this is the purpose of SDN Forum and help others Netweaver Chap who facing the same problem:
Problem faced:
Extractor failed intermittently for WORKLOAD ANALYSIS (Introscope Data) due to error message "Error when opening an RFC connection"
Due to the above error, performance data is not available in RCA workload analysis for J2EE engine.
Possible Solution:
1) Ensure both webadmin & SOLMANDIAG RFC working fine -> SM59 -> TCP/IP
2) go to SE16 -> E2E_RESOURCES and change the resourcecap to 10 for SOLMANDIAG
3) go to /smd/services -> Diagnostic System -> Advanced Setup -> Abap connectivity -> Connection Configuration and change server count to 10
4) Restart webadmin (step 3 & 4 can perform in VA too)
5) set gw/keepalive & gw/reg_keepalive to value 0 in RZ11 (without reboot of instance)
5) again go to SM59 -> TCP/IP -> SOLMANDIAG and put in the gateway host and gateway service correctly, don't leave this empty!!!! -
> This is the main solution to solve intermittent failed RFC for extractor.
Now, go back and monitor the extractor log and you should see no RFC error anymore and wait for 1 hour for the data to populate.
Thanks!
Nicholas Chang,

After BI 4.1 configuration in SOLMAN - error message "The systems you selected do not contain any software components currently supported by E2E Workload Analysis"

Hi All,
I'm trying configure E2E monitoring. I configured all necessary steps, I can see my BI 4.1 system in SLD, also in SOLMAN, all “lights” are green. But if I start Root Cause Analysis>> Ent-to End Analysis>> My system>> Workload Analysis, I see this error "The systems you selected do not contain any software components currently supported by E2E Workload Analysis".

It would be better if you can raise the question at Remote Supportability and Monitoring Tools
and or comment in the blog post How to generate and consume an E2E trace with BI4.x (for non-SolMan landscapes)
created by Toby Johnston
Do go through the note 1871260 - The systems you selected do not contain any software
components currently supported by E2E Workload analysis for SAP HANA
Hope they help.

E2E Workload Analysis for BI

Hi All,
Currently we are searching for BI - IP workload analysis tools. I come to know that SolMan Diagnostic tool E2E Workload Analysis for BI useful somewhat to measure the work load. Kindly anybody can tell me
1. Is this tool works for JAVA environment or not
2. How it is useful for BI-IP workload analysis
3. Is there any tools like SolMan diagnostic tool.
4. If we install this tool in SolMan what is the impact.
Thxs,
KVA

This is what I get from Application log (slg1) when I try to drill down on system BIJ (java system) and the page under Workload Analysis do not display (WA-Overview) is ok:
SELECT { [Measures].[0SMD_AVG], [Measures].[0SMD_MAX], [Measures].[0SMD_EXS
] } ON 0, NON EMPTY [0SMD_METY].MEMBERS ON 1 FROM [0SMD_MPEH/0SMD_MPEH_WA_Q
0008_H] SAP VARIABLES [0SMD_V_SID] INCLUDING "BIJ_2" [0SMD_V_TIHMFROM] INCL
UDING >= "201008270000" [0SMD_V_TIHMTO] INCLUDING <= "201008272359" [0SMD_V
INFOPR] INCLUDING "0SMDPERH" [0SMD_V_INFOPR] INCLUDING "0SMD_PE2H" [0SMD_
V_MTYPEM] INCLUDING "IVIEWS" [0SMD_V_MTYPEM] INCLUDING "BI RUNTIME SERVICE"
Value "BIJ_2" for variable "E2E SID Variable" is invalid
Type:E, Id:BRAIN, Number:643, System:SMDCLNT001
I applied the note Note 1301656 even if we are already sp23. I also regenerated the query 0SMD* in bi client.
What does Value "BIJ_2" for variable "E2E SID Variable" is invalid mean and how to correct this?

Workload Analysis tab is missing in E2E Anaysis

Hi Guru,
I am in process of generating EWA reports for portal ,below are the steps I have completed successfully.
1. SMD agent installation on portal.
2. Defined portal system in SMSY.
3. completed SOLMAN_SETUP.
4. Completed Setup Wizard for managed system.
5. Deploy IS agent via SDM in Solman.
6. Introscope agent setup done for managed system
7. Managed system data is visible in IS Enterprise Manager.
When I checked t code solman_workcenter->RCAtab-> E2E Anaysis->selected the portal system i cant find Workload Analysis tab i.e Workload Analysis tab is missing could you please help me to resolve this issue.
System Configuratoi: SAP EHP 1 for SAP Solution Manager 7.0 and portal is netweaver 7.0
Thanks
Abullais

Hi,
Kindly check security guide for RCA authorization,
https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718044&_SCENARIO=01100035870000000202
It may be due to authorization issue.
Regards,
Karthik

SMD on SP15: no data for E2E Workload Analysis are shown

Hello!
I have successfully run Setup Wizard for the satellite solution "EP Portal on 6.40".
Unfortunately no data for E2E Workload Analysis are shown since more than one month.
I use SAP Solution Manager with SP 15, BI CONT 9
I have implemented the following SAP notes:
1088163, 1107804, 110782, 1119766
The jobs E2E_EXTRACTOR_CONTROLLER are running without errors.
Enclosed one of those for portal solution:
09.04.2008 E2E: Extractor Controller 1
EC: 09.04.2008 13:05:52 UTC Extractor Controller started for SID B11
EC: 09.04.2008 15:05:52 CET Installation Number 0020198811
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 13:05:52 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:52 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:52 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:54 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/APPLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/APPLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/APPLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/DUMP_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
09.04.2008 E2E: Extractor Controller 2
ME: 13:05:54 UTC Calling Extractor /SDF/DUMP_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/DUMP_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/SYSLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/SYSLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/SYSLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/UPDATE_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/UPDATE_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/UPDATE_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
09.04.2008 E2E: Extractor Controller 3
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:55 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:55 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 13:05:56 UTC Receiving return code 6 from
E2E_JAVA_EXTRACTOR_IF
ME: Error:
DATA_RETRIEVAL_EXCEPTION
EC: 13:05:56 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:57 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:57 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR
09.04.2008 E2E: Extractor Controller 4
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 08.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 08.04.2008 12 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 08.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR ,
Extractor Class:
ME: 13:05:58 UTC Receiving return code 98 from
/SDF/IDOC_THROUGHPUT_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:58 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:00 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_C_TRANSPORTS
09.04.2008 E2E: Extractor Controller 5
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:01 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
09.04.2008 E2E: Extractor Controller 6
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:06:02 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:02 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F55_XI_IDOC_ADAPTER
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:02 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:02 UTC Calling Extractor F55_XI_IDOC_ADAPTER
ME: No Data Found.
ME: 13:06:02 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_C_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
09.04.2008 E2E: Extractor Controller 7
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_SSR_EXTRACTOR_IF
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: Local Execution of Extractor.
EC: ME called in Multi-Mode.
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor E2E_SSR_EXTRACTOR_IF ,
Extractor Class:
E2E_SSR_EXTRACTOR_0CCMSATPH
ME: 13:06:06 UTC Receiving return code 0 from
E2E_SSR_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:06 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
Any helpful information will be appreciated
regards
Thom

Same problem being observed in our Solman system (SP15). Below are the errors observed in the spool output of E2E framework jobs,
1] ME: Data Loader Error occurred.
   EC: 21:05:44 UTC Main Extractor raises exception. No Data returned by extractor.
2] No action - TSL parameter detected.
   This extractor is not allowed to run outside time frame
3] ME: 21:05:45 UTC Receiving return code    98   from
   /SDF/UPDATE_EXTRACTOR
   ME: Error:
   ME: Error - No RFC Destination maintained for remote execution.
   EC: 21:05:45 UTC Main Extractor raises exception. No Data returned by extractor.
4] ME: Error:
   DATA_RETRIEVAL_EXCEPTION
   EC: 21:05:46 UTC Main Extractor raises exception. No Data returned by extractor.
Tried referring E2E workload analysis guide...no use..the issues have not been covered in that.

Diagnostics Workload Analysis - Java Memory Usage gives BI query input

Dears
I have set up diagnostics (aka root cause analysis) at a customer side and I'm bumping into the problem that on the Java Memory Usage tab in Workload analyis the BI query input overview is given
Sol Man 7.0 EHP1 SPS20 (ST component SP19)
Wily Introscope 8.2.3.5
Introscope Agent 8.2.3.5
Diagnostics Agent 7.20
When I click on the check button there I get the following:
Value "JAVA MEMORY USAGE" for variable "E2E Metric Type Variable" is invalid
I already checked multiple SAP Notes like the implementation of the latest EWA EA WA xml file for the Sol Man stack version.
I already reactivated BI content using report CCMS_BI_SETUP_E2E and it gave no errors.
The content is getting filled in Wily Introscope, extractors on Solution Manager are running and capturing records (>0).
Did anyone come accross this issue already?
ERROR MESSAGE:
Diagnosis
Characteristic value "JAVA MEMORY USAGE" is not valid for variable E2E Metric Type Variable.
Procedure
Enter a valid value for the characteristic. The value help, for example, provides you with suggestions. If no information is available here, then perhaps no characteristic values exist for the characteristic.
If the variable for 0DATE or 0CALDAY has been created and is being used as a key date for a hierarchy, check whether the hierarchies used are valid for this characteristic. The same is valid for variables that refer to the hierarchy version.
Notification Number BRAIN 643
Kind regards
Tom
Edited by: Tom Cenens on Mar 10, 2011 2:30 PM

Hello Paul
I checked the guide earlier on today. I also asked someone with more BI knowledge to take a look with me but it seems the root cause analysis data fetching isn't really the same as what is normally done in BI with BI cubes so it's hard to determine why the data fetch is not working properly.
The extractors are running fine, I couldn't find any more errors in the diagnostics agent log files (in debug mode) and I don't find other errors for the SAP system.
I tried reactivating the BI content but it seems to be fine (no errors). I reran the managed system setup which also works.
One of the problems I did notice is the fact that the managed SAP systems are half virtualized. They aren't completely virtualized (no seperate ip address) but they are using virtual hostnames which also causes issues with Root Cause Analysis as I cannot install only one agent because I cannot assign it to the managed systems and when I install one agent per SAP system I have the message that there are already agents reporting to the Enterprise Manager residing on the same host. I don't know if this could influence the data extractor. I doubt it because in Wily the data is being fetched fine.
The only thing that it not working at the moment is the workload analysis - java memory analysis tab. It holds the Key Performance Indicators for the J2EE engine (garbage collection %). I can see them in Wily Introscope where they are available and fine.
When I looked at the infocubes together with a BI team member, it seemed the infocube for daily stats on performance was getting filled properly (through RSA1) but the infocube for hourly stats wasn't getting filled properly. This is also visible in the workload analysis, data from yesterday displays fine in workload analysis overview for example but data from an hour ago doesn't.
I do have to state the Solution Manager doesn't match the prerequisites (post processing notes are not present after SP-stack update, SLD content is not up to date) but I could not push through those changes within a short timeframe as the Solution Manager is also used for other scenarios and it would be too disruptive at this moment.
If I can't fix it I will have to explain to the customer why some parts are not working and request them to handle the missing items so the prerequisites are met.
One of the notes I found described a similar issue and noted it could be caused due to an old XML file structure so I updated the XML file to the latest version.
The SAPOscol also throwed errors in the beginning strange enough. I had the Host Agent installed and updated and the SAPOscol service was running properly through the Host Agent as a service. The diagnostics agent tries to start SAPOscol in /usr/sap/<SID>/SMDA<instance number>/exe which does not hold the SAPOscol executable. I suppose it's a bug from SAP? After copying the SAPOscol from the Host Agent to the location of the SMD Agent the error disappeared. Instead the agent tries to start SAPOscol but then notices SAPOscol is already running and writes in the log that SAPOscol is already running properly and a startup is not neccesary.
To me it comes down the point where I have little faith in the scenario if the Solution Manager and the managed SAP systems are not maintained and up to date 100%. I could open a customer message but the first advice will be to patch the Solution Manager and meet the prerequisites.
Another pain point is the fact that if the managed SAP systems are not 100% correct in transaction SMSY it also causes heaps of issues. Changing the SAP system there isn't a fast operation as it can be included in numerous logical components, projects, scenario's (CHARM) and it causes disruption to daily work.
All in all I have mixed feelings about the implementation, I want to deliver a fully working scenario but it's near impossible due to the fact that the prerequisites are not met. I hope the customer will still be happy with what is delivered.
I sure do hope some of these issues are handled in Solution Manager 7.1. I will certainly mail my concerns to the development team and hope they can handle some or all of them.
Kind regards
Tom

Error when call webservice on servlet

Hi All,
I'm having a problem when calling webservice inside the servlet on the WebLogic environment.
My code:
* Webservice:
package ws;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Date;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
@WebService
public class getData {
public getData() {
super();
@WebMethod
public String getHello() {
return "HELLO HELLO";
private Connection getConn() throws NamingException, SQLException {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource)ic.lookup("jdbc/hnxwebsite");
//System.out.println("POOL !!!!");
Connection con = ds.getConnection();
con.setAutoCommit(false);
return con;
@WebMethod
public String getIndexData(@WebParam(name="param") String param) {
StringBuffer sb = new StringBuffer();
String sql =
"Select * From idx_index_info iii where iii.index_code= ?";
Connection con = null;
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
con = getConn();
pstmt = con.prepareStatement(sql);
pstmt.setString(1, param);
rs = pstmt.executeQuery();
int columnCount = rs.getMetaData().getColumnCount();
Object val;
while (rs.next()) {
for (int i = 1; i < columnCount; i++) {
//System.out.println(i);
val = rs.getObject(i);
if (val != null)
sb.append(val.toString() + "\n");
} catch (SQLException e) {
e.printStackTrace();
} catch (NamingException e) {
e.printStackTrace();
} finally {
try {
if (rs != null)
rs.close();
if (pstmt != null)
pstmt.close();
if (con != null)
con.close();
} catch (Exception e) {
e.printStackTrace();
String str = sb.toString();
int len = str.length();
//System.out.println("LENGTH >>>>"+len);
return str;
public static void main(String[] arg) {
Date date = new Date();
System.out.println(date.toGMTString());
getData gd = new getData();
System.out.println(date.toGMTString());
//System.out.println(gd.getIndexData("ACB"));
* WebClient:
package hnx;
import java.util.Date;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPBodyElement;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.Dispatch;
import javax.xml.ws.Service;
import javax.xml.ws.WebServiceException;
import javax.xml.ws.soap.SOAPBinding;
public class wsClient {
public wsClient() {
super();
public String procWeb() {
String strmsg = null;
try {
QName serviceName = new QName("http://192.168.60.18:7001/","getDataService");
// QName for Port As defined in wsdl.
QName portName = new QName("http://192.168.60.18:7001/","getDataPort");
// //Endpoint Address
String endpointAddress = "http://192.168.60.18:7001/WsIndex/getDataPort?wsdl";
// Create a dynamic Service instance
Service service = Service.create(serviceName);
service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING,
endpointAddress);
// Create a dispatch instance
Dispatch<SOAPMessage> dispatch = service.createDispatch(portName,
SOAPMessage.class, Service.Mode.MESSAGE);
// Use Dispatch as BindingProvider
BindingProvider bp = (BindingProvider) dispatch;
// Optionally Configure RequestContext to send SOAPAction HTTP Header
Map<String, Object> rc = bp.getRequestContext();
rc.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
rc.put(BindingProvider.SOAPACTION_URI_PROPERTY, "http://ws/");
// Obtain a preconfigured SAAJ MessageFactory
MessageFactory factory = ((SOAPBinding) bp.getBinding())
.getMessageFactory();
// Create SOAPMessage Request
SOAPMessage request = factory.createMessage();
// Request Body
SOAPBody body = request.getSOAPBody();
// Compose the soap:Body payload
QName payloadName = new QName("http://ws/", "getIndexData","ns1");
SOAPBodyElement payload = body.addBodyElement(payloadName);
SOAPElement message = payload.addChildElement( "param");
message.addTextNode("HNX302");
request.saveChanges();
// Invoke the endpoint synchronously
System.out.println(message);
SOAPMessage reply = null;
try { // Invoke Endpoint Operation and read response
reply = dispatch.invoke(request);
} catch (WebServiceException wse) {
wse.printStackTrace();
// process the reply
SOAPBody bodyRes = reply.getSOAPBody();
SOAPBodyElement nextSoapBodyElement = (SOAPBodyElement) bodyRes
.getChildElements().next();
SOAPElement soapElement = (SOAPElement) nextSoapBodyElement
.getChildElements().next();
strmsg = soapElement.getValue();
System.out.println("AAA >>"+strmsg);
} catch (Exception wse) {
wse.printStackTrace();
return strmsg;
public static void main(String[] arg) {
wsClient ws = new wsClient();
Date date = new Date();
System.out.println(date.toGMTString());
System.out.println(ws.procWeb());
System.out.println(date.toGMTString());
* Servlet:
package hnx;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.*;
import javax.servlet.http.*;
import ws.GetData;
import ws.GetDataPortClient;
import ws.GetDataService;
public class getIndex extends HttpServlet {
private static final String CONTENT_TYPE = "text/html; charset=UTF-8";
public void init(ServletConfig config) throws ServletException {
super.init(config);
public void doPost(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
doGet(request, response);
public void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
response.reset();
response.flushBuffer();
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
// GetDataService service = new GetDataService();
// GetData getData = service.getGetDataPort();
// String str = getData.getIndexData("HNX302");
// int length = str.length();
// response.setContentLength(length);
wsClient ws = new wsClient();
String str = ws.procWeb();
try {
out.println(str);
} catch (Exception e) {
e.printStackTrace();
out.close();
ERROR: >>>>>[Another instance of the application is running on the server. JDeveloper redeploy the application.]
[Application SClient stopped but not undeployed from Server Instance IntegratedWebLogicServer]
[Running application SClient on Server Instance IntegratedWebLogicServer...]
[03:41:48 PM] ---- Deployment started. ----
[03:41:48 PM] Target platform is (Weblogic 10.3).
[03:41:48 PM] Retrieving existing application information
[03:41:48 PM] Running dependency analysis...
[03:41:48 PM] Deploying 2 profiles...
[03:41:48 PM] Wrote Web Application Module to C:\Users\W7\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs\SClient\sgetDataWebApp.war
[03:41:48 PM] Wrote Enterprise Application Module to C:\Users\W7\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs\SClient
[03:41:49 PM] Redeploying Application...
[03:41:49 PM] Application Redeployed Successfully.
[03:41:49 PM] The following URL context root(s) were defined and can be used as a starting point to test your application:
[03:41:49 PM] http://192.168.9.100:7101/SClient
[03:41:49 PM] Elapsed time for deployment: 1 second
[03:41:49 PM] ---- Deployment finished. ----
Run startup time: 1380 ms.
[Application SClient deployed to Server Instance IntegratedWebLogicServer]
Target URL -- http://127.0.0.1:7101/SClient/getindex
[param: null]
javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
     at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:117)
     at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
     at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:165)
     at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:101)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
     at com.sun.xml.ws.client.Stub.process(Stub.java:248)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:189)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:215)
     at hnx.wsClient.procWeb(wsClient.java:75)
     at hnx.getIndex.doGet(getIndex.java:40)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
     at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1687)
     at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
     at com.sun.xml.ws.message.saaj.SAAJMessage.writeTo(SAAJMessage.java:396)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:114)
     ... 29 more
Caused by: java.net.ProtocolException: Exceeding stated content length of 228
     at weblogic.net.http.ContentLengthOutputStream.write(ContentLengthOutputStream.java:39)
     at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:96)
     at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
     at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
     at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1685)
     ... 32 more
java.lang.NullPointerException
     at hnx.wsClient.procWeb(wsClient.java:82)
     at hnx.getIndex.doGet(getIndex.java:40)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone help?
Thanks in advance.
LTThoi

I'm no webservices/servlet expert , but can you check the obvious out here -
javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
at ......
at hnx.wsClient.procWeb(wsClient.java:75)+ // check if you are passign something thats more than 228 chars
at hnx.getIndex.doGet(getIndex.java:40)

Error BT616 when calling function module SXPG_COMMAND_EXECUTE in background

Hi All,
We use function module SXPG_COMMAND_EXECUTE with a custom command we defined in SM69 to move files in unix (mv command).
The function module call has worked fine for almost a year and recently we have been seeing an error (BT616) in our job lob (SM37) when the program is run in background. We have not been able to reproduce the error in foreground mode and it seems to be occuring only periodically in the background. (The appropriate SAP authorization objects where assigned to the batch job ID and the steps on the batch job.) We are in the process of setting up the trace flag and performing analysis on the trace log via ST11 to help identify the issue.
After perform analysis on SXPG_COMMAND_EXECUTE, the error is occurring when calling function module SAPXPG_END_XPG for exception 2, system failure, yet function module SAPXPG_END_XPG does not exist. I assume this is a program at the operating system level and is just a signature of the parameters to be passed to the operating system program.
Below is part of the SAP function module SXPG_COMMAND_EXECUTE that is failing.
* Now we have to wait for the termination of the external
* command if the caller wants us to.
    IF TERMINATIONWAIT = 'X'.
      CALL FUNCTION 'SAPXPG_END_XPG'
        DESTINATION DESTINATION
        IMPORTING   EXITSTAT = STATUS
                    EXITCODE = EXITCODE
        TABLES      LOG      = LOG
        EXCEPTIONS COMMUNICATION_FAILURE = 1 MESSAGE MSG
                    SYSTEM_FAILURE        = 2 MESSAGE MSG.
I performed a where used on function module SXPG_COMMAND_EXECUTE, and most of SAP programs call the function module with the parameter TERMINATIONWAIT = 'X', so I assume we should pass X as well.
Any ideas on what could be causing this issue?
Mike Vondran

I also remember I have this kind of issue, as I have some UNIX script at OS( UNIX) level . The problem was with the ID , as it dont have proper authorization at OS level ( UNIX ) . Please check this ID authorization. This could be the one of reasons if youre sure from SAP standpoint.
Hope thisll give you some guide line..
Thanks
Bye

Error '9' when calling service 'SO_OBJECT_SEND'

We are implementing travel module. The scenario is when the employee raises a travel request, after approving the mail should be sent back to the employee. This feature is provided by the standard.
However in the SEND_MAIL step the WORKFLOW Container variable 'Employee.Trip.User.Id' is not set owing to which the mail step gives out error.
Can anyone please guide us on the probable cause of the error ?? Where does the object TRIP gets the value 'TRIP.USER.ID' ??
Is it any setting issue ??
Please guide..

Hi
Run report HRALXSYNC and you will solve this.
We have faced this issue many times and the solution we have applied is
1. This issue occurs on a step that is dialog where some agent needs to either approver or reject.
2. You should check the rule (Agent determination rule in that step).
Run that rule with the workflow data (use scenario with which you are getting error).
Run the rule individually and check if you are getting right result.
this error most of the time id due to the fact that the rule is not be able to determine next processor of the workitem.
Error 9 when calling service SO_OBJECT_SEND SWF_RUN535
to assure you can hardcode the user for test in the rule and run the workflow as that is the most effective analysis that will help you determine the cause.
I have never seen this error on a background step unless there is a mail step involved.
You need to run the report HRALXSYNC to synchronize HR objects which will surely solve this issue.
regards
barin

Can we call a analysis view from a Dashboard

Hi,
Is it possible to call an Analysis View(ex Table, pivot view etc) from a dashboard. I am trying to call Summary and Detail View of an Analysis in a dashboard, when I click on Summary, Summary view should be called and when I click on Detail, Detail view should be called. Can anyone let me know, if this is possible.
I am using 11g.
Thanks for any help.

Hi,
It's possible only. just add analysis view in the dashboard end then call it where ever u want.
Thanks
Deva

Runtime error OBJECTS_OBJREF_NOT_ASSIGNED when calling any standard GRC API's

Hello colleagues,
I always get the runtime error OBJECTS_OBJREF_NOT_ASSIGNED when calling any standard GRC API's
For instance, lets take Function Modules:
I tried almost any of them but in particular:
GRPC_API_CONTROL_QUERY Load the list of controls
GRPC_API_ISSUE_QUERY Retrieve issues of the case
GRPC_API_ORGUNIT_QUERY Load list of Organizations
GRPC_API_RMPLAN_QUERY Retrieve remediation plans of case
GRPC_API_RISK_CONTROLS Retrieve the controls of the risk
and etc.
All of them return the runtime error OBJECTS_OBJREF_NOT_ASSIGNED, however I've provided Object ID's in the right format,
The same is for corresponding classes,
Does anyone have such problem before?
Appreciate your responses,
Thank you,
Best Regards,
Anton

Hi Anton,
We need to pass value for I_SESSION_ID. Because, when i execute FM: GRPC_API_RMPLAN_QUERY by giving correct I_OBJECT_ID as shown below, i'm also getting the same error.
On executing..
Getting following dump.
And attached is the dump analysis .
Thanks
KH

ABAP process hangs when calling a jCO Server J2EE-available RFC

Hi there
Here's the scenario:
We have deployed a jCO server under the SAP WAS. This jCO server implements two functions. They are both called from ABAP process through RFC. We are using the same RFC destination for both
First function is defined with import/export parameters and the second one only operates with a TABLE parameter.
Incidentally, these functions are captured by the jCO server, which calls an IBM MQ server
First function works fine. Second function hangs and there is not even a timeout so the ABAP process (run on foreground) can stay forever.
The interesting part is that the same application works really fine when called from a Tomcat using a standalon instance of the jCO.
Additional info:
We have noticed that some time after the second function gets called, there are five dumps on the system (the same amount of servers we make available). These are CALL_FUNCTION_SIGNON_REJECTED.
The fun part of the dumps is that the user making the RFC call is a different user that the one we use for the jCO connection, and the client number is '000', instead of the '728' we are using for the connection. Somehow they seem related but we do not know how yet:
Short text
    You are not authorized to logon to the target system (error code 1).
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    RFC (Remote Function Call) sent with invalid
    user ID "%_LOG01% " or client 000.
    User "ARINSO " under client 001 from system "SMD " has tried to carry out an
     RFC
    call under the user ID "%_LOG01% " and client 000 (Note: For releases < 4.0,
     the
     information on caller and caller system do not exist.).
Call Program........."SAPLSMSY_ACTUALIZE_DATA"
Function Module..... "SCSM_SYSTEM_LIST"
Call Destination.... "SM_ET7CLNT000_READ"
Source Server....... "sapwasmd_SMD_10"
Source IP Address... "172.17.82.80"
Termination occurred in the ABAP program "SAPMSSY1" - in
     "REMOTE_FUNCTION_CALL".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 67
    of the (Include) program "SAPMSSY1".
Any tip or suggestion on where to look at is more than welcome
Thanks in advance,
Miguel

And this is the content of the defaultTrace.0.trc log from the WAS
1.#005056AB04C500440000000200002B0000046B495CA1AF67#1243862737727#com.sap.caf.um.relgrou
ps.imp.principals.RelGroupFactory##com.sap.caf.um.relgroups.imp.principals.RelGroupFactor
y.RelGroupFactory()#######SAPEngine_System_Thread[impl:5]_13##0#0#Info#1#/System/Server#P
lain###sap.com caf/um/relgroups/imp MAIN_NW701P03_C 2846629#
#1.#005056AB04C500240000000100002B0000046B495CCDAAFB#1243862740608#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksCount>: com.sap.engine.library.monitor.
mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/Kerne
l/System Threads Pool/WaitingTasksCount' (MANAGERS.SThreadPool.WaitingInRequestQueueCount
, max. 40 characters)#
#1.#005056AB04C500240000000200002B0000046B495CCDB4CC#1243862740612#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/System Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.library.
monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for nod
e'/Kernel/System Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.SThreadPool.Waiting4Fr
eeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500240000000300002B0000046B495CCDCDA1#1243862740618#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksCount>: com.sap.engine.library.mon
itor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group for node'/
Kernel/Application Threads Pool/WaitingTasksCount' (MANAGERS.AThreadPool.WaitingInRequest
QueueCount, max. 40 characters)#
#1.#005056AB04C500240000000400002B0000046B495CCDD69B#1243862740620#com.sap.engine.library
.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace####n/a##b3
89a8004eaf11dec9b7005056ab04c5#SAPEngine_System_Thread[impl:5]_39##0#0#Error##Plain###Reg
isterNode</Kernel/Application Threads Pool/WaitingTasksQueueOverflow>: com.sap.engine.lib
rary.monitor.mapping.ccms.CcmsConnectorException: 2100850: Invalid configuration group fo
r node'/Kernel/Application Threads Pool/WaitingTasksQueueOverflow' (MANAGERS.AThreadPool.
Waiting4FreeReqQueueSlotCount, max. 40 characters)#
#1.#005056AB04C500600000001600002B0000046B4960688301#1243862801089#com.sap.slm.exec.messa
ge.SLMApplication#sap.com/tcslmslmapp#com.sap.slm.exec.message.SLMApplication#Guest#0##
n/a##c59827604eaf11de9fb3005056ab04c5#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##
Java###null##
#1.#005056AB04C500730000000000002B0000046B4CF0593ABD#1243878100908#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain###com.sap.mw.jco.JCO$AbapException: (126) 1: Array index out of rang
e: 48#
#1.#005056AB04C500730000000100002B0000046B4CF0594028#1243878100909#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.efh.jco.valtran.sap.ValtranRequestHandler.serverExceptionO
ccurred(ValtranRequestHandler.java:164)#
#1.#005056AB04C500730000000200002B0000046B4CF059406B#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO.fireServerExceptionOccurred(JCO.java:880)#
#1.#005056AB04C500730000000300002B0000046B4CF05940A3#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.listen(JCO.java:8187)#
#1.#005056AB04C500730000000400002B0000046B4CF05940DB#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.work(JCO.java:8303)#
#1.#005056AB04C500730000000500002B0000046B4CF0594111#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.loop(JCO.java:8250)#
#1.#005056AB04C500730000000600002B0000046B4CF0594143#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at com.sap.mw.jco.JCO$Server.run(JCO.java:8166)#
#1.#005056AB04C500730000000700002B0000046B4CF05941F0#1243878100910#System.err#arinso.com/
valtran_validator#System.err#Guest#0##ET7#MIGUELGU                        #4A240FF606CD5E
5AE10000000A38418C#Thread[JCO.ServerThread-11,5,SAPEngine_Application_Thread[impl:3]_Grou
p]##0#0#Error##Plain### at java.lang.Thread.run(Thread.java:770)#

Error when calling BAPI_MATERIAL_SAVEDATA

Hi all,
I'm calling BAPI_MATERIAL_SAVEDATA through a RFC. I use SAP PI to call a function module and the function module calls the BAPI like this:
call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        headdata             = ls_headdata
        clientdata           = ls_clientdata
        clientdatax          = ls_clientdatax
        plantdata            = ls_plantdata
        plantdatax           = ls_plantdatax
        salesdata            = ls_salesdata
        salesdatax           = ls_salesdatax
        warehousenumberdata = ls_warehousenumberdata
        warehousenumberdatax = ls_warehousenumberdatax
      tables
        materialdescription = lt_materialdescription
        unitsofmeasure       = lt_unitsofmeasure
        unitsofmeasurex      = lt_unitsofmeasurex
        internationalartnos = lt_internationalartnos
        taxclassifications   = lt_taxclassifications
        returnmessages       = lt_return2.
The BAPI stops processing on the line:
UPDATE MARU FROM TABLE MARU_UPD
in function MARA_ARRAY_UPDATE.
I receive the following error message in PI Communication Channel Monitoring:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZSD_PEPE_CAT_INBOUND in remote system (RfcClient[CC_PepeSAPSDIn]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Data type MARU was found in a newer version than required.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZSD_PEPE_CAT_INBOUND in remote system (RfcClient[CC_PepeSAPSDIn]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Data type MARU was found in a newer version than required.
ST22 tells me this:
Runtime Error          TYPELOAD_NEW_VERSION
       Occurred on     11.03.2009 at   13:08:11
Data type "MARU" was found in a newer version than required.
What happened?
Runtime error
The current ABAP program, "SAPLMG21", had to be terminated because one of the
statements could not be executed at runtime.
Information on where terminated
The termination occurred in the ABAP program "SAPLMG21" in "MARA_ARRAY_UPDATE".
The main program was "SAPMSSY1 ".
The termination occurred in line 44 of the source code of the (Include)
program "LMG21U02"
of the source code of program "LMG21U02" (when calling the editor 440).
Any idea what's wrong with the data type MARU?
Thanks in advance!!
Regards,
Ivo van Ee

Just found out that a colleague added some append fields to the mara structure. This seems to be the cause of the problem. We still don't know how to solve the problem though....
MARA:
.APPEND     ZAMARA_HFL     STRU     0     0     Fashion additional article master data
ZZCOLOR     ZCOLOR     CHAR     3     0     Color code
ZZCOLOR_DESCR     ZCOLOR_DESCR     CHAR     20     0     Color code description
ZZFIT     ZFIT     CHAR     3     0     Fit code
ZZFIT_DESCR     ZFIT_DESCR     CHAR     20     0     Fit code description
ZZSIZE_SCALE     ZSIZE_SCALE     CHAR     1     0     Size scale
ZZSIZE_DESCR     ZSIZE_DESCR     CHAR     20     0     Size description
ZZSIZE_POS     ZSIZE_POS     NUMC     2     0     Position of Size description in matrix
ZZANALYS04     ZANALYS04     CHAR     4     0     Analysis code 04
ZZANALYS04_DESCR     ZANALYS04_DESCR     CHAR     20     0     Analysis code 04 description
MARU:
ZZCOLOR     CHAR     3     Color code
ZZCOLOR_DESCR     CHAR     20     Color code description
ZZFIT     CHAR     3     Fit code
ZZFIT_DESCR     CHAR     20     Fit code description
ZZSIZE_SCALE     CHAR     1     Size scale
ZZSIZE_DESCR     CHAR     20     Size description
ZZSIZE_POS     NUMC     2     Position of Size description in matrix
ZZANALYS04     CHAR     4     Analysis code 04
ZZANALYS04_DESCR     CHAR     20     Analysis code 04 description

Problem with Workload analysis

Hi All,
we recently added one system to SMD. when I enter workload analysis in SMD for this system, I see the below two error.
1. 'Message A RSDODSO 162 cannot be processed in plugin mode HTTP'
2. Error when generating dataProvider
Please suggest where the problem persist.
Regards,
Deepak

Hello,
Please go to
http://server.company.domain:52000/webdynpro/dispatcher/sap.com/tcsmde2ewa/E2ewaConfig url and correct the BI url and port ?
Please, add also the BI port to your SAP router.
This should resolve your error.
Regards,
Paul

BRAIN 605 when calling Workload analysis in Solman 4.0 EHP1

Similar Messages

Maybe you are looking for