Skip to end of metadata
Go to start of metadata

Symptom
You cannot see any system data in the Monitoring UI or jump-in to E2E Trace is not available.

Background
Executions (Timestamp and steps below) are written with bold letters if system data or a trace is available. If the execution is triggered with a trace level > 0 the text is written in italic letters.
Currently there are 3 types of scripts where system data or traces can be collected/displayed:

1. HTTP Script for SAP J2EE based applications

System data/traces are only available if tracing has been enabled (Run Script with trace or Set temporary configuration). It is possible to configure so that HTTP log and DSR records are always written. See also Trace Enabling for EEM  

2. HTTP Script for ABAP based application

System data/statistical records are always available. Detail traces (SQL, ABAP Trace,..) are only available when tracing has been enabled.

3. SAPGUI Script

System data/statistical records are not for all steps available. Detail traces (SQL, ABAP Trace,..) are not possible at the moment.

Solution

When system data/traces are missing (see description above) you can check the following steps:

1 . The parameter "Expire in seconds" of temporary configuration should have a value higher than 60 seconds (default 1800)

2. Is the script assigned to a technical scenario? In setup step 3.3. check that a technical scenario is filled in for the script.

3. Is the extractor running?
Go to work center SAP Solution Manager Administration, in Infrastructure launch the Extractor Framework view. For each technical scenario there is an extractor EEM system data of TechScen .... See screen shot:

4. Check the log of the extractor.

If there is an error message like

Current SMD Upgrade status does not allow trace collection

the SMD Upgrader must be executed after applying an LM-Service patch.
This can be done in SOLMAN_SETUP -> Basic Configuration -> Step 2.4 (Solution Manager Internal Connectivity) -> Activity: Run Java Upgrader

If there is an error message like

Trace collection failed: 1/0 exceptions occurred during synchronous/asynchronous trace collection.

an error occurred during trace collection in Solution Manager J2EE and  you need to check the log viewer of the Solution Manager Java Stack.

- Start the NWA log viewer ( /NWA -> Monitoring -> Logs and Traces -> Show Default trace.

- open the filter and enter:  location   contains   com.sap.sup.admin.e2e.trace and click on 'Apply filter '

From the screen shot above it is clear why the trace collection aborted (SMD Agent cannot be reached at this time) but in other cases when the BusinessTransaction*.xml could be retrieved it makes sense to start a single analysis just with one file that is uploaded in the E2E Trace application for the system. Proceed as follows:

Manual Trace Collection

- Get the BusinessTransaction.xml from robot (click the link if you want to analyze the BusinessTransaction.xml within the EEM Editor)

  • Select the interesting execution in the EEM Monitoring UI
  • Right-click with mouse and select "Copy Transaction ID to clipboard":

- Open the E2E Trace application from the RootCause Analysis work center for the Technical System(s)/Scenario you want to collect the trace and paste this id there:

- Trigger the server-side trace collection and check the progress and in parallel the default.trc as mentioned above.


 
Known Problems
1. HTTP Script for SAP J2EE based applications
-HTTP log or DSR records could not be found.

2. HTTP Script for ABAP based application
-ICM HTTP log does not have the correct format.

3. SAPGUI Script
-ABAP Statistic records could not be found because the time difference of Robot and called system is too high.

4. In SAP Solution Manager 7.1 SP03 and SP04
- No system data can be found if the Technical Scenario name has been created including lower case characters. Because of a data element change it is possible to create Technical Scenarios with lower case but internally another data element was used which translates them to upper case. The problem is solved with SP05. As a workaround in SP03 and SP04 you need to create the Technical Scenario name only in upper case.

5. In SAP Solution Manager 7.1 SP03 and SP04
- System data of SAPGUI scripts are not displayed in monitoring UI because trace collector aborted during trace collection. In default trace of J2EE engine you can find the exception:
ABAP SysLog collection was aborted: For input string: ".
This problem is solved with LMSERVICE patch 2 for SP03 or LMSERVICE patch 1 for SP04.

6. In SAP Solution Manager 7.1 SP05
The user SM_EXTERN_WS does not have the authorization to collect automatically traces and system data. Upload the role SAP_SM_EXTERN_WS attached to note 1703150 in PFCG, go to SOLMAN_SETUP 'System Preparation' step 1 and update authorization of user SM_EXTERN_WS.

7. Extractor fails with exception Overflow when converting from "  "
There might also a dump CX_SY_CONVERSION_OVERFLOW created for program CL_E2E_TA=====================CP.

The reason is a bug in statistic recrods in managed system leading to extremly high numbers which is solved with note 2071875 (Incorrect Average RFC Interface Time ("CPIC/RFC")).

Apply in the managed system the Kernel patch mentioned in note 2071875.

 

 

  • No labels