Introduction
The error monitor gives access to a database-funded long-term error archive.
How to monitor error messages:
Opening the error monitor automatically loads a list of errors since midnight. The time-range for the error messages can be modified with the “Search period“ setup.
Doubleclicking an error message opens another window with an extensive error report:
For each error message, the error report delivers the following information:
General: basic information about the error (timestamp, affected module, version, command, transaction and user ).
Technical summary:
Title: simplified short description of the error message.
Message: comprehensive technical error description.
Stacktrace: System information regarding the context of the error situation.
Files: the error report provides direct access to files that are connected with the problem. The type and number of files depends on the context of the error. For example, the error report of an interface module will include the import file that caused the problem. Typical files in error reports are:
XX_slot-data.xml: XML-data of the client-/server-communication during the error condition.
XX_slot-command.xml: XML-configuration of the affected command(s).
„log.txt“: Text extract of the server log.