A guide about the Error Log Dashboard in Good Sign
Required User Rights
To be able to access the Error Log, you’ll need at least the following user right: 4510 Menu – Error Log.
Error Log Dashboard
The Log menu contains administrative dashboards for system logs to be used by system administrators. The Error Log dashboard can be found under the Logs menu: Logs > Error Log.
Figure 1: Error Log dashboard
The Error Log contains rare errors that have occurred in the database. These errors are typically due to bad data not allowing a transaction to complete and this results in a syntax error or missing mandatory data. The nature of the log is technical and requires expertise, but it gives indication to the nature of the event. In the event of a user reporting an issue, the system administrator can check if the error log has entries in the timeframe the user had the issue.
System administrators should check the error log every now and again and contact Good Sign if there are errors logged without any evidence of malfunction. This will help eliminate unnecessary entries to the error log.
The Error Log dashboard has normal Good Sign Grid functionalities as explained in the How to Manage the Good Sign Grid guide.
Tip: It can be especially useful to filter this grid by the Error Procedure, to see if the same procedure has failed before
The error dashboard contains:
- Error Log ID – Unique ID for a specific error log
- Log Time – The date and time that an error occurred
- Error Number – Database engine error number, explained in the Error Message column
- Error Severity – Database engine error severity
- Error State – Database engine state number of the error
- Xact State – Database engine transaction state of the error
- Error Procedure – The SQL procedure causing the error log entry
- Error Line – Failed line in the SQL procedure code
- Error Message – Explains the error in question e.g., invalid column name etc.
The error log is by nature deeply technical, related to the database, and provides input to advanced troubleshooting.
For system administrators, the most important things to look for are the Error Procedure and the Error Message. These provide understandable hints on what might be wrong.
Example
The Error Procedure dbo.invoice_closeperiod is related to Invoice Scheduling. Should such an error occur, there might be a problem in generating invoices. In this case, Error Message gives an indication to the problem. For example, there is a bad sentence in the Rule of the invoice schedule.