Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Troubleshooting Guide for End-User Experience Monitoring

*in SAP Solution Manager 7.1 and 7.2

----

Content

Design Time

Symptom
*Post parameters of a http message are duplicate.

Reason
The client plugin (EEM recorder) has a defect.

Solution
Manually eliminate the duplication as long as no official fix is available.
Example:

Recorded parameter
cmd=get_esidcmd=get_esid
Corrected parameter
cmd=get_esid


New imported SAPGUI script fails in EEM Editor during replay

Symtom
You imported a SAPGUI recording into EEM Editor and provided correct logon credentials. A script execution in EEM Editor fails and you get error messages like: "The control could not be found by id. (SAP Frontend Server ):619: wnd1/usr/ctxt2.text"

Reason
There might be several reasons for this behaviour and a step by step analysis is required.

Procedure

  1. Re-record the script in SAPGUI and ensure that you do not use value history function of SAPGUI to provide values to textfields even if they are provided. Type it character by character again.
  2. Stop the recorder and try to execute the created VBS file directly in the SAPGUI.
    1. If the VBS file shows a execptional behavior by showing control errors the issue is related to your SApGUI installation not to EEMon
    2. In this case provide the version/buildnumber of your SAPGUI to support together with the recorded file.
    3. In most cases a different version of SAPGUI solves the issue.
  3. If the script was executed succesfully in SAPGUI alone but fails after import to EEM Editor please check the User credentials again.
  4. Execute the script step by step to identify the EEM message which causes the issue by adressing an unknown UI element.
  5. Execute the script again till the point where the script would during next action. Use the mouse to click on the UI element which should be adressed during a correct execution. The red square helps you to navigate in the UI components. For example
  6. Proceed with script execution to exit the script. The selection of the correct UI elemet with the mouse has created an availability check for this element. We do not need this check but it shows the component ID of the important UI element that is not pressed or activated during the exeptional scipt runs.
  7. Compare the component ID from check with the component ID mentioned in the next message. In some cases the IDs differ. Try to execute the script with a corrected component ID in the message.
  8. Run the script again with hardcopy and component trace options:
    1. Go to script configuration, SAPGUI settings.
    2. Activate "hardcopy" and "Component Trace" and hit "Apply".
    3. Perform another replay of the script. During the replay the editor now captures screenshots for every message and in addition a dump of the UI element hierarchy.
    4. You can review this by clicking at single messages in the replay result.
  9. If it is still not working prepare a WTS connection to the recording PC to an account where the SAP support can use the EEM Editor and execute and analyse the script in detail.
Unable to render {include} The included page could not be found.

Symptom:

Editor finished execution half way of a replay without any error infomation. Go to workspace\.metadata\.log,
there is some OOM identified.

Solution:

Open EemEditor.ini file and add the following parameters to increase the Java heap size: -XX:MaxPermSize=64m, -Xmx128m



Symptom
You are recording SAPGUI Script under usage of a F4 help dialog and action dumps with
"Runtime error MESSAGE_TYPE_X has occurred occurs"

Solution

Open the SAPGUI menu HELP => SETTINGS => tab F4 Help

Set Display radio button to "Dialog(modal)"


Symptom
When executing an http script in EEM Editor some requests fail with error message
Variable inplaceEditForm:reference:c0-e6, inplaceEditForm_accordionMenu_expanded_state:reference:c0-e7 is not defined, e.g., because a preceding request did not deliver the expected result.
Reason
The string is a JSON object but handled as a variable. This might happen for example when creating a script for Successfactor.

Solution
Create a variable with exactly the same name and value.
Example:

Name
inplaceEditForm:reference:c0-e6, inplaceEditForm_accordionMenu_expanded_state:reference:c0-e7
Value
{inplaceEditForm:reference:c0-e6, inplaceEditForm_accordionMenu_expanded_state:reference:c0-e7}


 

 

EEM Editor Crash with Java 7

Symtom

The EEM Editor might crash with an EXCEPTION_ACCESS_VIOLATION when executing an RFC script.

Reason

The problem is located in the JCO native libraries.

Solution

Configure the EemEditor explicitly to launch with a specified 32bit JDK. For this purpose, add this parameter to EemEditor.ini:

-vm c:/full/path/to/javaw.exe

 

 

RFC ContentCheck in Export Parameters cantaining <item> elements*

