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

Article:TECH73314  |  Created: 2009-01-10  |  Updated: 2014-03-21  |  Article URL http://www.symantec.com/docs/TECH73314
Article Type
Technical Solution

Product(s)

Environment

Issue



After starting an Enterprise Vault Archiving Task (Mailbox, Journal, or Public Folder), the Task fails, generating an Event ID 2949 or 2256 in the event log reporting that the Task could not be started due to startup errors.


Error



error 0x8007203A means

# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x203a
# for hex 0x203a / decimal 8250 :
  ERROR_DS_SERVER_DOWN                                         

# The server is not operational.
# 1 matches found for "0x8007203a"
 

 A DTRACE of the task may report the following example output:


(PublicFolderTask) GetADDomainController - using FQDN subdomain.domain.com
(PublicFolderTask) :GetADDomainController() - DsGetDcName dwResult==[1355]
(PublicFolderTask) :GetADDomainController() - 2nd DsGetDcName dwResult==[0]
(PublicFolderTask) :GetADDomainController() - 3rd DsGetDcName dwResult==[0]
(PublicFolderTask) :GetADDomainController() - returning | DC Name==[\\pdcemulator1.domain.com],| Search Format==[GC://pdcemulator1.domain.com],| GC Found==[True]
(PublicFolderTask) FindExchServerDn - Bind to Search Base: GC://pdcemulator1.domain.com
(PublicFolderTask) FindExchServerDn returning error 0x8007203A


Cause



In certain Active Directory environments containing Windows 2000 PDC emulators, the Enterprise Vault archiving tasks 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



Workaround:
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
 
Note: specifying a GC is a single point of failure and should not be considered a long term solution.
 
-------
 
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently being considered by Symantec Corporation to be addressed in the next major revision of the product.  There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
 

 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.  For information on how to contact Symantec Sales, please see  http://www.symantec.com

 

Supplemental Materials

SourceETrack
Value1057237
Description

GetADDomainController returns a domain controller that is not a GC in a multi- domain environment





Legacy ID



329569


Article URL http://www.symantec.com/docs/TECH73314


Terms of use for this information are found in Legal Notices