The following error is logged in the Event Log on the Enterprise Vault Server
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 16/11/2012 00:00:20
Event ID: 40966
Task Category: File System Synchronization Task
Level: Error
Keywords: Classic
User: N/A
Computer: EV Server
Description:
A program fault has raised an exception.
Exception: An entry with the same key already exists.
Diagnostic:
Type: System.ArgumentException
Reference:
Command Line: "C:\Program Files (x86)\Enterprise Vault\EvFsaSyncTask.exe" -URL:tcp://xx.xx.xx.xx:57123/4298f576_231e_457a_a061_bf8095ccf364/KVS.EnterpriseVault.ProcessManager61879347 -CUSTOM:1569722952782284DB4D6A991E50CAF661012g00EV8|False|
Application Domain: EvFsaSyncTask.exe
Process Id: 2796
Thread Id: 3612
Stack Trace: at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.SortedList`2.Add(TKey key, TValue value)
at KVS.EnterpriseVault.FileServerArchive.FileShareResolver.EnumShareS(String serverName)
at KVS.EnterpriseVault.FileServerArchive.FileShareResolver.Initialise(String fileServerId, String fileServer)
at KVS.EnterpriseVault.FileServerArchive.FileSystemTaskInfo.GetFileServer(String fileServerEntryId, Boolean loadVolumesForFileServer)
at KVS.EnterpriseVault.FileServerArchive.FileSystemTaskInfo.AddVolume(Boolean alwaysAdd, String fileServerEntryId, String volumeId, String volumeName, Boolean loadVolumesForFileServer)...
V-437-40966
When the FSA Archiving or Synchronization starts processing, the shares on the target file server are enumerated. If the list contains a duplicate share name, this will generate the 'An entry with the same key already exists' exception.
The duplicate share names may not look exactly the same. An example of a duplicate set is:
Assessment and Aßessment
The simplest solution is to rename the duplicate share once it has been identified