1. Support
  2. Knowledge base
  3. 100022349

Event ID 493: APP Analytics - Could not start RuleEngineJob.

Article: 100022349
Last Published: 2023-09-19
Ratings: 1 0
Product(s): Enterprise Vault

Problem

Enterprise Vault (EV) Discovery Accelerator (DA) includes an Analytics feature that allows additional work to be automated against accepted search results on a per Case basis. Enabling Analytics within a Case also creates a RuleEngineJob in the SQL Agent. If this RuleEngineJob is deleted incorrectly, the following error will be entered repeatedly into the DA server's EV Event Log.

Error Message

Source: Accelerator Manager

Category: None 
Event Type: Error 
Event ID: 493 
Description: APP Analytics - Could not start RuleEngineJob. View error log details. Exception:

V-437-493

Cause

The SQL Server Agent service looks for jobs to execute on a routine basis and executes them when those jobs are scheduled to be run.  For each Analytics rule, the DA configuration database contains a reference that is used by the SQL Server Agent service.  When an Analytics related job is deleted without following the Analytics disabling processing, the DA configuration database still has a reference to the now non-existent job.  That reference causes the SQL Server Agent service to attempt to locate and execute that job.  With the job no longer present, the error is thrown.
 

Solution

Complete the following steps:
1. Disable Analytics for all Cases that have Analytics enabled. For the steps to disable Analytics, see the section titled Disabling analytics on a Discovery Accelerator case in the DA Administrator's Guide (see Related Articles below for a full list of all EV product  documentation).  Disabling Analytics on all Cases and Research Folders will clear all Analytics related files, tables and jobs from the database and SQL server.  To determine which Cases or Research Folders have Analytics enabled, run the following SQL query against the DA customer database:
SELECT tc.CaseID
     , tc.Name AS 'Case Name'
     , CASE WHEN tc.FolderType = 330 THEN 'Case'
       WHEN tc.FolderType = 331 THEN 'Research Folder'
       ELSE 'Undefined'
      END AS 'Case Type'
     , tc.StatusID AS 'Case StatusID'
     , ts1.Name AS 'Case Status Name'
     , tc.AnalyticsStatusID
     , ts2.Name AS 'Current Analytics Status Name'
     , tc.LastAnalyticsStatusID
     , ts3.Name AS 'Previous Analytics Status Name'
FROM tblCase AS tc
INNER JOIN tblStatus AS ts1 ON tc.StatusID = ts1.StatusID
INNER JOIN tblStatus AS ts2 ON tc.AnalyticsStatusID = ts2.StatusID
INNER JOIN tblStatus AS ts3 ON tc.LastAnalyticsStatusID = ts3.StatusID
WHERE tc.AnalyticsStatusID IN (850, 851);
2. Stop the Enterprise Vault Accelerator Manager Service (EVAMS) on the DA server
3. Backup the DA Customer database's transaction log as follows:
  1. Log onto the SQL server with an account that has proper permissions (the Vault Service Account should have such permissions)
  2. Open Microsoft SQL Server Management Studio
  3. Expand Databases in the left pane
  4. Right click on the DA Customer database
  5. Select the Tasks option
  6. Select the Back Up... option
  7. For the Backup type:, click the drop down arrow and select Transaction log
  8. Provide the rest of the information needed (Backup set name and location)
  9. Click the OK button to execute the backup
4. When the backup completes successfully, close the SQL Management Studio and log off of the SQL Server as needed
5. On the DA Server, start the EVAMS.
6. Review the EV Event Log to ensure no new Event ID 493 errors are thrown.
7. In the DA Client, enable Analytics for Cases as needed.

Was this content helpful?

Article Languages