Resolve Scheduled Reporting Agent failures in Confirm by reading the Task Processor logs

Products Affected: Confirm®, Confirm® OnDemand
Product Feature: Agent Performance, Ad-hoc Reporting


The Scheduled Reporting Agent in Confirm® runs but fails every time.


The Scheduled Reporting Agent is failing due to the Structured Query Language (SQL) in a particular report.


UPDATED: April 17, 2017
The location of the Task Processor log files is set within the Confirm client (Main > System Administration > System Configuration > Task Processor Settings).  If the Logging checkbox is ticked the Task Processor writes to the file specified but also, if there is an error, it will write the last 1000 lines to a file with the same name/location and with the prefix "Error".  Go to this location and look at the end of the file to find out the name of the last Scheduled Report to see if it is creating an error or retrieving a very large amount of data.

In this example "Enquires by Method and Month" is the name of the Scheduled Report that is retrieving a very large amount of data:

2015-03-09 16:45:23.8441 :  : 3872 : 26 : 2015-03-09 16:45:23.844    Scheduled Reporting Agent : DebugReport (Enquires by Method and Month): Retrieved 713732 rows

In Confirm find the Scheduled Report in question and set the Next Run Time to a period in the future so it will not run when the Scheduled Reporting Agent next runs. Then open the Scheduled Tasks screen (Main > System Administration > Scheduled Tasks) and manually run the Scheduled Reporting Agent to see if it completes one cycle.

If you suspect that recent changes to Data Sources may be impacting the Scheduled Reporting Agent you can use the Modified From fields on the Data Source filter to review Data Sources that have been changed recently. Process them to see how long they take to run and how many rows they retrieve.