TaskRunner failure post-migration

Products

• Information Centric Analytics

Issue/Introduction

The following job steps of the nightly RiskFabric Processing job fail post-migration:

• Update DB Utility Versions
• Send License Expiration Notifications
• Send Scenario Step Up Emails
• Send Email Notifications

The error message logged in the RiskFabric.TaskRunner log file and in the SQL Server Agent history log is:

[1:ERROR] Program.Main() System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The network path was not found

Environment

Release : 6.x

Component : Metric Collector

Cause

The TaskRunner executable's connection string points to the wrong database server.

Resolution

Update the connection string by following this procedure:

1. Open File Explorer on the new database server
2. Navigate to the Database Utilities folder
   
   NOTE: The default path is %SystemDrive%\Program Files\Bay Dynamics\Database Utilities\TaskRunner
   
   
3. Open the file TaskRunner.exe.config with Notepad or a text editor of your choice
4. Locate the <connectionStrings> key and edit the connectionString Data Source value to point to the correct database server
5. Save and close the file