A backlog of items waiting to be indexed may occur when using a Hitachi Data Systems HCP as the Partition Storage Location
Problem
A backlog of items waiting to be indexed may occur when using a Hitachi Data Systems HCP as the Partition Storage Location and Enterprise Vault is running on a Windows 2008 R2 server.
Error Message
A dtrace of EVIndexVolumesProcessor will show the output below:
EVIndexVolumesProcessor) <Work Item enqueuing thread:9764> EV-M {INDEXVOLUMESMANAGER.EN_US} IVM --> Manager Queue Controller: there are no free slots in the Work Item Queue, will try later.(EVIndexVolumesProcessor) <Agent Thread for 1146C2C67783BAF414D54250D68C67KF9testvault_142:126848> EV-H {SYNCHRONISATIONWORKITEM.EN_US} Error of type [NonCritical] occured whilst processing work item [1146C2C67783BAF414D54250D68C67KF9testvault_142]. Error Description [Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.Exceptions.IndexVolumesProcessorStartTimeoutException: Timed out waiting for [Agent Thread for 1146C2C67783BAF414D54250D68C67KF9testvault_142] to start after [1800] seconds.| at Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.State.WorkerThreadBase.WaitForStart(Boolean throwOnTimeout)| at Symantec.EnterpriseVault.Indexing.IndexVolumesProcessor.StateProcessingBase.ResumeProcessing()].
Event ID 41380 may also logged with the error:
Type : Error
Date : 8/15/2012
Time : 12:34:54 AM
Event : 41380
Source : Enterprise Vault
Category : Trace (Index Query Server)
User : N/A
Computer : evserver1.testdomain.local
Description:
Index volume agent failed to start due to time out.
Index Volume ID: 1770A2229803F9B44B843AFFEA11BD97C1110000evserver1.testdomain.local_73
Error: Timed out waiting for [Agent Thread for 1770A2229803F9B44B843AFFEA11BD97C1110000evserver1.testdomain.local_73] to start after [1800] seconds.
V-437-41380
Cause
An interaction between Windows and the Hitachi Data Systems HCP Streamer Software results in StorageCrawler becoming unresponsive to requests from EVIndexVolumesProcessor.
Solution
Apply the Microsoft hotfix available from KB2719306:
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.