Enabling and editing retry SQL connection in TimeXtender Orchestration

This guide shows how to enable or edit TimeXtender Orchestration to ensure database connections do not stop tasks from executing

Tasks that start in TimeXtender Orchestration require a connection to the database that stores information about the TimeXtender Orchestration instance. When the task fails to connect to the database, for whatever reason, it can be good to enable the retry logic.

To enable or edit the retry logic, follow these steps:

1. Open TimeXtender Orchestration and Data Quality client
2. Open Execution History under General -> Audit History -> Execution History

   

3. Here you can see all the servers (and in some cases local user machines) that execute TimeXtender Orchestration tasks. At a minimum, you should want to enable the retry on the most common servers you see.
   1. An easy way to see the most common servers is by right-clicking the server name column header and selecting Group by this columns

   

4. Now connect to the servers you want to enable or edit the retry logic on through Remote Desktop or other similar tools
5. Find TimeXtender Orchestration and Data Quality installation on the server. It is usually located under C:\Program Files\exMon\Bin
6. Open the file ExpectusConfig.config
7. Look for the values ExmonConnectionSleepSeconds and ExmonConnectionRetryCount
   1. If you find these values edit them for your needs. 'Retry count' is the number of times TimeXtender Orchestration will try to connect to the database after a failure. 'Sleep seconds' is the number of seconds TimeXtender Orchestration will wait between retries.
   2. If you do not find these values you can paste these values to the file:
          <add key="ExmonConnectionSleepSeconds" value="20"/>
          <add key="ExmonConnectionRetryCount" value="2"/>
      The file should then look similar to this:

   

8. When you have added this logic to the most common servers that execute TimeXtender Orchestration, you are done and TimeXtender Orchestration should now retry connecting to the database on failure.