Symtome
Your RFC content check fails even if you have correctly mapped the XML structure shown under tab Export Parameters in a Content Check path.

Export Parameters
<OUTPUT>
 <SCRIPTS>
    <item>
      <SCENARIO_ID>2</SCENARIO_ID>
    </item>
 </SCRIPTS>
</OUTPUT>

The current implementation of EEM is not operating on the displayed XML structure which is only dumped out for the end-user in the EEMEditor. During runtime it is operating on predefined classes for RFC handling with a different hierarchy:

Be Careful

Wrong path, but what you would expect from XML: EXPORT.OUTPUT.SCRIPTS.item.Scenario_ID

Correct Path

To get a correct path generally ignore OUTPUT and metatag item, which just represents an ABAP table unknown to java.:
Correct path: EXPORT.SCRIPTS.Scenario_ID

 ----

Configuration Time

Symptom
The SOLMAN_SETUP task 'Create Endpoints for communication' fails with message Error during End Point creation.
Reason
The configuration For service definition AI_EEM_LIST_ALL_SCENARIOS could not be generated. There was a problem in after import method when applying the SP.
Solution
Execute the report REPAIR_AFTER_IMPORT to solve the issue and execute the task again.


Symptom

Error Message after trying to deploy scripts to robots:

  • Resources cannot be uploaded: Script= ... SoapFaultCode 4: Deserialization fails: Nested Message: XML Deserialization Error. XML Parser has thrown exception while parsing input
  • Resources cannot be uploaded.;Script= ... SoapFaultCode:5 Reader is not positioned on start element.Probably incorrect usage of stream parsing methods.
  • ICF Error when receiving the response: HTTPIO_PLG_CANCELED

Resolution

This is a known bug in the http service of the SAP J2EE server. SAP Note 1638655 lists the patch levels for J2EE software components that fix the problem.

Work-around: Point the consumer proxy directly to the J2EE dispatcher instead of pointing to the ICM. Procedure:

  1. Start SOAMANAGER in SAPGUI via transaction /nSOAMANAGER
  2. Select Web Service Configuration
  3. Search by Consumer Proxy, search pattern *EemAdmin*. Select CO_EEM_EEM_ADMIN_VI_DOCUMENT and click Apply Selection.
  4. Select tab Configurations in the lower pane.
  5. Select the logical port SMD and click Edit.
  6. Select tab Transport Settings
  7. Update the field Port Number of Access URL to contain the J2EE dispatch port (e.g. 50000).
  8. Select tab Messaging
  9. for Message ID (Synchronous), select _Suppress ID Transfer
  10. Click Save

Symptom
When deploying or uploading a script that cannot be started on the robot because of missing properties or an error the deployment throws the exception
SOAP:1.001 CX_SY_CONVERSION_OVERFLOW:.An error occurred when deserializing in the simple transformation program /1SAI/....Overflow converting from <java timestamp>.
Reason
The long value of the java timestamp is mapped to an INT4 data element.
Solution
Check in transaction SRT_UTIL in the paylaod for the real error (e.g. property not found in SecureStore:...) correct it and deploy the script again. The mapping is corrected with 7.1 SP08.

Symptom

In the SOLMAN_SETUP step 'Configure EEM Robots' terminates with the error Operation "getMatchingAgentInfo{urn:EemAdminWsd/EemAdminVi/document}" not supported (interface: "CO_EEM_EEM_ADMIN_VI_DOCUMENT" ...} when clicking on button 'Check Agents'.

Reason 

The web service in Java has been enhanced to provide a filter option when searching for robot candidates. 

Solution

Execute in SOLMAN_SETUP the activity Create Logical Ports in step Configure Automatically:

 

 

----

Run Time

Known problems

Known problems in Solution Manager 7.1 SP03

  1. Each second http script execution fails with status 504 (server not responding).
    This problem is solved with LMSERVICE patch 2 for SP03
  2. 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.

Known problems in Solution Manager 7.1 SP04

  1. After upgrade to SP04 scripts are not executed anymore or are executed with wrong configuration (e.g. wrong schedule period)
    Check if correction note 1651279 has been applied and if SOLMAN_SETUP step 2.4(Configure Automatically) and activity 'Perform tasks after upgrade' has been executed.
  2. Each second http script execution fails with status 504 (server not responding).
    This problem is solved with LMSERVICE patch 1 for SP04
  3. Starting a script in the editor will fail if no Solution Manager connection is maintained. Error message: com.sap.smd.eem.executor.ExecutorException: Failed initiate executor
    ... Caused by: java.lang.NumberFormatException: For input string: ""
    Work-around: In the status bar (bottom right) click "Solution Manager Connection not Configured" and maintain the connection data. After this scripts can be executed.
  4. 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 1 for SP04. 

