Forum Discussion

wilsond3010's avatar
12 years ago
Solved

Virtual Vault's not syncing

We recently went through a upgrade from EV9 to EV10.4 but find some users unable to setup and sync to vault cache.

 

Only thing I am noticing in the logs in the. 

DisablePST is not set in the registry

Would this stop the vault cache from being created?

 

 

Registry Settings:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
 "FixedPreviewPane" = dword:0000000c
 "LastPSTSearch" = "20131224"
 "OVShowSyncDetails" = dword:00000001
 "OVSyncOnTop" = dword:00000000
 "OLBarState" = dword:00000000
 "NoPendingSaveMsg" = dword:00000001
 "LoggingLevel" = dword:80000003
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\14414D5DCBBCD411820A00508B64CF34
 "OVRootDirectory" = "C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\"
 "OVStoreVersion" = "8.0.3.1857.0"
 "OVEnabled" = dword:00000001
 "OVStatus" = dword:00000004
 "OVStoreSize" = dword:0000a400
 "OVMDCLastSyncTime" = "2013-12-24T18:02:42"
 "OVMDCNextSyncTime" = "2013-12-24T16:58:10"
 "OVMDCLastGoodSyncTime" = ""
 "VirtualVaultConfiguredProfiles" = "Profile
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\PSTsMarked
 
Directory Listing of Offline Vault:
24/12/2013 18:04:56.810[2568]: PVHelper::GetWorkingDirectory: 0x0
24/12/2013 18:04:56.810[2568]: PVHelper::GetRootDirectory: 0x0
24/12/2013 18:04:56.810[2568]: DesktopConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.810[2568]: DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.810[2568]: ~DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.810[2568]: ~DesktopConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.811[2568]: [Offline Config] Root Directory: C:\Documents and Settings\ecanfiel\Local Settings\Application Data\KVS\Enterprise Vault\
24/12/2013 18:04:56.811[2568]: ~PVHelper::GetRootDirectory: 0x0
24/12/2013 18:04:56.811[2568]: DesktopCommon::OpenDefaultStore: 0x0
24/12/2013 18:04:56.812[2568]: ~DesktopCommon::OpenDefaultStore: 0x0
24/12/2013 18:04:56.813[2568]: [Offline Config] Working Directory: C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\
24/12/2013 18:04:56.813[2568]: ~PVHelper::GetWorkingDirectory: 0x0
C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\100647E8D52D42E459128DEB5E5415E841110000evsite.mdc    12/24/2013  12:04    271360
C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\1008C7D36AAD91447BB02DE274673D46C1110000evsite.mdc    12/24/2013  12:04    271360
C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\1008DF4F2FF746B4E9FAF66C13E5CE6711110000evsite.mdc    12/24/2013  12:04    271360
C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\100B6DBB6A010C741B31A72844DF6AC701110000evsite.mdc    12/24/2013  12:04    271360
C:\Documents and Settings\username\Local Settings\Application Data\KVS\Enterprise Vault\14414D5DCBBCD411820A00508B64CF34\100F1C53CB754DE49BF59343F17D3C8E01110000evsite.mdc    12/24/2013  12:04    271360
 

 
24/12/2013 18:04:56.880[2568]: DisablePST is not set in the registry
 

