VERIFIED SOLUTION i

Resolve the system agents getting stuck at 1% and no errors being logged and other agents are working fine in Confirm

Products affected: Confirm®, Confirm OnDemand

 

Issue

A System Agent in Confirm®, such as the Scheduled Reporting Agent is getting stuck at 1% and no errors are being logged and other agents are working fine including the Alerts and Notifications agent.

All registry and task processor settings appear ok.

Cause

The task processor configuration file could be corrupt.

There may also be more than one task processors configured to connect to the same database and they will be trying to run the same tasks at the same time.  This means that the job scheduler is trying to run the same task twice and it is causing the agent to stall.

Resolution

UPDATED: March 7, 2018
Recreate the task processor configuration file using the following process. This will recreate the config file from the Confirm client without picking up any existing corruption.
  • Stop the Confirm Task Processor service.
  • Log into the Confirm client, go to System Administration > System Configuration > Database Settings.
  • Make a note of the Database Config File field setting.
  • Change the Database Config File field to point at the Task Processor config file as defined in the Confirm Task Processor registry settings.
  • Log out of Confirm client.
  • Open the Task processor config file and delete all the contents.
  • Log back into the Confirm client, the profile name drop down will be blank.
  • The Database Settings screen will be displayed with no profiles and connection details.
  • Enter the required connection details for the database profiles that the Task processor needs to connect to.
  • Click Save, this adds the new connection details into the config file and also tests the connection.
  • Now change the Database Config File field back to the original client config file location.
  • Log out of Confirm client.
  • Restart the Confirm Task Processor service.


If more than one task processor is running against the database, stop one of the task processsors from connecting to the database by altering the configuration file.