----

EEM Robot

 


Symptom:
EEM Robot does not show sapgui as supported protocol
Solution:
The EEM robot tries to access the SAPGUI scripting object as test whether SAPGUI scripts can be supported on the robot. Possible reasons for not supporting SAPGUI scripts:

  1. SAPGUI is not installed on the robot PC: SAPGUI for Windows must be installed
  2. The scripting functionality of sapgui is not installed. Open SAPlogon -> options -> Scripting. There must be a message like "Scripting is installed".
  3. EEM Robot fails to execute SAPGUI script due to missing privileges of MS Windows service-user "SAPService<DASID>".
    Add the "SAPService<DASID>" to group Administrators and restart the EEM Robot

Symptom
java.lang.RuntimeException: No implementation for SHA or MD5:
java.security.NoSuchProviderException: no such provider: IAIK
#at
com.sap.smd.eem.wsnotify.bulk.AI_EEM_BULK_NOTIFICATION_Stub

Solution

Follow the description to enable SSL for WSnotify.

Workaround

Revert to http.

Symptom
Sending a notification fails with the following error message:
com.sap.smd.eem.executor.wsnotify.WsNotifier - doNotification: notification call failed for URL http://../sap/bc/srt/scs/sap/ai_eem_bulk_notification?
EXCEPTION
javax.xml.rpc.soap.SOAPFaultException: Processing Error. More details in WS Error Log (transaction SRT_UTIL) by selection with UTC timestamp
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)

In SRT_UTIL you see this error message:
<EXCEPTION_INFO>
<TYPE>CX_INVALID_TRANSFORMATION</TYPE>
<ERROR_TEXT>The transformation /1BCDWB/WSSBED2302F1E3963004DA could not be executed</ERROR_TEXT>
<CX_SOAP_CORE>
<E_LOCATION>
<CLASS>CL_SXMLP_DATA_ST==============CP</CLASS>
<METHOD>CL_SXMLP_DATA_ST==============CM004</METHOD>
</E_LOCATION>
<E_TEXT>CX_INVALID_TRANSFORMATION:An exception with the type CX_INVALID_TRANSFORMATION occurred, but was neither handled locally, nor declared in a RAISING clause.The transformation /1BCDWB/WSS<...> could not be executed
</E_TEXT>

Background
It can happen that, e.g. after an upgrade, some transformations seem to have disappeared:
Meta data still exists (and the contents of the transformation can be displayed in Transaction STRANS) but the TRDIR entry is missing.

Solution
Apply note 1390832. The note contains report RS_RETRIEVE_XSLT which must be run afterwards in order to re-create some missing transformation programs.

 

Symptom

After upgrading to Solution Manager 7.20 sending a notification fails with the following error message:

[Thread[EEM WsNotifyQueue,5,main]] Error
com.sap.smd.eem.executor.wsnotify.WsNotifierST.doNotification notification call failed for URL https://<solman_host>:<port>/sap/bc/srt/scs/sap/ai_eem_bulk_notification_st?sap-client=XXX (user: SM_EXTERN_WS)

[EXCEPTION]

com.sun.xml.internal.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class com.sap.smd.eem.wsnotifyst.soapfunctions.mc_style.AiEemBulkNotificationSt is not found. Have you run APT to generate them?

 

Background

The JVM version of the SMD Agent might be too old.

Solution

Check the JVM version of the SMD Agents a version like  6.1.010 is too old. Apply a newer JVM version (e.g. 6.1.076 ) as described in note 1774669 (Diagnostics Agent - How To Switch or Update SAP JVM) or in the wiki page Diagnostics Agent Maintenance Procedures.

Symptom

After upgrading to Solution Manager 7.20 sending a notification fails with the following error message:

 

[Thread[EEM WsNotifyQueue,5,main]] Error      com.sap.smd.eem.executor.wsnotify.WsNotifierST.doNotification notification call failed for URL  https://<solman_host>:<port>/sap/bc/srt/scs/sap/ai_eem_bulk_notification_st?sap-client=XXX (user: SM_EXTERN_WS)

