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

This message is displayed when the Data Insight indexer component fails to update the index with metadata. The metadata is retrieved for a share or a site collection from the file server or a SharePoint server.  As a result, Data Insight moves the scan databases to the indexer/err folder in the Data directory. You can find the message on the Events page of  the Data Insight Management console.


Some of the possible causes of failure of the indexer component are:
 

  • Insufficient memory on the Indexer node
     
  • Corrupt indexes
     
  • Corrupt scan database files

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2013-06-27 19:54:06 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 determine the exact cause of the failure:

  1. Check the resource consumption on the Indexer node for the file server or web application. In the Events page under the Origin column you can find the Indexer node where the failure occurs.

Failure to update index with scan data might happen when both the following conditions are met:

 

  • The memory usage on the Indexer node is high.

 

  • There is not enough memory for idwriter.exe to process  the scan files.
  1. Open a command window on the Indexer node for the file server or web application. Change the working directory to DataInsightInstallDir\bin. To check data integrity of indexes, enter:

    configcli execute_job IndexCheckJob

    To check if the job is complete, enter:

    configcli list_jobs

The output of the command displays an asterisk (*) next to the currently running jobs. After the IndexCheckJob job, check the idxcheck.0.log file for any reported index corruption.

  1. On the Indexer node, change the working directory to DataInsightInstallDir\bin, if it is not currently your working directory. Change the logging level for services. Enter:

    configcli loglevel com.symc.matrix ALL

    Move the scan databases from the DataDir\indexer\err folder to the DataDir\inbox directory, and run IndexWriterJob. Enter:

    configcli execute_job IndexWriterJob

If scan database files are moved to the DataDir\indexer\err folder again, you may find the reason for update failure in the commd.0.0.log file. The commd.0.0.log file is present in the DataInsightInstallDir\log folder.

 

If scan database files continue to be moved to the DataDir\indexer\err folder, contact Symantec Technical Support.

 

Note: The default path for DataInsightInstallDir is C:\Program Files\Symantec\Data Insight, and the default path for DataDir is C:\DataInsight\Data. You can change these default paths during the installation process. In that case, the values of DataInsightInstallDir and DataDir will change accordingly.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service