Event Id 3305 and 2256, 2258 or 2949 being logged continuously on Enterprise Vault Server for Archiving Task.

Problem

Event ID's 3305 and 2256, 2258 or 2949 are logged continuously on the Enterprise Vault server. It has been verified that the System Mailbox is not hidden in the Global Address List, and that creating a new System Mailbox does not help.

Depending on the configuration of Enterprise Vault there may be a number of different event ID's logged in the Veritas Enterprise Vault event log. 

Error Message

All failed tasks experiencing this issue will log the Event ID 3305:

Event ID: 3305
Description: 
The Task '<Archiving Task>' failed to log on to Exchange server '<servername>' using mailbox 'mailbox@domain.com'.
Please ensure that the server is running and that the Vault account has sufficient permissions on the server.
V-437-3305
 

If a Mailbox Archiving Task is configured then the event ID 2256 will be logged:

Event ID: 2256
Description:
The Archiving task '<Mailbox Archiving Task>' could not be started due to startup errors.
V-437-2256

If a Journal Task is configured then the event ID 2258 will be logged:

Event ID: 2258
Description: 
The Journal Task '<Journaling Task>' could not be started due to startup errors.
V-437-2258

If a Public Folder Task is configured then the event ID 2949 will be logged:

Event ID: 2949
Description:
The Public Folder Task '<Public Folder Task>' could not be started due to startup errors 
V-437-2949

UMI Code: V-437-41443

Cause

It is possible that incorrect credentials for the remote server are stored in Windows under the Control Panel's Credential Manager.

Solution

1. Open the Control Panel > User Accounts applet.

1a. On Windows XP/2003/Vista/2008, select the Advanced tab and click the Manage Passwords button.
1b. On Windows 7/2008 R2, select the Manage your credentials.

2. Look for either a non-VSA account that is stored to connect to the Exchange server, or a VSA account with an incorrect password. Remove either such entry.

3. Restart the EV Admin Service.

4. Check the Event Viewer when the Task has restarted and see if the errors have subsided.