Error Message

Event ID: 41461 Some savesets cannot be archived because of an inconsistency on the Storage Queue. Enterprise Vault will automatically try to recover from this problem.|If you see several occurrences of this event, restart the Storage service.|Enterprise Vault will try again in approximately (seconds): 30

Exception logged by EVStorageQueueBroker process :
(EVStorageQueueBroker)    <49984>    EV-H    {LogExceptions.LogException} Exception: Sequence contains more than one element Info:An error occurred while invoking Void b__9().|Error Context : Getting Work Status from Storage Archive Process No. [41308] Diag: Type:System.InvalidOperationException ST:   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)|   at Symantec.EnterpriseVault.StorageQueueBroker.StorageArchiveXmlReader.SetStatusFromXMLElements(IList`1 listSavesets, List`1 xSavesets)|   at Symantec.EnterpriseVault.StorageQueueBroker.StorageQueueBrokerXmlReader.UpdateSavesetsWorkStatus(IList`1 listSavesets, String xmlResponse)|   at Symantec.EnterpriseVault.StorageQueueBroker.StorageArchiveProcessController.GetSavesetsWorkStatus(List`1 storageArchiveProcessSavesets)|   at Symantec.EnterpriseVault.StorageQueueBroker.WorkingQueuedSavesetMonitor.ProcessSavesetForStorageArchiveProcess(List`1 processSavesets, List`1 listUnprocessedSavesets)|   at KVS.EnterpriseVault.Common.COMHelper.InvokeHelper(Object COMInterface, Action act, String context, LoggingMode loggingMode, Boolean rethrow) Inner:None

Under rare circumstances EV XML parser throws an exception if there are more than one elements in the XML sequence.When this exception is raised the item does not get processed further.

There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time.  However, the issue has been addressed in the revision of the product specified at the end of this article. 
 
Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

This issue has been addressed in EV 12.5.3 and EV 14.0.