Skip to main content

Retrieving error logs

In this article, we explain how to find and view error logs in Mosaic, including using tools and error IDs to access stack details.

Y
Written by Yusef Abulaynain
Updated over 3 months ago

Error logs from the front end - Mosaic 22.1

This feature works with Mosaic version 22.1 and above.

To retrieve error logs from Mosaic's front end please follow the below steps:

  1. Login to Mosaic, then click Tools.

  2. Click Configuration tools, then click Search Error Logs.

  3. In the error log ID field. enter the full error log ID.

  4. Click the Find Error Log icon, then copy and paste the error log into your notepad.


Error stack behind ID - Mosaic 21.2

From 21.2 the ability to take the Epoch error ID to the Configuration Tools area of the software and see the error for yourself was introduced to the build.

An example of an onscreen error looks like this:

'Error The following error has occurred. Please contact the system administrator. Error ID : mos-prod-app21681979212767_52937 Error Message : An unexpected error has occurred. Please check your last transaction as it may not have completed correctly. The error has been logged against the error ID above. Please contact your support team providing the error ID and details of the action taken immediately prior to this error.'


Configuration tools

To have the error log icon appear for you on Configuration Tools you just need the ERRLOG system function on your worker role enabled so that the button appears, and as long as the system property enableErrorLoggingToDatabase is set to true then you can be sure that errors like that of above will be captured and writing to the database.

When you input your error ID into the field the error stack will appear. You can then search this on the Customer Success Portal for further information and instructions on what to do.

If you wish to know what state, the system property is for your site then please raise a new case online and reference the title of this article but otherwise feel free to give the appropriate person permissions for this functionality and see if you are able to check any errors there and then.


Did this answer your question?