Error Code details
V-378-1312-202
Severity: Error 
Component: Data Insight 
Message:
Error updating audit information for \<file server name>/<share name>. Input file <file name> moved to data/indexer/err folder. Or Error updating audit information for http://<Web application>/<site collection URL>. Input file <file name> moved to data/indexer/err folder.
Description:

This message is displayed on the Events page of the Data Insight Management console when the indexer component of Data Insight fails to update the index with the audit information that is retrieved for a share or site collection from the file server or a SharePoint server.

As a result, Data Insight moves the audit databases from the Data directory to the indexer/err folder. Possible reasons for the failure of the indexer component are insufficient memory on the Indexer node, corrupted indexes, and corrupted audit database files.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2014-10-14 19:54:37 PST
Platform: Windows Server 2003 (x86-64), Windows Server 2003 (IA-64), Windows Server 2003 (x86-32), Windows Server 2008 (x86-64), Windows Server 2008 (IA-64), Windows Server 2008 (x86-32), Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
Release: Generic
Content:

To find the exact cause of the failure, do the following:
 

1. Check the resource consumption on the Indexer node for the file server or web application.


The name of the Indexer node where the failure occurs is displayed on the Events page under the Origin column.


If the memory usage on the Indexer node is high and the available memory for idxwriter.exe to process the audit files is insufficient, it might cause a failure to update index with the audit data.
 

2. Run IndexCheckJob to check the data integrity of indexes.

  1. Open a command window on the Indexer node for the file server or web application.
     
  2. Change the working directory to Data_Insight_Installation_Directory\bin.
     
  3. Run the following command:

              configcli execute_job IndexCheckJob

  1. To check whether the job is complete, run the following command. The output of the command displays an asterisk (*) against the jobs that are currently running.

              configcli list_jobs

  1. After the IndexCheckJob is complete, check the idxcheck.0.log file to see whether any index corruption is reported.

3. Do the following:

  1. On the Indexer node, make sure that your current working directory is Data_Insight_Installation_Directory\bin.
     
  2. Run the following command to change the logging level for services:

              configcli loglevel com.symc.matrix ALL

  1. Move the audit databases from Data_Directory\indexer\err folder to Data_Directory\inbox folder.
     
  2. Run IndexWriterJob by using the following command:

              configcli execute_job IndexWriterJob

  1. If the audit database files are moved to the Data_Directory\indexer\err folder again, check the commd.0.0.log file to find out the reason for the failure to update index with the audit data. The commd.0.0.log file is in the Data_Insight_Installation_Directory\log folder.
     
  2. Contact Symantec Technical Support if the audit database files continue to be moved to the Data_Directory\indexer\err folder.

Note: The default value for Data_Insight_Installation_Directory is C:\Program Files\Symantec\Data Insight. For Data_Directory, the default value is C:\DataInsight\Data. The default directories can be changed during the installation. In that case, the values for Data_Insight_Installation_Directory and Data_Directory are changed accordingly.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service