Event ID 41352: Index Volumes Processor - Indexing engine unreachable

Event ID 41352: Index Volumes Processor - Indexing engine unreachable

Article: 100007814
Last Published: 2018-06-12
Ratings: 0 0
Product(s): Enterprise Vault

Problem

The Index Volumes Processor generates errors with Event ID 41352 when attempting to process a particular Index Volume.

Error Message

Type : Error
Date : 2/26/2012
Time : 12:13:34 PM
Event : 41352
Source : Enterprise Vault 
Category : Index Volumes Processor
User : N/A
Computer : EVSERVER.Domain.Com
Description:
The processing of the Synchronize Sub task has stopped following errors.

Synchronize Sub task ID: 12A345B6789CDE01234F5A6B78C9DE0121110000evserver_5
Reason: Undefined
Error Type: NonCritical

Description: Indexing engine unreachable.

 V-437-41352

A DTrace of 'EVIndexVolumesProcessor' shows: 

1704 12:12:50.556 [12624] (EVIndexVolumesProcessor) <Agent Thread for 12A345B6789CDE01234F5A6B78C9DE0121110000evserver_5:13732> EV-H {IndexingWCFProxy`1} Exception: Error in deserializing body of reply message for operation 'SearchCollectionStatus'. Info: Diag: Type:System.ServiceModel.CommunicationException ST:
Server stack trace: 
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters)
   at System.ServiceModel.Dispatcher.ProxyOperationRuntime.AfterReply(ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Symantec.EnterpriseVault.Indexing.IndexingEngineService.VelocitySrvRef.VelocityPort.SearchCollectionStatus(SearchCollectionStatusRequest request)
   at lambda_method(ExecutionScope , VelocityPort )
   at KVS.EnterpriseVault.Runtime.WCF.WCFProxy`1.Invoke[TResult](Expression`1 method)
   at Symantec.EnterpriseVault.Indexing.Common.IndexingWCFProxy`1.Invoke[TResult](Expression`1 method) Inner:System.InvalidOperationException: There is an error in XML document (1, 1238). ---> System.OverflowException: Value was either too large or too small for an Int32.
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at System.Xml.XmlConvert.ToInt32(String s)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVelocityPort.Read23_crawlerstatus(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVelocityPort.Read66_vsestatus(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVelocityPort.Read67_SearchCollectionStatusResponse(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVelocityPort.Read463_Item()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer26.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest)

 

Cause

The Index Volume is reporting values that are either too large or too small for an Int32 value (2 ^ 32).

Solution

The following workarounds are available for 10.0.0 and 10.0.1

Workaround #1:

The last date and time that the Index Volume was updated can be examined in the IndexVolumes table within the EnterpriseVaultDirectory database, a backup of the given Index Volume can then be restored.  Once restored an Index Verify and Synchronize should be conducted against this Index Volume.

The IndexVolume table will have a FolderName entry:  '12A345B6789CDE01234F5A6B78C9DE012_5'; this can then be used with the IndexRootPathEntryId to find the path and folder of the specific Index Volume.  In addition this entry in the table will have a column named 'WorkPendingLastUpdatedUTC', which can be used as a guide to determine the timeframe of the backup to restore.

Following SQL query can be used for determining the detailed information of the Index Volume.

Use EnterpriseVaultDirectory
Select CE.ComputerName, IRPE.IndexRootPath, IV.FolderName, IV.WorkPendingLastUpdatedUTC
From IndexVolume IV
Inner Join IndexRootPathEntry IRPE
 On IV.IndexRootPathEntryId = IRPE.IndexRootPathEntryId
Inner Join IndexingServiceEntry ISE
 On ISE.ServiceEntryId = IRPE.IndexServiceEntryId
Inner Join ComputerEntry CE
 On CE.ComputerEntryId = ISE.ComputerEntryId
Where IV.FolderName ='12A345B6789CDE01234F5A6B78C9DE012_5'

 

Workaround #2:

A Rebuild of the Index Volume can be conducted.  For details refer to the associated document:  100024435

 

This issue has been resolved in the following release:

Enterprise Vault 10.0.2

https://www.veritas.com/support/en_US/article.100004492.html


References

Etrack : 41352 Etrack : 2980386

Was this content helpful?