Client add-on logging for Virtual Vault does not currently provide details as to the reason why it may be in a Read Only state.
|Article:TECH169023|||||Created: 2011-09-07|||||Updated: 2012-06-20|||||Article URL http://www.symantec.com/docs/TECH169023|
There are a number of reasons why a local Virtual Vault may be in a Read Only state. The logging does not currently provide explicit details as to the specific cause.
During the reading of the Enterprise Vault hidden message within the mailbox the following may be identified:
During the IsOpAllowed check, the following may be identified:
EVMSP: <Inbox> [Policy::IsOpAllowed] Enter
EVMSP: <Vault - LastName, FirstName>[EVMsgStore::IsReadOnly] Enter
EVMSP: <Vault - LastName, FirstName>[EVMsgStore::IsReadOnly] Exit: S_OK
EVMSP: <Inbox> [Policy::IsOpAllowed] Operation:InterStoreItemMoveOrCopyInToBeArchived, Allowed: false, Store ReadOnly: true,
CanReorg: false, CanDelete: false, CanArchive: false, CanRestore: false,CanIntraStoreCopy: false
EVMSP: <Inbox>[Helper::MapReadOnlyReasonAndThrow] Enter
EVMSP: <Inbox>[Helper::MapReadOnlyReasonAndThrow] Exit: MAPI_E_NO_ACCESS
EVMSP: <Inbox> [Policy::IsOpAllowed] Exit: S_OK
This issue has been addressed in the following releases:
Enterprise Vault 10.0.1
Enterprise Vault 9.0.4
Enterprise Vault 8.x
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 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. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
"VV_ForceReadOnly=true" due to MAPI_E_NO_ACCESS, however unable to determine root cause.
Article URL http://www.symantec.com/docs/TECH169023