Windows Desktop Search (WDS) reconciles its index of Enterprise Vault's DB files multiple times

Article:TECH163879  |  Created: 2011-07-04  |  Updated: 2013-08-29  |  Article URL http://www.symantec.com/docs/TECH163879
Article Type
Technical Solution

Product(s)

Issue



Each time Outlook is started, and an archived item is opened via Vault Cache/Virtual Vault an index reconciliation takes place between the DB file and WDS Index. The DB files are used and created by Enterprise Vault for Virtual Vault /Vault Cache.  If this is allowed to complete and Outlook is restarted, the same DB is accessed again and the process repeats itself.


Error



Outlook Search Logs will show the below each time the DB is opened. 

2011/06/08|14:28:16:374|Marking store for reconciliation: The store was last
opened on a different machine|0|||||||||||OK

Outlook logging can be be enabled using the registry key below. The version number will depend on your version of Outlook being used.  (Please ensure you backup your registry before making any changes)

[HKEY_CURRENT_USER\Software\Microsoft\Office\version number\Outlook\Search]
"EnableLogging"=dword:ffff0000


(so Outlook generates log files in %temp%\Outlook logging)


Cause



The root cause of the issue is the registry key below. When an item is accessed the corresponding DB file is added to an Outlook temporary profile. This causes the entry in the key below to be reset, and Outlook and WDS to perform reconciliation between all the items in the DB file and the WDS index. If another item is accessed in the same DB file in the same Outlook session nothing else happens. However if Outlook is restarted and an item is accessed again in the same DB file, reconciliation will occur again.

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Search\Catalog\DB name


Solution



Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation 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 Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com
 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Supplemental Materials

SourceETrack
Value2344159


Article URL http://www.symantec.com/docs/TECH163879


Terms of use for this information are found in Legal Notices