Event ID 4004 — DNS Server Active Directory Integration

Event ID 4004 — DNS Server Active Directory Integration

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

You can configure the DNS Server service to use Active Directory Domain Services (AD DS) to store zone data. This makes it possible for the DNS server to rely on directory replication, which enhances security, reliability, and ease of administration.

Event Details

Product: Windows Operating System
ID: 4004
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.1
Symbolic Name: DNS_EVENT_DS_ZONE_ENUM_FAILED
Message: The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "%2". The event data contains the error.

Resolve
Troubleshoot AD DS and restart the DNS Server service

The DNS Server service relies on Active Directory Domain Services (AD DS) to store and retrieve information for AD DS-integrated zones. This error indicates that AD DS is not responding to requests from the DNS Server service. Ensure that AD DS is functioning properly, troubleshoot any problems, and then restart the DNS Server service.

For information about troubleshooting AD DS, see Active Directory Troubleshooting Topics  (http://go.microsoft.com/fwlink/?LinkId=95789).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To restart the DNS Server service:

  1. On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, expand Roles, expand DNS Server, and then expand DNS.
  3. Right-click the DNS server, click All Tasks, and then click Restart.

If the problem continues, restart the computer and then use Server Manager to confirm that the DNS Server service has started.

To restart the computer:

  • Click Start, click the arrow next to the Lock button, and then click Restart.

To confirm that the DNS Server service has started:

  1. On the DNS server, start Server Manager.
  2. In the console tree, expand Roles, and then click DNS Server.

The System Services list shows the state of the DNS Server service.

Verify

Ensure that Event IDs 4523 and 4524 are being logged and that no events in the range 4000 to 4019 appear in the Domain Name System (DNS) event log.

Related Management Information

DNS Server Active Directory Integration

DNS Infrastructure

Related:

Error Getting DDE data processing Message for user ‘{user name}’.

Details
Product: Exchange
Event ID: 4004
Source: MSExchangeMig
Version: 6.0
Component: Migration Wizard
Symbolic Name: GW_ERR_NODDEDATA
Message: Error Getting DDE data processing Message for user ‘{user name}’.
   
Explanation
Dynamic Data Exchange (DDE) is used for inter-process communication. No data returned. Insufficient system resources may be causing this problem.
   
User Action
Restart Exchange server and run migration again.

Related:

‘%1’ rule collection could not be loaded because of configuration errors. Messages will be deferred. The description of the configuration error is: ‘%2’

Details
Product: Exchange
Event ID: 4004
Source: MSExchange Messaging Policies
Version: 8.0
Symbolic Name: RuleCollectionLoadingError
Message: ‘%1’ rule collection could not be loaded because of configuration errors. Messages will be deferred. The description of the configuration error is: ‘%2’
   
Explanation

This Error event indicates that the rule collection specified in the event description could not be retrieved from Active Directory. The journaling rules are stored in Active Directory as rule collection. This event may occur when one or more of the following conditions are true:

  • The Exchange server that logged this event cannot find any Active Directory servers in the organization.

  • The specified rule collection is corrupted or does not exist.

  • There are configuration issues as specified in the event description.

    Note   For more information about the Journaling agent, see Overview of Journaling in the Exchange 2007 Online Help.

   
User Action

To resolve this error, follow one or more of these steps:

  • Make sure that the Microsoft Exchange server that logged this event is able to communicate with one or more Active Directory servers available in the organization.

  • Increase the diagnostic logging level on the Rules counter of the MSExchange Messaging Policies performance object. You can increase logging by running the following Exchange Management Shell command:

    Set-EventLogLevel “MSExchange Messaging Policies\Rules” -Level High

    For more information about increasing logging, see How to Change Logging Levels for Exchange Processes.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

    Important   After you have completed troubleshooting this issue, return logging to the default level by running the following command:

    Set-EventLogLevel “MSExchange Messaging Policies\Rules” -Level Lowest

  • If the recommended steps do not resolve this error, contact Microsoft Product Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Process %1: Unable to find a public folder server for organizational unit (OU) %2.

Details
Product: Exchange
Event ID: 4004
Source: MSExchange Availability
Version: 08.00.0632.000
Symbolic Name: PublicFolderServerNotFound
Message: Process %1: Unable to find a public folder server for organizational unit (OU) %2.
   
Explanation

This Error event indicates that Microsoft® Exchange Availability service could not find a public folder server to retrieve the Schedule+ Free Busy data for one or more legacy Exchange mailboxes. A legacy Exchange mailbox refers to a mailbox that resides on an Exchange 2000 or Exchange 2003 server. The Exchange Availability service is responsible for retrieving Schedule+ Free Busy data for a set of mailboxes. If the mailbox resides on a computer that is running Exchange 2007 Server, the Availability service retrieves the data from the mailbox itself. However, if the mailbox resides on an Exchange 2000 or Exchange 2003 server, the Availability service retrieves the data from public folders. This event occurs when the Exchange Availability service does not locate a public folder server for legacy Exchange mailboxes. A public folder server is an Exchange server that has a public folder store. The organizational unit (OU) specified in the event description refers to an Administrative Group under which the Exchange server that is missing the public folder store is installed.

   
User Action

To resolve this error, make sure that the mailbox store that has legacy Exchange mailboxes points to a valid public folder store. You can confirm this by looking at the General tab of Mailbox Store Properties. For more information, see the following articles at the Microsoft Exchange Server TechCenter:

If you find that the required public folder store has been deleted or the mailbox store that has legacy Exchange mailboxes does not point to a valid public folder store, contact Microsoft Product Support Services. For more information, visit the Microsoft Help and Support Web site.

Note  If you aren’t already doing so, consider running the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mailflow, and better manage disaster-recovery scenarios. Go to the Toolbox node of Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is “%2”. The event data contains the error.

Details
Product: Windows Operating System
Event ID: 4004
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_ZONE_ENUM_FAILED
Message: The DNS server was unable to complete directory service enumeration of zone
%1. This DNS server is configured to use information obtained from Active
Directory for this zone and is unable to load the zone without it. Check
that the Active Directory is functioning properly and repeat enumeration
of the zone.
The extended error debug information (which may be empty) is “%2”.
The event data contains the error.
   
Explanation

The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a high load on the domain controller or the failure of other domain controller services.

   
User Action

If this message appears repeatedly, restart the DNS Server service, and then look in the event log for other events occurring at the same time that could be causing this problem.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center
.

Related:

Process %1: Unable to find a public folder server for organizational unit (OU) %2. The service will attempt to find a random server, which may take a longer time to service the request.

Details
Product: Exchange
Event ID: 4004
Source: MSExchange Availability
Version: 8.0
Symbolic Name: PublicFolderServerNotFoundForOU
Message: Process %1: Unable to find a public folder server for organizational unit (OU) %2. The service will attempt to find a random server, which may take a longer time to service the request.
   
Explanation

This Error event indicates that Microsoft® Exchange Availability service could not find a public folder server to retrieve the Schedule+ Free Busy data for one or more legacy Exchange mailboxes. A legacy Exchange mailbox refers to a mailbox that resides on an Exchange 2000 or Exchange 2003 server. The Exchange Availability service is responsible for retrieving Schedule+ Free Busy data for a set of mailboxes. If the mailbox resides on a computer that is running Exchange 2007 Server, the Availability service retrieves the data from the mailbox itself. However, if the mailbox resides on an Exchange 2000 or Exchange 2003 server, the Availability service retrieves the data from public folders. This event occurs when the Exchange Availability service does not locate a public folder server for legacy Exchange mailboxes. A public folder server is an Exchange server that has a public folder store. The organizational unit (OU) specified in the event description refers to an Administrative Group under which the Exchange server that is missing the public folder store is installed.

   
User Action

To resolve this error, make sure that the mailbox store that has legacy Exchange mailboxes points to a valid public folder store. You can confirm this by looking at the General tab of Mailbox Store Properties. For more information, see the following articles at the Microsoft Exchange Server TechCenter:

If you find that the required public folder store has been deleted or the mailbox store that has legacy Exchange mailboxes does not point to a valid public folder store, contact Microsoft Product Support Services. For more information, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: