Enterprise Vault™ Administrator's Guide
- About this guide
- Managing administrator security
- Roles-based administration
- Working with predefined RBA roles
- Customizing RBA roles
- Day-to-day administration
- About Exchange mailbox archiving reports
- About starting or stopping tasks or services
- Monitoring journal mailboxes
- About monitoring disks
- About maintaining the SQL databases
- Using SQL AlwaysOn availability groups
- About managing vault store groups and sharing
- About managing safety copies
- About managing partition rollover
- About expiry and deletion
- Working with retention categories and retention plans
- Setting up retention folders
- Enabling archiving for new mailboxes
- About moving archives
- How Move Archive works
- About moving mailbox archives within a site
- About moving mailbox archives between sites
- About configuring Move Archive
- Running Move Archive
- Monitoring Move Archive
- PowerShell cmdlets for managing archives
- Using Enterprise Vault for records management
- Setting the default record type for users
- Common configuration scenarios
- Searching archives for items marked as records
- Automatically filtering events
- Managing indexes
- About the indexing wizards
- Managing indexing exclusions
- About the indexing PowerShell cmdlets
- Advanced Domino mailbox and desktop policy settings
- Editing the advanced settings for Domino mailbox and desktop policy
- Domino mailbox policy advanced settings
- Archiving General: Domino mailbox policy
- Archiving General: Domino mailbox policy
- Domino desktop policy advanced settings
- Advanced Exchange mailbox and desktop policy settings
- Editing the advanced Exchange mailbox and desktop settings
- Exchange mailbox policy advanced settings
- Archiving General (Exchange mailbox policy advanced settings)
- Archiving General (Exchange mailbox policy advanced settings)
- Exchange desktop policy advanced settings
- Office Mail App (Exchange desktop policy advanced settings)
- Outlook (Exchange desktop policy advanced settings)
- OWA versions before 2013 (Exchange desktop policy advanced settings)
- Vault Cache (Exchange desktop policy advanced settings)
- Virtual Vault (Exchange desktop policy advanced settings)
- Advanced Exchange journal policy settings
- Archiving General (Exchange journal policy advanced settings)
- Advanced Exchange public folder policy settings
- Archiving General (Exchange public folder policy advanced settings)
- Advanced SMTP policy settings
- Site properties advanced settings
- Editing site properties advanced settings
- Site properties advanced settings
- Content Conversion (site properties advanced settings)
- File System Archiving (site properties advanced settings)
- IMAP (site properties advanced settings)
- Indexing (site properties advanced settings)
- Skype for Business (site properties advanced settings)
- SQL Server (site properties advanced settings)
- SMTP (site properties advanced settings)
- Storage (site properties advanced settings)
- Content Conversion (site properties advanced settings)
- Computer properties advanced settings
- Editing computer properties advanced settings
- Computer properties advanced settings
- Agents (computer properties advanced settings)
- IMAP (computer properties advanced settings)
- Indexing (computer properties advanced settings)
- Storage (computer properties advanced settings)
- Task properties advanced settings
- Advanced Personal Store Management properties
- Classification policy advanced settings
- Managing the Storage queue
- Automatic monitoring
- About monitoring using Enterprise Vault Operations Manager
- About monitoring using MOM
- About monitoring using SCOM
- Managing extension content providers
- Exporting archives
- Enterprise Vault message queues
- Customizations and best practice
- Mailbox archiving strategies
- Notes on archiving based on quota or age and quota
- Notes on archiving items from Exchange Server 2010 managed folders
- About performance tuning
- Mailbox archiving strategies
- Failover in a building blocks configuration
- Appendix A. Ports used by Enterprise Vault
- Appendix B. Useful SQL queries
- Appendix C. Troubleshooting
- Installation problems
- Microsoft SQL Server problems
- Server problems
- Client problems
- Problems enabling or processing mailboxes
- Problems with Vault Cache synchronization
- Identifying and resolving Vault Cache issues on the Enterprise Vault server
- Identifying and resolving Vault Cache issues on an end-user computer
- Problems with Enterprise Vault components
- Troubleshooting: All tasks and services
- Troubleshooting: Directory service
- Troubleshooting: Exchange archiving or Journaling tasks
- Troubleshooting: Storage service
- Troubleshooting: Shopping service
- Troubleshooting: Web Access application
- Troubleshooting: All tasks and services
- Techniques to aid troubleshooting
- How to modify registry settings
- About moving an Indexing service
- Appendix D. Enterprise Vault accounts and permissions
Client synchronization status text
A client can report numerous possible statuses for both Content Cache synchronization and Header synchronization to the Enterprise Vault server.
Table: Content Cache synchronization status explains the Content Cache synchronization statuses and the steps you can take to remedy any issues on the client computer.
Table: Content Cache synchronization status
Status | Meaning and steps to remedy |
---|---|
Initializing | Content Cache is initializing. This is a normal phase for newly enabled clients before a first synchronization occurs, and is not a cause for concern. |
Not yet downloading | Content Cache has finished initializing but has not yet started downloading files. Again, this is a normal part of the Content Cache download process, and is not a cause for concern. |
Complete | Content Cache synchronization has completed successfully. Depending on your Desktop policy settings, this may or may not have involved downloading item content to the user's Content Cache. |
Waiting for file on server | Content Cache is waiting for a file to be built on the Enterprise Vault server. Content Cache waits for a PST file to be built on the Enterprise Vault server and downloads the same file to the user's local Content Cache. |
Downloading | Content Cache is currently downloading a file from the Enterprise Vault server. |
Retrying | Content Cache is retrying a download following an error communicating with the Enterprise Vault server. The client may have lost connectivity momentarily. |
BITS not available | The Microsoft Windows BITS service is not installed or not available. On the affected client computer, check to see if the Background Intelligent Transfer Service is listed as a service and is started. |
Build failed | A failure occurred on the Enterprise Vault server while building a file or as part of integrating a built file with a local Content Cache. The Enterprise Vault Outlook Add-In should retry the Content Cache download as part of the next scheduled synchronization. If this status occurs regularly for a number of users then you should investigate any possible issues on the Enterprise Vault server or client. See Identifying and resolving Vault Cache issues on the Enterprise Vault server. See Identifying and resolving Vault Cache issues on an end-user computer. |
BITS download error | The Microsoft Windows BITS feature reported an error while downloading a file from the Enterprise Vault server. The download will be retried during the next scheduled synchronization. If this status occurs regularly for an individual user then you should investigate the BITS feature on that client computer. |
Failed to add archive | The Content Cache component encountered an error when attempting to process an additionally available archive. A retry will occur during the next synchronization attempt. If this status occurs regularly for an individual user, then you should examine a client log file from the affected computer to help diagnose the underlying issue. |
Could not connect | Content Cache could not connect to the target Enterprise Vault server for the selected archive. It is unlikely that this status will ever be seen, since a connection to the Enterprise Vault server is a requirement for the Outlook Add-In to report the synchronization state. |
File locked | A client-side file that Content Cache depends on ( |
Unspecified error | Content Cache has encountered an unspecified error. See Identifying and resolving Vault Cache issues on an end-user computer. |
Unknown error | Content Cache has encountered an unknown error. See Identifying and resolving Vault Cache issues on an end-user computer. |
Table: Header synchronization status explains the Header synchronization statuses and the steps you can take to remedy any issues on the client computer.
Table: Header synchronization status
Status | Meaning and steps to remedy |
---|---|
Archive changed | The archive information for the user changed while Header synchronization was in progress. This should be resolved by the next scheduled synchronization. |
Failed (server synchronizing) | Header synchronization failed because the server was synchronizing the archive hierarchy on the Enterprise Vault server. This is a temporary state for an archive on an Enterprise Vault server and the next scheduled synchronization should complete as normal. |
Synchronization prevented | Header synchronization was prevented by user activity in Virtual Vault. While a user is performing certain actions within Virtual Vault (for example, moving folders) synchronization cannot occur. Synchronization will be retried during the next scheduled synchronization. |
Insufficient disk space | There is insufficient disk space on the client computer for header synchronization to occur. You need to increase the amount of available disk space before synchronization can complete. The Enterprise Vault Outlook Add-In needs 100MB by default to be able to synchronize. |
Failed to acquire slot | Header synchronization failed to acquire a synchronization slot from the Enterprise Vault server. This synchronization slot is in place to limit the number of concurrent header synchronizations occurring on the Enterprise Vault server. If this status occurs regularly for a large number of users, consider altering your server configuration to allow for a larger number of concurrent synchronizations. |
Could not connect | Header synchronization could not occur because the Enterprise Vault Outlook Add-In could not connect to the Enterprise Vault server. It is unlikely that this status will ever be seen, since a connection to the Enterprise Vault server is a requirement for the Outlook Add-In to report the synchronization state. |
Offline | The Enterprise Vault Outlook Add-In does not currently have a connection to the Enterprise Vault server. It is unlikely that this status will ever be seen, since a connection to the Enterprise Vault server is a requirement for the Outlook Add-In to report the synchronization state. |
Corrupt MDC | Header synchronization could not proceed due to a corrupt MDC file. You will need to delete the MDC file from the affected user's computer. |
Unknown failure | Header synchronization encountered an unknown error. See Identifying and resolving Vault Cache issues on an end-user computer. |
Complete | Header synchronization completed successfully. |
Not yet synchronizing | Header synchronization has not yet started. This might be an additionally available archive that the user has not yet selected to synchronize with Enterprise Vault. |
Pending | Header synchronization is pending, but not yet started. You should not see this status on the Vault Cache Diagnostics page, but it may be seen on client computers before synchronization has started. |
In progress | Header synchronization is in progress. You should not see this status on the Vault Cache Diagnostics page, but it may be seen on client computers during synchronization. |
Acquiring slot | The Enterprise Vault Outlook Add-In is trying to acquire a synchronization slot from the Enterprise Vault server to proceed with synchronization. You should not see this status on the Vault Cache Diagnostics page, nor on client computers. It is an internal, transient state that is replaced with another status when the synchronization slot has been either acquired or not acquired. |
Waiting for slot | The Enterprise Vault Outlook Add-In is trying to acquire a synchronization slot from the Enterprise Vault server to proceed with synchronization. You should not see this status on the Vault Cache Diagnostics page, nor on client computers. It is an internal, transient state that is replaced with another status when the synchronization slot has been either acquired or not acquired. |
Reset | Header synchronization was reset manually by the user. You should not see this status on the Vault Cache Diagnostics page, nor on client computers. It is an internal, transient state that is replaced with another status when synchronization is resumed. |
Suspended | Header synchronization was suspended by the user. You should not see this status on the Vault Cache Diagnostics page, nor on client computers. It is an internal, transient state that is replaced with another status when synchronization is resumed. |
Client Shutdown | Header synchronization was stopped due to a shutdown by the user. You should not see this status on the Vault Cache Diagnostics page, nor on client computers. It is an internal, transient state that is replaced with another status when Outlook is restarted. |
Unknown | Header synchronization encountered an unknown error. See Identifying and resolving Vault Cache issues on an end-user computer. |