Mapisvc.inf File Contents:
[Services]  
LiveMeeting=Live Meeting Transport  
CRMSTORE=Microsoft Dynamics CRM  
MSCRM AB=Microsoft Dynamics CRM Address Book  
EVMSP=Virtual Vault  
MSFAX XP=Fax Mail Transport  
[LiveMeeting]  
Providers=LMXP  
PR_SERVICE_DLL_NAME=lmxp.dll  
PR_SERVICE_SUPPORT_FILES=lmxp.dll  
PR_SERVICE_DELETE_FILES=lmxp.dll  
PR_RESOURCE_FLAGS=SERVICE_SINGLE_COPY  
PR_SERVICE_ENTRY_NAME=ServiceEntry  
[LMXP]  
PR_PROVIDER_DLL_NAME=lmxp.dll  
PR_RESOURCE_TYPE=MAPI_TRANSPORT_PROVIDER  
PR_PROVIDER_DISPLAY=Live Meeting Transport  
[CRMSTORE]  
Providers=CRMSTOREP  
PR_SERVICE_DLL_NAME=CRMPRV.dll  
PR_SERVICE_SUPPORT_FILES=CRMPRV.dll  
PR_SERVICE_DELETE_FILES=CRMPRV.dll  
PR_SERVICE_ENTRY_NAME=MSServiceEntry  
PR_RESOURCE_FLAGS=SERVICE_SINGLE_COPY | SERVICE_NO_PRIMARY_IDENTITY  
[CRMSTOREP]  
PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER  
PR_PROVIDER_DLL_NAME=CRMPRV.dll  
PR_PROVIDER_NAME=Microsoft Dynamics CRM  
PR_PROVIDER_DISPLAY=Microsoft Dynamics CRM  
PR_STORE_SUPPORT_MASK=STORE_CREATE_OK  
[MSCRM AB]  
Providers=MSCRM ABP  
PR_DISPLAY_NAME=Microsoft Dynamics CRM Address Book  
PR_SERVICE_DLL_NAME=CRMPRV.dll  
PR_SERVICE_SUPPORT_FILES=CRMPRV.dll  
PR_SERVICE_DELETE_FILES=CRMPRV.dll  
PR_SERVICE_ENTRY_NAME=ServiceEntry  
PR_RESOURCE_FLAGS=SERVICE_SINGLE_COPY | SERVICE_NO_PRIMARY_IDENTITY  
[MSCRM ABP]  
PR_RESOURCE_TYPE=MAPI_AB_PROVIDER  
PR_PROVIDER_DLL_NAME=CRMPRV.dll  
PR_PROVIDER_DISPLAY=Microsoft Dynamics CRM Address Book  
PR_STORE_SUPPORT_MASK=STORE_CREATE_OK | STORE_RESTRICTION_OK  
[EVMSP]  
PR_SERVICE_DLL_NAME=EVMSP.DLL  
PR_SERVICE_ENTRY_NAME=ServiceEntry  
PR_RESOURCE_FLAGS=SERVICE_NO_PRIMARY_IDENTITY  
Providers=MS_EVMSP  
PR_SERVICE_SUPPORT_FILES=EVMSP.DLL  
PR_SERVICE_DELETE_FILES=EVMSP.DLL  
[MS_EVMSP]  
PR_RESOURCE_TYPE=MAPI_STORE_PROVIDER  
PR_PROVIDER_DLL_NAME=EVMSP.DLL  
PR_RESOURCE_FLAGS=STATUS_NO_DEFAULT_STORE  
PR_DISPLAY_NAME=Virtual Vault  
PR_PROVIDER_DISPLAY=Virtual Vault Message Store Provider  
[MAPI]  
ServiceOrder=  
[Default Services]  
MSFAX XP=Fax Mail Transport  
[MSFAX XP]  
PR_RESOURCE_FLAGS=SERVICE_SINGLE_COPY|SERVICE_NO_PRIMARY_IDENTITY  
PR_SERVICE_ENTRY_NAME=ServiceEntry  
PR_SERVICE_SUPPORT_FILES=FXSXP.DLL  
PR_SERVICE_DLL_NAME=FXSXP.DLL  
Providers=MSFAX XPP  
PR_DISPLAY_NAME=Fax Mail Transport  
[MSFAX XPP]  
PR_PROVIDER_DISPLAY=Fax Mail Transport  
PR_DISPLAY_NAME=Fax Mail Transport  
PR_RESOURCE_FLAGS=STATUS_NO_DEFAULT_STORE  
PR_RESOURCE_TYPE=MAPI_TRANSPORT_PROVIDER  
PR_PROVIDER_DLL_NAME=FXSXP.DLL  
 
24/12/2013 18:04:56.901[2568]: PSTs disabled in Mapisvc.inf
24/12/2013 18:04:56.901[2568]: Unicode PSTs disabled in Mapisvc.inf
24/12/2013 18:04:56.901[2568]:  
24/12/2013 18:04:56.901[2568]: PVHelper::GetOnlineDatabaseList: 0x0
24/12/2013 18:04:56.902[2568]: DesktopConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.902[2568]: DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.902[2568]: ~DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.902[2568]: ~DesktopConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.902[2568]: ~PVHelper::GetOnlineDatabaseList: 0x0
24/12/2013 18:04:56.903[2568]: PVHelper::IsRemoveOVSet: 0x0
24/12/2013 18:04:56.903[2568]: ~PVHelper::IsRemoveOVSet: 0x0
24/12/2013 18:04:56.903[2568]: DesktopCommonConfig::GetConfigValue: 0x0
24/12/2013 18:04:56.903[2568]: DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.903[2568]: ~DesktopCommonConfig::GetClientStoreKey: 0x0
24/12/2013 18:04:56.904[2568]: DesktopCommonConfig::GetSetting: 0x0
 

 

 

  • So I found this:

     

    Enterprise Vault creates MDC files for each additional Archive end users have access to regardless of the choice to synchronize the additional Archives into Vault Cache.

    Article:TECH200200  |  Created: 2012-11-28  |  Updated: 2013-08-29  |  Article URL http://www.symantec.com/docs/TECH200200

    Which means there was a server side fix for an issue in 10 sp4.

    You do have those entries in the client log.  But then I found this in the Updates.htm in the Changes affecting Outlook users and requiring new Outlook Add-In section:

    Users with access to a large number of archives experienced errors with Vault Cache synchronization [2983983]

    This issue occurred when the Vault Cache advanced setting Synchronize archive types in the Exchange desktop policy was set to All mailbox archives or All mailbox and shared archives. The issue affected users with access to a large number of archives. Vault Cache synchronization failed and users experienced out of memory errors, even when the primary mailbox archive was the only archive selected for synchronization with Vault Cache.

    This has been fixed. A user with access to a large number of archives can now successfully enable a few of them for Vault Cache synchronization. Errors may still occur if the user enables too many archives for Vault Cache synchronization.

    It looks to me from the log the affected user has permission to a lot of archives. If that is the case you might consider pushing the new client out.


    Regards,

     

12 Replies