Archiving tasks fail due to corrupt or excessive number of Outlook mail profiles

book

Article ID: 100008333

calendar_today

Updated On:

Description

Error Message

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

Event ID: 3305
Description: 
The Task '' failed to log on to Exchange server '' 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 '' 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 '' 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 '' could not be started due to startup errors 
V-437-2949

 

A Dtrace of the relevant archiving task (ArchiveTask, JournalTask or PublicFolderTask) shows:

CMailboxHelper::CreateProfileAndSession(VaultMbxAgent-XXX-XXX-2292-1338541567-0-37-0) - Profile failed (0x80004005)
CAgentTask::Initialise - Failed to open privileged MAPI session - aborting agent startup, error [80004005]

Cause

This issue might occurs by a corrupted Outlook profile on the Enterprise Vault (EV) Server or if excessive number of Outlook mail profiles have been created. Follow these steps to confirm if excessive Outlook mail profiles have been created:

  1. Open Windows Control Panel > Profiles.
  2. Verify if the following error message is displayed:

    "The list of profiles cannot be loaded. an unexpected error has occurred"
     
  3. Verify the following Windows registry key for Outlook profiles to confirm if excessive Outlook mail profiles have been created:

    HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

OR

HKEY_CURRENT_USER> Software> Microsoft> Office> 15.0> Outlook> Profiles – (15.0 is the example version used in this article. You will need to go to the version of Office that you have installed)

Resolution

1. Rename or recreate the Windows registry key for Outlook profiles.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

  1. Stop all the Enterprise Vault services.
  2. Open the Windows registry (regedit) and browse to the following registry key:

    HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

OR

HKEY_CURRENT_USER> Software> Microsoft> Office> 15.0> Outlook> Profiles – (15.0 is the example version used in this article. You will need to go to the version of Office that you have installed)

  1. Perform right click over the registry key Profiles and click on Rename.
  2. Enter a new name to the registry such as Profiles.old. A different approach could be to delete all of the subkeys; however, this action may cause regedit to lock up and require to be terminated. 
  3. Start the Enterprise Vault services.

The Windows registry key Profiles will be recreated by Outlook once the Enterprise Vault services are started and the archiving tasks try to connect the Exchange servers.

2. Recreate a new Outlook Profile to the Task System Mailbox and confirm the mailbox is accessible.

Refer to the following Microsoft article to create a new profile in Outlook:

How to create profile and set up an e-mail account in Outlook
https://support.microsoft.com/kb/829918

 

 

Issue/Introduction

When starting an Enterprise Vault Archiving Task, it fails after 30 seconds.

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.