[EXCEPTION]

javax.xml.ws.soap.SOAPFaultException: Web service processing error; more details in the web service error log on provider side (UTC timestamp XXX; Transaction ID ...)

                at com.sun.xml.internal.ws.fault.SOAP12Fault.getProtocolException(SOAP12Fault.java:214)
                at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:117)
                at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
                at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
                at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
                at com.sun.proxy.$Proxy39.aiEemBulkNotificationSt(Unknown Source)

Or

javax.xml.ws.soap.SOAPFaultException: SRT: Serialization / Deserialization failed  
   at com.sun.xml.internal.ws.fault.SOAP12Fault.getProtocolException(SOAP12Fault.java:210) 
   at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:125)

Background

With older versions of the EEM Editor it was possible to create scripts with step names longer than 40 characters. In 7.20 the SOAP runtime throws an exception if the step name is too long.

In SRT_UTIL you can find an error like:

Data loss occurred when converting Step with a very long name 123456789012345678901234567890

Solution

Import the script in a new EEM Editor and reduce the length of the step names.

Executor

Symptom
SAPGUI script aborts at step 3 with exception The control could not be found by id
Background

The issue is caused by the configuration of the backend ABAP system in respect to multiple user logons. 

 

A SAPGUI script is recorded after the login procedure; the login procedure is not part of the recording.  To handle the logon the EEM Editor automatically adds the necessary steps. During the import it inserts 4 specific steps bevor the “main” the script logic.

From those 4 the steps 1 and 2 handle the regular login. The step 3 and 4 are conditional steps which are automatically inserted by the EEM Editor to confirm the multi login pop-up. That is, to handle the situation, when an active user session already exists and the backend system prompts the user on which actions he wants to take: “terminate the current logon”, “terminate other logons” or  the “continue with this logon, without ending any other logon”. The steps 3 and 4 will attempt to select the “continue with this logon” checkbox in the corresponding pop-up window and press the “login”. 

 

However, in some systems multiple login is not allowed (setting profile parameter login/disable_multi_gui_login). In this case the step 3 will always fail. It will try to find that “continue with this logon” checkbox which simple won’t be presented in the backend system. If the system does not allow multiple logons this pop-up has only two checkboxes, and the login will not succeed. All further steps of the script will probably fail either. The error message “FAILED: control could not be found by id” means that the particular “third” checkbox could not be found.

 

The issue may not occur in the EEM editor and the SAPGUI script work fine. The situation is typically different in the Solution Manager system, if multiple robots are login on the ABAP system with the same user credentials and if by chance two robots/executions happen to run in parallel or shortly one after another.

 

Solution
To get the script running successfully you have the following options:

  1. Configure different users per robot. Use for each script execution another user. This can be reached by setting the properties sapgui.user and sapgui.password in scope  script_on_robot (different for each script instance on the robots).
  2. Change the type of the user to SERVICE. This will prevent the pop-up for this user and as the advantage that the password will not expire.
  3. Allow multiple logons with same user in the backend systems. Add the user to the profile parameter login/multi_login_users
  4. Avoid parallel executions of the script. Synchronize executions in a way that a robot always logs out before another one tries a logon. See also Script Synchronization and Serialization

 

SAPGUI script fails on robots

Symtom You created a SAPGUI script which is running sorrectly in the editor and uploaded it to an EEM Robot where it fails. There might be different kind of errors like:

- RESULT_FAILED Message ... Current window id is wnd[0] while expected window id is wnd[1], please check for popups  

Reason SAPGUI scripts are executed in background on the robot with operating user SAPSERVICE<SID> which cannot interact with desktop. There might be several reasons for an error and a step by step analysis is required.

Procedure

You can change temporally the seetings of the service to interact with desktop. Every SAPGUI script execution is then visible when you logon to the robot with the SAPService user.

  1. Start services.exe
  2. Select the service e.g SAPDAA_96 and open the properties.
  3. Open tab 'Log On' and select 'Local System Account' and 'Allow service to interact with desktop' as shown on the screen shot below:
  4. Wait until the script will be executed and display the result.

After the analysis you should change the setting back to its original value. 



Symptome:
When executing a https script you get the exception"java.lang.NoClassDefFoundError: javax/crypto/SunJCE_b"

Background:
Jce-policy file is not extracted to the lib\security folder of the SAP JVM during the installation of agent 7.11 (SAP Note 1234387), which makes the https doesn't work for EEM.

