Cannot successfully synchronize vault cache if archive item has invalid or outdated received date.
Article ID: 100002046
Updated On:
Description
Error Message
Last synchronization was interrupted
Cause
When Enterprise Vault(EV) archives an item, the "Creation Date" or "Received Date" of the item is recorded as IdDateTime. In certain circumstances, mail items may arrive with an invalid, or outdated date (I.E. 01/01/1901). This is due to how the item was originally created and has been identified in the following types of messages:
a. Spam messages.
b. System generated or automatically generated messages.
c. Original source Exchange with an invalid System Time.
Vault Cache (VC) synchronizes messages, newest first, and will stop at 01/01/1970. Items with invalid dates prior to this will fail to download.
This will cause the VC Status tab to show "Last synchronization was interrupted" although detail tab shows "Complete".
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Manually create a registry key value "OVCCLastCompletedTime"(REG_SZ) with recent date value (i.e 2010-01-01T01:01:31)
HKEY_CURRENT_USER
\SOFTWARE
\KVS
\Enterprise Vault
\Client
\
\OVCCLastCompletedTime (REG_SZ)
Notes:
a. This is a short-term solution.
b. Items with an IdDateTime older than this value will not download to the local VC.
Note: The below instructions should only be performed by a SQL Database Administrator.
1. Run the following query below to locate the affected savesets and user(s).
--------------- Copy Below ---------------
-- Alter the VaultStoreDatabaseName to reference the Vault Store Database
-- Alter the below DECLARE to reference the MailboxAlias
USE VaultStoreDatabaseName
DECLARE @MailBoxAlies nvarchar(255) = 'MailboxAlias'
DECLARE @OldDateTime datetime = '1970-01-01'
SELECT Distinct SS.IdTransaction, SS.IdDateTime AS IdDateTime_Ascending, ME.MbxAlias, ME.LegacyMbxDN, ME.DefaultVaultId
FROM Saveset SS JOIN ArchivePoint AP on SS.ArchivePointIdentity = AP.ArchivePointIdentity
JOIN EnterpriseVaultDirectory.dbo.ExchangeMailboxEntry ME ON AP.ArchivePointId = ME.DefaultVaultId
WHERE SS.IdDateTime < @OldDateTime and ME.MbxAlias = @MailBoxAlies
ORDER BY ME.MbxAlias, SS.IdDateTime ASC
--------------- Copy Above ---------------
2. Perform a Full Database Backup of the Vault Store Database prior to performing any changes.
3. Update the IdDateTime value for the items returned with a recent date (i.e. 2005-01-01 01:01:01.000)
Note: It is recommended to adjust this value to a recent value as VC requests items in 3 month increments, newest first. The farther back VC must trawl, the longer the VC synchronization will take to complete.
4. Reset the affected VC user(s).
Resolution
Veritas Corporation has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.
There are currently no plans to address this issue by way of a cumulative hotfix or service pack 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, but is not 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 https://www.veritas.com.
Issue/Introduction
Additional Information
