Unable to create Archive Points for Folder targets with similar names in the Vault Administration Console (VAC)

Problem

In some languages, there can be different representations for a character. For instance, the word Assessment may be written with the letter ‘ß’ as Aßessment.  This is because the letter ‘ß’ (Sharp S) represents two ‘s’ characters in the German language.

An example of a typical German word that uses the ‘sharp S’ character is Straße, meaning street, which can also be written as Strasse.

With the above example, if there are two folders with the names Straße and Strasse, depending on the database collation, the interpretation of the folder names will translate to the same result when creating an Archive Point for the second Folder target, and an error will be displayed by the New Folder wizard.

It is important to note that this condition will only occur if the two folders are present at the same Folder Path.

Error Message

From the Vault Admin Console the UI returns the error: Failed to save or update the details for folder  

In Event Viewer the following error event is logged:

Event ID 13405.

A constraint violation error was detected while accessing the Vault Database

Description:  
Violation of UNIQUE KEY constraint 'Unique_FileServerFolderEntry_VolumeEntryId_FolderPath'. Cannot insert duplicate key in object 'dbo.FileServerFolderEntry'. The duplicate key value is (19EED805DC529CC4890CC38C07169C95C1011000EV, Aßessment).  SQL Command:  INSERT FileServerFolderEntry (FolderEntryId, FolderPolicyEntryId, VolumeEntryId, FolderPath, ArchiveThisFolder, ArchiveSubFolders, IgnoreVolumeRules) VALUES ( ?, ?, ?, ?, ?, ?, ?)  Additional Microsoft supplied information: Source:       Microsoft OLE DB Driver for SQL Server Number:       0x80040e2f SQL State:    23000 Native Error: 00002627 HRESULT 0x80040e2f 

Cause

This issue is primarily due to the default collation value set on the Enterprise Vault Directory database. If issue is limited to FSA Targets, it may be addressed by changing the SQL collation at the Database Table Column level.

Please contact Support for assistance on how to execute the script to modify the collation.

Solution

Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
 
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see http://www.veritas.com
 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.