System cannot find file during processing

Products

Information Centric Analytics

Issue/Introduction

One or more of the following steps of the nightly RiskFabric Processing job fail (step IDs noted parenthetically):

Metric Collector (22)
Update DB Utility Versions (23)
Send License Expiration Notifications (25)
Send Scenario Step Up Emails (26)
Send Email Notifications (27)

One or more of the following corresponding errors are captured in the SQL Server Agent history log:

Executed as user: [<domain>\]<account>. The process could not be created for step 22 of job 0x08792F55D0A7C1488FF33273CF89270D (reason: The system cannot find the file specified).  The step failed.

Executed as user: [<domain>\]<account>. The process could not be created for step 23 of job 0x08792F55D0A7C1488FF33273CF89270D (reason: The system cannot find the file specified).  The step failed.

Executed as user: [<domain>\]<account>. The process could not be created for step 25 of job 0x08792F55D0A7C1488FF33273CF89270D (reason: The system cannot find the file specified).  The step failed.

Executed as user: [<domain>\]<account>. The process could not be created for step 26 of job 0x08792F55D0A7C1488FF33273CF89270D (reason: The system cannot find the file specified).  The step failed.

Executed as user: [<domain>\]<account>. The process could not be created for step 27 of job 0x08792F55D0A7C1488FF33273CF89270D (reason: The system cannot find the file specified).  The step failed.

Environment

Version : 6.x

Component : Database Utilities

Cause

The path to the command specified in the failing RiskFabric Processing job step is either incomplete or points to a location that does not exist on the filesystem.

Resolution

To resolve this error, first identify the path specified in the failing job step(s) by following this procedure:

Open SQL Server Management Studio (SSMS)
Connect to the Database Engine hosting the RiskFabric relational database
From the File menu, select New > Query with Current Connection
A new query editor window will open

Copy the following query and paste it in the new query editor window:

SELECT     js.step_id,
           js.step_name,
           js.command
FROM       msdb.dbo.sysjobsteps AS js
INNER JOIN msdb.dbo.sysjobs AS j
        ON js.job_id = j.job_id
WHERE      j.[name] = N'RiskFabric Processing' AND
           js.subsystem = N'CmdExec';

Execute the query by pressing the F5 key, clicking the Execute button in the SQL Editor toolbar, or selecting Execute from the Query menu

Determine whether the path(s) returned in the command column for each failing job step exist on the filesystem. If a path does not exist, either create it on the filesystem or modify the command path for the job step by following this procedure:

Open SSMS
Connect to the Database Engine hosting the RiskFabric relational database
In Object Explorer, navigate to SQL Server Agent > Jobs
Right-click the RiskFabric Processing job and select Properties
The Job Properties - RiskFabric Processing window will open
Select the Steps page
Select the failing job step and click the Edit button
The Job Step Properties - <step-name> window will open
Modify the path to the executable provided in the Command window
NOTE: paths containing spaces should be enclosed in double-quotation marks ("), as in the following example:
```
"E:\Program Files\Bay Dynamics\Database Utilities\TaskRunner\TaskRunner.exe" TaskRunner.Tasks.Custom.DBUtilitiesVersionUpdater
```
Click the OK button to close the Job Step Properties - <step-name> window
Repeat steps 6 through 8 for each step that is failing
Click the OK button to close the Job Properties - RiskFabric Processing window