Error Message

Enterprise Vault Event Log Error 1:

Event ID: 93
Description:
APP AT - Customer ID: 3 - An error occurred while updating Vaults for Vault Store: ID=23 KVS ID: 16D80487B3FFA5145AFBB560448DFF7FA1210000evlab.local. System.Threading.ThreadAbortException: Thread was being aborted.
at KVS.Accelerator.Application.Vaults.UpdateVaults(Int32 VaultStoreID, String KVSVaultStoreEntryID, Boolean bUpdateIndexServer, Boolean updateOnlyVaultServers, IndexServerLookup indexServerLookup)

 

Enterprise Vault Event Log Error 2:

Event ID: 361
Description:
APP AT - Customer ID: 34 - An error has occured when synchronization to the directory (VaultStores). System.Threading.ThreadAbortException: Thread was being aborted.
at KVS.Accelerator.Application.Vaults.Synchronize(ManualResetEvent stopEvent, Boolean updateOnlyVaultServers)
at KVS.Accelerator.Application.VaultStores.Synchronize(Boolean IncludeVault, ManualResetEvent stopEvent, Boolean updateOnlyVaultServers)
at KVS.Accelerator.Application.VaultStores.Synchronize(Boolean IncludeVault, ManualResetEvent stopEvent)
at KVS.Accelerator.Server.ADSynchronisationController.DirectorySynchronizeNow()

 

Enterprise Vault Event Log Error 3:

Event ID: 359
Description:
APP AT - Customer ID: 34 - An error has occured when synchronization to the directory. System.Threading.ThreadAbortException: Thread was being aborted.
at KVS.Accelerator.Server.ADSynchronisationController.DirectorySynchronizeNow()

 

When a Vault Store is created, EV records the Vault Store in the EnterpriseVaultDirectory database in table VaultStoreEntry.  Each Vault Store is identified with an unique VaultStoreEntryID, regardless of the name given to the Vault Store.  This allows multiple Vault Stores to be created with the same name.

CA and DA periodically synchronize select information from the VaultStoreEntry table into the tblVaultStore table in the CA or DA Customer database.  This synchronization occurs when the Enterprise Vault Accelerator Manager Service (EVAMS) is started and every 6 hours thereafter (by default).  This synchronization can also be manually triggered through the Accelerator Client.

The data synchronized into the tblVaultStore table includes, but is not limited to, the Vault Store name and its associated VaultStoreEntryID.  The Accelerator Client displays Vault Stores by name.  If multiple Vault Stores exist in the tblVaultStore table with the same name, only the first instance of the name may be viewed in the DA Case-level Archives sub-tab, depending on the Vault Store selections in the Case properties; all Vault Stores may be visible in the CA or DA Client's Application tab's Archives sub-tab.

When a Vault Store is created in EV and synchronized to the Accelerators and then deleted from EV, EV removes that information from the VaultStoreEntry table; however, the Accelerators retain the information for the deleted Vault Store in the tblVaultStore table.  If that Vault Store did not contain any Archives, the Application tab's Archives sub-tab in the Accelerator Client will show the deleted Vault Store with no associated Archives and the deleted Vault Store cannot be selected.  This is expected behavior, but can cause confusion when two or more Vault Stores exist with the same name as a Vault Store without any associated Archive(s) cannot be selected to be searched within any CA Department or DA Case.  This may also prevent other Vault Stores that do have archives from being selected in the Application tab's Archives tab.  For any CA or DA search to be able to run against archives in a Vault Store, the Vault Store must be selected in the Application tab's Archives sub-tab and the Vault Store's archives to be searchable must also be selected in order to be available for all CA Departments or DA Cases.

 

 To confirm this issue exists:

1. To determine if there are duplicate Vault Stores in the tblVaultStore table of the CA or DA Customer database, run the following SQL query against the Customer database:

SELECT VaultStoreID
     , VaultStoreEntryID
     , Name
     , Type
     , DirectoryServer
     , SiteID
     , MostRecentArchiveDeletionUTC
     , StoreEnabled
FROM tblVaultStore
GROUP BY VaultStoreID
     , VaultStoreEntryID
     , Name
     , Type
     , DirectoryServer
     , SiteID
     , MostRecentArchiveDeletionUTC
     , StoreEnabled
     HAVING (COUNT(VaultStoreEntryID) > 1 OR COUNT(Name) > 1)
ORDER BY VaultStoreID;

If this query returns any rows, investigate each Vault Store listed to determine if its entry exists in the EnterpriseVaultDirectory database's VaultStoreEntry table by completing the following steps.

2. Run the following SQL query against the EnterpriseVaultDirectory database, replacing VaultStoreName with the name of the Vault Store showing no archives in the DA Client:

DECLARE @VaultStoreName nvarchar(32) = 'VaultStoreName'; -- Edit Vault Store name here
SELECT VaultStoreName, VaultStoreEntryId
FROM EnterpriseVaultDirectory.dbo.VaultStoreEntry
WHERE VaultStoreName LIKE '%' + @VaultStoreName + '%';

For example:

DECLARE @VaultStoreName nvarchar(32) = 'Vault Store 1'; -- Edit Vault Store name here
SELECT VaultStoreName, VaultStoreEntryId
FROM EnterpriseVaultDirectory.dbo.VaultStoreEntry
WHERE VaultStoreName LIKE '%' + @VaultStoreName + '%';

3. Run the following SQL query against the DA customer database, again replacing VaultStoreName with the name of the Vault Store showing no archives in the DA Client -

DECLARE @VaultStoreName nvarchar(32) = 'VaultStoreName'; -- Edit Vault Store name here
SELECT Name, VaultStoreEntryID
FROM tblVaultStore
WHERE Name LIKE '%' + @VaultStoreName + '%';

For example:

DECLARE @VaultStoreName nvarchar(32) = 'Vault Store 1'; -- Edit Vault Store name here
SELECT Name, VaultStoreEntryID
FROM tblVaultStore
WHERE Name LIKE '%' + @VaultStoreName + '%';

4. Compare the outputs from both queries to see which Vault Stores exist in the VaultStoreEntry table and correspond to entries in the tblVaultStore table.

Any Vault Store that exists in the tblVaultStore table that does not exist in the VaultStoreEntry table is a Vault Store that has been deleted from EV and cannot be used within CA or DA.

For assistance with resolving this issue, please contact technical support and reference this article.

 

There are no Archives listed for a Vault Store in an Enterprise Vault (EV) Discovery Accelerator (DA) Case under the Archives tab nor in the Application tab's Archives sub-tab of DA, or in an Compliance Accelerator (CA) Department where the Vault Store may show two instances with one having Archives and the other none. In the EnterpriseVaultDirectory database's VaultStoreEntry table, the Vault Store only shows once. In the CA or DA Customer database's tblVaultStore table, two entries exist with different values in their VaultStoreEntryID columns.