exMon is a tool with many features and therefore many errors can occur.
For exception manager to work, the user needs to select a column or combination of columns that are unique for query results. This is due to the way exception manager updates old exceptions.
To fix this issue, user needs to open exMon Administrator, open the test that is failing and change the primary key columns.
Note: that exMon Administrator can only guarantee that primary keys are unique for current data results, it cannot ensure that query will always return a unique primary key.
This failure happens when schedule’s trigger has not executed at the correct time and has exceeded it’s timeframe to do so. Usually this is due to the server being down for an extended period of time. Rather than risking crashing the server again by executing all schedules that should’ve executed while the server was down, we notify the system owner and reschedule the failed schedules.
You can manually execute vital schedules on the main server, either by using the exMon execution agent or administrator.
When a task starts failing, users often want to see how the task has been running up until that point.
Administrator and portal each have their own way to see the execution history of a task.
In the administrator you can find the execution history of all exMon tasks under General –> Audit History –> Execution History. You can then filter or search for the results you want to see. There’s also a shortcut under each task’s toolbar which opens the execution history with the list filtered on the task.
In portal you can see the execution history of tasks that are on Process/exception maps. You can find the list of tasks under Process Management –> Status, and similar to the administrator you can select the task you want to view in more detail.
There are many reasons why this can be happen, so we’ll address each one in short detail.