You notice while using Information Centric Analytics (ICA) that data are stale or missing on one or more dashboards. Data in the Analyzer may also be stale or missing. When you check the job status of the RiskFabric Processing or RiskFabric Intraday Processing jobs in the console by navigating to Admin > Integration > Job Status, the Last Run Outcome for the job is Cancelled. Using SQL Server Management Studio (SSMS) to check the job status under SQL Server Agent > Jobs, you see an error similar to the following logged in the job history:
Executed as user: <domain>\<account-name> The step was canceled (stopped) as the result of a stop job request.
NOTE: a stopped or cancelled processing job differs in nature from a processing failure. If the processing job completed with failures or appears to be hung, this article is not applicable.
Version : 6.x
Component : Microsoft SQL Server
...\Program Files\Microsoft SQL Server\MSSQL<n>.<instance-name>\Log
SQLServerAgent service successfully stopped.
SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
Service Broker manager has shut down.
.NET Framework runtime has been stopped.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Agent (<instance-name>) service entered the stopped state.
The SQL Server (<instance-name>) service entered the stopped state.
In addition to reviewing both Windows and SQL Server logging, contact the server administrator and/or database administrator (DBA) for assistance with determining why the job was stopped. The server may have been shutdown recently for maintenance, software installation, or testing. Services may have been stopped for the same reasons. These events may be evident in the logs but lack context or an explanation that your server and database administrators can provide.