Solution:

  • Download the JCE jurisdiction policy files as described in SAP Note 1240081.
  • Unzip it and copy the two JAR files, local_policy.jar and US_export_policy.jar, in the following folder:
    /usr/sap/<DASID>/SYS/exe/jvm/<PLATFORM>/sapjvm_<xxx>/sapjvm_5/jre/lib/security
  • On Unix platform do not forget to set the owner of the files to the Diagnostics Agent user (<dasid>adm:sapsys) and to set the permissions mode to 777.
  • Restart the agent.
  • Goto the folder \usr\sap\<AGENT_SID>\<AGENT_INSTANCE>\exe\sapjvm\jre\lib\security and check if the local_policy.jar and US_export_policy.jar exist. If not, please also copy the local_policy.jar and US_export_policy.jar to this folder.

Symptom
You are running a script which aborts with "java.net.ConnectException: Connection timed out: connect"

Solution

Check if a proxy is required to reach the url.
Set the properties http.proxy.host and http.proxy.port to the corresponding values and set http.proxy.enable to true.

Depending of the called system it might be required to set properties in different scopes:

  • If the called system and therefore the script always require these proxy properties you need to set them in the editor in the script properties (in the scope of the Script):
  • If the location/robot always require a proxy to reach called system(s) you need to set these proxy settings in SOLMAN_SETUP in the scope of the Robot:
  • If the called system requires requires these proxy settings only from some locations you need to set them in SOLMAN_SETUP in the scope of the Script on Robot:

 

 

 


Symptom
You are running a https script which aborts with "javax.net.ssl.SSLException: java.lang.UnsupportedOperationException"

Solution

Check if the script has a valid truststore or if the password for the global password is set.
When the password for the global truststore is not set you can add in eem_admin for the scope global the property
global.trustore.password and set it to eemstore.

 

Symptome:

When executing a script the following exception is thrown:

