Enterprise Vault services do not start (login failure).
If Enterprise Vault 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 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 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 service, so you may need to stop and restart multiple 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.
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 Exchange Policy Properties dialog box, 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.
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 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:
HKEY_LOCAL_MACHINE \SOFTWARE \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: