Event ID's 2256, 2258 or 2949 in the event log reporting that the Task could not be started due to startup errors.

Problem

After starting an Enterprise Vault Archiving Task (Mailbox, Journal, or Public Folder) the task fails.

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

Error Message

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   
                                  
 

A Dtrace of the relevant task (ArchiveTask, JournalTask or PublicFolderTask) may report the following error:

FindExchServerDn returning error 0x8007203A

Cause

In certain Active Directory environments containing Windows 2000 PDC emulators, the Enterprise Vault archiving task may attempt to communicate to these servers as if they were a Global Catalog (GC) server for the domain. These communications will fail, causing the task to stop and report the error.
 

Solution

Manually enter a GC in the Vault Administration Console:

1. Expand Enterprise Vault | Directory On.. | SiteName | Targets | Exchange | Properties of the Domain
2. Check the box to Use specific Global Catalog Server and enter a known good GC using the Fully Qualified Domain Name
3. Restart all EV services and attempt another restore


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)