EXCEPTION
com.sap.smd.eem.executor.MessageException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target[
LinkedList0:
Issuer: CN=Company CA 5, OU=Trust Center Company, O=Company Services GmbH, C=DE
Subject: CN=selfservice-test.portal.Company.de, C=DE, ST=NRW, L=Anywhere, Company GmbH
SerialNum: 8166
Expires: Thu Nov 25 08:25:04 CET 2010
....
Index: 1

LinkedList1:
Issuer: C=BE, O=GlobalSign nv-sa, OU=RootSign Partners CA, CN=GlobalSign RootSign Partners CA
Subject: CN=CompanyCA 5, OU=Trust Center Company, O=Company Services GmbH, C=DE
SerialNum: 40000000001094550f4da
Expires: Thu Feb 07 12:00:00 CET 2013
...
Exception: null
Index: 2

LinkedList2:
Issuer: CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject: C=BE, O=GlobalSign nv-sa, OU=RootSign Partners CA, CN=GlobalSign RootSign Partners CA

Solution:

At least one of the bold written certificates above must be entered to the truststore (either global trustore or script specific truststore).

Please check 'How to Import HTTP Trust Certificate'  to import the certificate.

How to identify which truststores are used and what is contained?
To get information which certificates are already part of which truststores you have to increase tht log level of SMDAgentApplication.log of an SMD Agent to Debug and then stop and start the script. This is an extract of the output:
Info com.sap.smd.eem.executor.http.CertificateContext - loadKeyStore: Return the cached key store for file <Agent_path>\exe\sapjvm_5\jre\lib\security/cacerts
Debug com.sap.smd.eem.executor.http.CertificateContext - dumpKeys: TrustedCertificateEntry Subject:CN=VeriSign Class 1 Public Primary Certification Authority ...
Debug com.sap.smd.eem.executor.http.CertificateContext - dumpKeys: TrustedCertificateEntry Subject:CN=Entrust.net...
Info com.sap.smd.eem.executor.http.CertificateContext - loadKeyStore: Return the cached key store for file <Agent_path>\SMDAgent\applications.config\com.sap.smd.agent.application.eem\scripts/<Script_Name>/trustStore.jks

Debug com.sap.smd.eem.executor.http.CertificateContext - dumpKeys: TrustedCertificateEntry Subject:CN=portal-qas.company.de,C=DE,ST=...
Info com.sap.smd.eem.executor.http.CertificateContext - loadKeyStore: Return the cached key store for file <Agent_path>\SMDAgent\applications.config\com.sap.smd.agent.application.eem/trustStore.jks
Debug com.sap.smd.eem.executor.http.CertificateContext - dumpKeys: TrustedCertificateEntry Subject:CN=portal-qas.company.de,C=DE,ST=...

Symptom:

Http script runs in error (Editor or Robot) because of an ssl handshake failure

Message in the Editor:
SSL handshake failed, probably due to timeout, please restart the script: Received fatal alert: handshake_failure

In the Log you will see:
handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

Solution:

The SSL handshake failure is typically caused because client side (EEM) and web server could not agree on a common https protocol (e.g. SSL3, TLSV1, TLSV1.1, TLSV1.2) or on a cipher suite. There are multiple possible reasons for this:

There was some kind of timeout

Just try again ... 

The Java VM running the EEM script (in the editor / on the robot) misses the "unlimited strength jurisdiction policy" files.

Please install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. Information on where to get these files can be found in SAP Note 1240081.

  1. JDK used by the Editor
  2. JDK used by the robots (Sample path: ...\usr\sap\<Agent-SID>\SMDA97\exe\sapjvm_6\jre\lib\security)

The Java VM running the EEM script does not support the SSL protocol implementation / cipher suite at all

Java 6 has only limited support for crypto algorithms, whereas Java 8 comes with a more complete choice. Example: Java 6 does not support TLSV1.1 or TLSV1.2, while Java 8 does. So if the web server requires to use TLSV1.2, the EEM script will fail to execute running on Java 6. Since January 2018 Diagnostics Agents connecting against SAP Solution Manager 7.2 are also supported on SAP JVM 8.1.

As a cross check try if it makes a difference to run the EEM editor with Java 8. See Configure the Java VM for the Editor.

You can also activate a detailed SSL trace by setting the Java VM parameter -Djavax.net.debug=all (in EemEditor.ini). Output will be sent to the console. To make the console visible run the editor with java.exe (instead of the default javaw.exe). See again Configure the Java VM for the Editor.

For Diagnostics Agent communication issues having to do with TLS V1.2 please see the SAP Note 2463712.




 

Monitoring UI:


There might be several reasons why the monitoring UI does not start.

You get error messages like 'Cannot retrieve language bundle' or 'Cannot retrieve severtiy rules'.

  • Endpoints were not generated succesfully
    The endpoinpts the monitoring UI is calling are created in SOLMAN_SETUP for EEM in step 2.4 (Configure Automatically)

When the WSDL has ben loaded succesfully but further WS calls are failing like in the screen shot then the following points could be the reason:

  1. Missing authoriation.
    The user does not have the correct role and authorization for this WS is missing. To verify this an authorization trace for the user in ST01 can be recorded when calling the monitoring UI.
  2. Wrong WS configuration
    During SOLMAN_SETUP you explicitly allow in
    -> System Preparation -> Step 5.2 Web Service infrastructure Configuration
    which authentication types all web services can use:
    - Basic Authentication
    - X.509 Certificate Authentication
    - Ticket Authentication
    If you don't allow for example Ticket Authentication it is not possible to logon first via SAPGUI to SAP Solution Manager and start from there in the workcenter the EEM Monitoring UI. The following screen shot shows the required settings when all authentication types should be used:

     

Symptom
The Monitoring UI does not display any script executions. You just see the deployed scripts with grey icons and status 509 or 109.
Solution
The system does not get any notifications from the robots. There could be several reasons:

  1. The user for sending the notifications is locked
    The user for sending the notifications is stored on each robot. If the password is changed in user master record (SU01) and not in the setup application the robots use still the old password. But even if the password is changed in the the setup application it might happen that there is a small overlap when robots still using the old password until they receive the new password. The user can be unlocked in SU01. The name of the user is specified with parameter wsnotify.user .
  2. Accepting notifications is disabled
    For 7.1 in the setup application (SOLMAN_SETUP) and for 7.01 in eem_admin accepting notifications can be disabled globally.
  3. Robots are not available
    If robots are not reachable they are usually displayed at disconnected and they cannot send any notification.
  4. URL for sending the notification has been changed or is not correct
    The URL (including protocol, host and port) has been changed or is not correct. This might happen if the URL is using a host name and port for the message server that is not reachable from the robot location. The URL can be adapted by adjusting the parameter wsnotify.url .
  5. Notification is using https but iaik files are not installed. In SMDAgentApplication.log you can find this exception
    java.lang.Exception: Could not create https handler:java.lang.ClassNotFoundException iaik.protocol.https.Handler
    See also http://wiki.sdn.sap.com/wiki/display/EEM/SSL+For+Wsnotify
  6. After upgrading to Solution Manager 7.20 some robots cannot send notifications.
    See also AiEemBulkNotificationSt is not found

In general you should check the SMDAgentApplication.log of the robot if there is an error when sending the notification.

 

  

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.

 

 


The context menu in the monitoring UI can contain the following entries:

  • Go to E2E Trace Analysis
    This entry is only selectable if system data or traces have been collected and if user has the authority to jump to the E2E Trace.
  • View Collector Log
    This entry provides a jump-in to ABAP application log (SLG1) to display the result of the extractor collecting the system data or traces of the script executions. This entry is only selectable if the system data is not available.
  • Copy TransactionID to Clipboard
    The entry is only selectable for a script execution (time stamp). It provides the possibility to collect the logs from the robot and analyze it it tne eem editor. See also
  •  Run Script with Trace
    This entry is only possible for a selected script and robot combination. It triggers immediately an additional execution with provided trace level.
  • Set Temporary Configuration
    The selected script on the selected robot is executed for the configured time frame with the specified trace level.
  • Filter to
    Opens a new tab with just the selected script.
  • Assign Steps Filter
    Opens configuration menu to assign a filter on step level.
  • Jump to Alert Inbox
    Provides jump in to Unified Alert Inbox.
  • Collect Trace
    Triggers a trace collection immediately for the selected script execution.

Alerting

Missing alerts in Alert Inbox
Even there are red executions in the monitoring UI there are no alerts in the Alert Inbox.
There might be several reasons for this behaviour.

  1. During configuration an error occured and the script is not known to Monitoring and Alerting Infrastructure (MAI).
    Check the status of the script in SOLMAN_SETUP step 5 on tab Scripts. If the Alerting Status icon is green the script is at least available in MAI directory

    The script can also be configured from here.
  2. The script or the steps of the scripts are not alerting relevant
    Check in SOLMAN_SETUP step 5 on tab Steps if the flags for the Script/steps are set.
  3. Workmode settings supress the triggering of alerts.

    Check in SOLMAN_SETUP step 2.7 if Monitoring is enabled for workmode type 'No workmode configured'. If this flag is not set the default behaviour for DPC/MAI is to supress alerting.
  4. During alerting configuration of a script an exception occured.
    Check the application log (SLG1) for error messages of object E2E_ALERTING.
  5. Alerts are not triggered for each 'red' execution.
    Check the event propagation rule (Bestcase, Worstcase) for this category (Performance,Availability). See also FAQ Alert Progagation for more explanations
    Check that the ACE job (SAP_ALERT_CALCULATION_ENGINE) is running regularly (usually every minute) without delay.

Known problems in MAI

Known problems in Solution Manager 7.1 SP03

  1. No alerts are available in Alert Inbox even there are red executions in Monitoring.
    When a script is configured for alerting (during deployment or explicit action) this exception is written in application log for object E2E_ALERTING:
    Source type \CLASS=CL_AC_METRIC is not compatible, for the purposes of assignment, with target type \INTERFACE=IF_ATW_EVENT
    An exception with the type CX_SY_MOVE_CAST_ERROR occurred, but was neither handled locally, nor declared in a RAISING clause
    This problem is solved with note 1648119.
  2. Event Rule is not getting saved.
    When changing an event rule in SAP Solution Manager Configuration workcenter -> Technical Monitoring -> End User Experience Monitoring -> step 'Alerting' it is changed back to the original value after saving the step.
    This problem is solved with note 1720528.

Known problems in Solution Manager 7.1 SP04

  1. Event Rule is not getting saved.
    When changing an event rule in SAP Solution Manager Configuration workcenter -> Technical Monitoring -> End User Experience Monitoring -> step 'Alerting' it is changed back to the original value after saving the step.
    This problem is solved with note 1720528.

Known problems in Solution Manager 7.1 SP05

  1. No alerts are available in Alert Inbox even there are red executions in Monitoring.
    There are no alerts for EEM available in the Alertinbox even the script and its steps are marked as alert relevant in SAP Solution Manager Configuration workcenter -> Technical Monitoring -> End User Experience Monitoring -> step 'Alerting'.
    This problem is solved with note 1739161.
  2. No metrics (EEM step names) are displayed in the analysis report atached to an email notification. The problem is solved with note 1752164.

Known problems in Solution Manager 7.1 SP06

  1. No alerts are available in Alert Inbox even there are red executions in Monitoring.
    There are no alerts for EEM available in the Alertinbox even the script and its steps are marked as alert relevant in SAP Solution Manager Configuration workcenter -> Technical Monitoring -> End User Experience Monitoring -> step 'Alerting'.
    This problem is solved with note 1748968.
  2. No metrics (EEM step names) are displayed in the analysis report atached to an email notification. The problem is solved with note 1752164.

Known problems in Solution Manager 7.1 SP08

  1. No alerts are available in Alert Inbox even there are red executions in Monitoring.
    The alert inbox is completely empty and there are no alerts displayed neither on other tabs.
    This problem is caused by POWL change and can be solved with note 1736533.
  2. There are no alerts availabe in Alert Inbox for new configured EEM scripts.
    In directory browser one can see that the alert consumer flags are not set for the metrics on step level.
    This problem is caused by a repository change and is solved with note 1924786 (Metric Consumers are not defaulted while creating new metric).

 Reporting

Missing data in reporting
Even there are executions in the monitoring UI there are no entries available in reporting.
There might be several reasons for this behaviour.

  1. The script or the steps of the scripts are not reporting relevant
    Check in SOLMAN_SETUP step 6 if the flags for the Script/steps are set.
  2. The extractor is not running
    Check in extractor framework for the Solution manager SID if the extractor EEM Reporting Data is running:

    If the extractor EEM Reporting Data is not scheduled, then execute again the step BW Basic Settings of the Technical Monitoring -> End-User-Experience configuration in SOLMAN_SETUP.
    - Go to step 'BW Basic Settings';
    - Unselect the check boc 'step BW Basic Settings';
    - Save;
    - Select the check boc 'step BW Basic Settings' again;
    - Save;
  3. To prevent that scripts executed with trace falsify the normal response time reporting all executions with trace level > 0 are not reporting relevant. Check that property trace.e2etracelevel is not set permamently (neither in scope global nor in any other scope). If the property is set as in the screen shot below all executions are triggered with a trace and are therefore not reporting relevant.

  • No labels

5 Comments

  1. Former Member

    Hi,

    for the Executor Symtom "java.net.ConnectException: Connection timed out: connect", can you advise where to set the http.proxy.host, http.proxy.port and http.proxy.enable parameters?

    Regards,

    Richard

     

  2. Former Member

    Hi Thomas,

    thanks for updating with details on how to set. I have a similar requirement to set the proxy host and port in other applets installed on the SMD Agent. eg. com.sap.smd.agent.wsclients.dpc.BindingStub.e2eDpcPushCfgVersion is trying to connect using webservices to Solution Manager and I am getting the same "Connection timed out" error when the SMD agent is behind a firewall. Is there are proxyhost setting for the wsclients or dpc applets?

    regards

     

    Richard

  3. Former Member

     

    For every SAPGUI Script I recorded, it faild to replay in the Script Editor in the logon phase.
    Step 1 - openConnection is successful. I saw my user and password were entered, but than the logon step faild with the error code

    Anweisungsende erwartet (Kompilierungsfehler in Microsoft VBScript ):1025: wnd[0]/usr/pwdRSYST-BCODE.text

    This gave me some headaches until I found out that the error was, that the login password contained a quotation mark (") which could obviously be not processed properly by the Scripting Editor. Nobody would ever by free will use a quotation mark in his passwords if not forced by SAP security politics setting - but sometimes this fires back.

  4. Former Member

    Hi Thomas,

    We are experiencing the issue with similar symptom “New imported SAPGUI script fails in EEM Editor during replay” which you specified above, but the error message we are getting is different.

    We have imported a SAPGUI recording into EEM Editor and provided correct logon credentials. When we executed the script we are getting the error message as below.

    “The 'Sapgui Component' could not be instantiated. (sapfewse):605: Connection to application server broken WSATYPE_NOT_FOUND: The specified class was not found”.

     

    Our Current GUI Release is 730 with Patch Level 2

    Solution manager Release 710 with SP 13.

    Can you please suggest us on how to fix this issue.

     

    Thanks in advance.

     

    Best Regards,

    Raveendra.