End User Experience Monitoring Issue Resolution
End User Experience Monitoring is a Solution Manager functionality for monitoring the end user experience in terms of system performance or availability. In a complex IT landscape where the server is at one location and the user are accessing it from various locations across the Globe 24×7 maintaining the system performance consistent throughout all the locations is a big challenge.
With the System Monitoring functionality of Solution Manager, one can get to know whether the server is up and running but that does not guarantee that all the end users across multiple locations are able to access it and get proper performance. There can be an issue anywhere in the network between the server and the end user client. EEM helps you to tackle this issue by providing the performance and availability data from an end user perspective.
EEM robots (SMD agents) are installed on the end user machines and they religiously execute the scripts (recorded transactions for which the monitoring is required) and sends the performance and availability data to Solution Manager which displays it in the form of monitoring graphs.
One can come across many issues which configuring and operating EEM. Below mentioned are some of the issues and its resolution.
|1||If the EEM editor does not connect to the managed system or scripts are not uploading or some “exceptions” error comes.||Check the version of the EEM Editor. There are different versions of the editors accordig to the SP levels. Go to the http://wiki.sdn.sap.com/wiki/display/EEM/home, follow the link EEM downloads on the page and then download the correct version of EEM Editor.|
|2||The EEM robot in the administration window shows the SAPGUI or HTTP script selection inactive. You are not able to deploy these scripts on the robot.||The robot will only be able to run the type of scripts for which the client is installed on its host. For SAPGUI script you will need an SAP logon and for running http script the should be Java 1.5 or higher on the host of the robot.|
|3||EEM alerts not triggered in alert inbox, CX_SY_MOVE_CAST_ERROR in class CL_AC_ALERT||Its a coding error apply note 1648119 it has an attachment correction instruction 1047641.|
|4||Scenario reports is not generated- (An error was detected while parsing the E2E application configuration data)||Log on to SM59–> TCP/IP connections—> MDX Parser service, do connection test. If connection is not working then implement the note 1032461 and replace the file librfc32.dll in kernel directory OS level access will be required.
If still the report is not generated then implement note 1259109- a config.xml file is to be uploaded.
|5||The E2E traces are not starting. Some error occurs while enabling trace through the RCA workcenter.||Start the NWA log viewer, (http://<host>:port/nwa) then -> Monitoring -> Logs and Traces -> Show Default trace. You will see the error log and then troubleshoot further.|
|6||/nwa error log, no technical system could be found in the technical scenario||Write the technical scenario name in the upper case only.|
|7||Script shows connection problem. “RESULT_FAILED scripting is disabled by the server.(sapfewse):624:” , When the managed system in which the script is being played is restarted the script execution fails.||Check the “sapgui/user_scripting” scripting parameter in RZ11 and change the value to true.
After the system restart the parameter value gets changed so after every restart check the value.
|8||When you play the script in the editor it gives you the error “sapgui component could not be initiated” , set the value of sapgui.componenttrace to true. You change the value of the parameter in the script and the editor but still it gives the same error||Check the login data. The user ID and password might be incorrect. Correcting them would solve the problem.
In the script there is a component “sapgui.componenttace” but that can be edited once the script has been uploaded in the solman. So before that you need to run the script in the editor to edit it. So the message of the error is not much relevant and the source of error could be something else. One of the reason could be the incorrect login data.
|9||The monitoring UI shows that the Robot is disconnected and no execution graphs are visible but in the configuration steps the status of the robot is green, everthing running fine. For HTTP script is running fine but for GUI it shows the agent disconnected.||Remove the script from the robot and redeploy it on the robot. The script would start running.|
|10||You cannot see any system data in the Monitoring UI or jump-in to E2E Trace is not available.||The parameter “Expire in seconds” of temporary configuration should have a value higher than 60 seconds (default 1800) 2. Assign the script to a technical scenario 3. check the extractor is running or not. Open the link http://<solman>:<port>/sap/bc/webdynpro/sap/wd_efwk_adminui_config 4. Check the extractor log.|
|11||In the step 2.6 Configure EEM robots you check the robots a list appears but you cannot use the robot for EEM||make sure the robot has a name. If the robot does not have a name then it cannot be used for EEM.|
|12||Problem retrieving data from the managed system for E2E trace||The user in the read RFC should be provided the profile S_AI_SMD_E2E., go through note 1252944 and 1274287.|
|13||When you run the script with trace the script execution with trace starts but doesnt stop after the specified time period.||Check the parameter “trace.e2etracelevel” if the value is 1 then make it 0.|
|14||Extractor running into error.||Check the link http://wiki.sdn.sap.com/wiki/display/EEM/Known+problems+in+7.1
apply the latest LMSERVICE patch.
|15||How to add log off step in SAP GUI scripts.||for SAPGUI scripts the logon and logoff steps cannot be recorded but they are added automatically by the EEM Editor|
|17||The script execution stops. The monitoring UI does not show any execution.||If by any reason the agent gets disconnected from the system then you may need to assign the scripts to the robots again. Check in the script disrtibution tab and assign the scripts to the agents if they have been unassigned.|
|18||The e-mail notifications are not triggered when an alert is generated.||Do the SCOT configuration, maintain the server details and follow the Note 1581460 – SM 7.1: Steps for Auto-notification in Alert Inbox. Apply note 1739161 and reconfigure
the relevant EEM-Script.
|19||EEM Robot fails to execute SAPGUI script due to missing privilegs of MS Windows service-user “SAPService<DASID>”||Add the “SAPService<DASID>” to group Administrators and restart the EEM Robot|
|20||The editor does not connect to the Solution Manager. Gives the error “Java Version Check Failed: Service call exception; nested exception is: java.io.EOFException: Connection closed by remote host. Connection to EEM Repository (ABAP) Failed! Service call exception; nested exception is: java.io.EOFException: Connection closed by remote host.”||If there has been a version upgrade then check the editor version. There is a different editor for every SP level of solution manager. That is different for Solman 7.01 SP 25, 26 etc and for 7.1 SP1, SP2 and so on. If the editor is for the correct Solman SP level then check the connection parameters you enter. Try both the port 5XX00 and 81XX. Uncheck the “Secured” check and try again. “it cannot work if you enter the Java port only, it should be the ABAP http port. Secure means HTTPS = different ports.”|
|21||“Alerting is deactivated” in the monitoring UI the status of the script is diplayed in grey with the message alerting is deactivated.||If the execution has stopped because of agent getting stopped of system downtime then wait for a while the alerts will get active again. In the “Alerting” step in the “Step” tab, activate alerting, select the Performance or Availability columns at the relevant hierarchy level|