The following error codes indicate bottlenecks. The complete message text, generated at runtime, gives information about resolving the error.
Code |
Name |
Meaning |
---|---|---|
0 |
Unspecified |
|
104 |
Script stopped |
The administrator has stopped the EEMon script manually, e.g. for test purposes |
109 |
No data because of the low frequency of script executions |
You must move the time window to display script executions. |
201 |
OK |
|
204 |
Planned downtimes |
The administrator has scheduled a downtime, in Work Mode Management. |
208 |
Enough successful steps |
The minimum number of successfully-performed steps which you specified, was reached. |
401 |
Poor performance |
A yellow threshold which you specified, has been exceeded. |
501 |
Critical performance |
A red threshold value which you specified, has been exceeded. |
502 |
Check operations on the response, failed |
A text check, for example, failed. |
503 |
Substantive problem |
Log error (e.g. HTTP error message 500, Missing SAPGUI user interface component). |
504 |
Connection problem |
No connection (e.g. message “Target host not reachable”, “Remote system not responding”). |
505 |
Internal error |
EEMon-internal error which does not affect the system landscape to be monitored. |
508 |
Insufficient successful steps |
The minimum number of successfully-performed steps which you specified, was not reached. |
509 |
Script scheduled but not executed |
The EEMon script is scheduled, but the EEMon robot has not delivered the execution data. The delay need not mean a restriction of the monitored technical scenario. Examine whether measurement resumes soon, or there is a problem. |