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
Specific problems
Enterprise Vault tasks and services do not start (login failure).
If Enterprise Vault tasks and services do not start and report a login failure, the most likely cause of the problem is that the password that has been supplied for the Vault Service account is wrong. If you supply an incorrect password, there will be login failures from all Enterprise Vault tasks and services.
Error while enabling mailbox for user /o=aaaa/ou=bbbbb/cn=Recipients/cn=ccccc, error sending enabled message.
Enterprise Vault cannot send the enable mailbox message. This message is stored in a file called EnableMailboxMessage.msg on the Exchange Mailbox task computer.
Changes to an Enterprise Vault task or service do not take effect.
For many of the settings that you can change, you must stop and restart the appropriate Enterprise Vault task or service so that it can obtain the new settings. There are some settings that affect more than one task or service, so you may need to stop and restart multiple tasks and services.
Mailboxes with no associated Windows account are not archived.
This is the correct behavior. The Exchange Mailbox task automatically disables archiving for such mailboxes.
BCC recipients are missing from a message.
If you archive an unsent message with BCC recipients and then restore it, the BCC recipients are missing from the restored message.
Re-installing the Outlook Add-In to a different folder does not work.
If you remove the Outlook Add-In and then install it to a different folder, Outlook may not refresh its cache and so may not recognize the new location.
To force Outlook to see the new installation, do the following in the order listed:
Exit Outlook.
Remove the Enterprise Vault Outlook Add-In from the computer.
Start and then exit from Outlook.
Reinstall the Enterprise Vault Outlook Add-In.
Start Outlook.
Items cannot be deleted from archives.
This may not be a problem at all. There is a five-minute delay before the Index service catches up with a user deleting something from an archive, so users should wait some time before checking that items have been deleted.
Extra copy of an item when archive fails.
If an item cannot be archived for some reason, and you have chosen not to delete the original item after archiving on the Archiving Actions tab of the Enterprise Vault Exchange policy properties, it is possible that the user may have an extra copy of the item.
User cannot store items in an archive.
Following a power or disk failure, Enterprise Vault may need to reconstruct indexes for one or more archives. If Enterprise Vault is reconstructing indexes for some archives, it rejects all archive and retrieval operations for those archives until the reconstruction is complete, so users of those archives cannot archive or retrieve items. A user whose archive index is being reconstructed cannot archive items, but does not receive any error message. Other archives are unaffected by the replay operations, so archive and retrieval operations can continue normally. The solution is to wait until Enterprise Vault has finished reconstructing the indexes.
Archiving appears to work, but the log shows an error.
If the error message is An error was detected whilst accessing the Vault Database "vaultstore", the password to the vault store may have been changed but the Storage service has not been stopped and restarted. Stop the Storage service and restart it so that the service uses the new password.
Error: RPC Server is Unavailable.
You can receive a message that an RPC Server is unavailable in the following situations:
When you are using the Administration Console to add Enterprise Vault tasks or services.
When you are running the Enterprise Vault Configuration Program to configure your system.
When you are remotely managing a computer that is running Enterprise Vault tasks and services.
Each Enterprise Vault computer requires a registered IP address, and the DNS properties for the TCP/IP protocol must be defined.
You may see this problem if the computer on which you are configuring the Enterprise Vault tasks and services does not have any WINS servers defined, and you have chosen not to enable DNS for Windows Resolution on the TCP/IP Protocol property page for WINS. You can either use DNS for service control management or enable DNS for Windows resolution.
If this does not solve the problem, set up the Administration Console computer to use LanMan names instead of DNS names to connect to Service Control Manager. To do this, set the following registry string value to 1:
On a 32-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \Admin \UseLanmanNameForSCM
On a 64-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \Admin \UseLanmanNameForSCM
Items never become eligible for archiving, or manual archives do not work, or an item cannot be restored.
All of these problems can happen if an Enterprise Vault server does not have the necessary Windows codepages installed. If you need to install extra languages, see the following article in the Microsoft Knowledge Base:
Microsoft Message Queue Server: MQIS Initialization Error.
There is a known MSMQ Server problem that results in the following error message:
Error: 0xc00e0013 No connection with the Site's controller.
Alternatively, the following error may be logged in the Windows Application Event Log:
MQIS Database Initialization Error.
These errors may be caused by the lack of, or the misplacement of, the ODBC System Data Source Name (DSN) used to connect SQL Server to the MQIS database. For more information on how to solve this problem, see the following article in the Microsoft Knowledge Base: