Event ID 6003 — DNS Server Zone Transfer

Event ID 6003 — DNS Server Zone Transfer

Updated: November 13, 2007

Applies To: Windows Server 2008

Domain Name System (DNS) enhances fault tolerance and load balancing by providing for server redundancy. For any given zone, a DNS server can act as a primary master server, which is the authority for a zone, or as a secondary server, which obtains its zone data from the zone’s primary master server or another secondary server. This process is known as zone transfer.

Event Details

Product: Windows Operating System
ID: 6003
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_UDP_ZONE_TRANSFER
Message: The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full zone transfers must be made using TCP.

Resolve

This is a normal condition. No further action is required.

Related Management Information

DNS Server Zone Transfer

DNS Infrastructure

Related:

The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full zone transfers must be made using TCP.

Details
Product: Windows Operating System
Event ID: 6003
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_UDP_ZONE_TRANSFER
Message: The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full zone transfers must be made using TCP.
   
Explanation

The request was ignored because the server requesting the transfer has no authority over the requested zone.

Related:

The Application log file could not be opened. %1 will be used as the default log file.

Details
Product: Windows Operating System
Event ID: 6003
Source: EventLog
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_DefaultLogCorrupt
Message: The Application log file could not be opened. %1 will be used as the default log file.
   
Explanation

The Application log file is corrupted. The default log file will continue to be used as the log file until the Application log file is repaired and the system is restarted.

   
User Action

Ask the person with administrative rights on your computer to determine the cause of the corruption.

Related:

Error creating IFF PRImary and SECondary files in – {file name}. Error Code: {error code}.

Details
Product: Exchange
Event ID: 6003
Source: MSExchangeMig
Version: 6.0
Component: Migration Wizard
Symbolic Name: IFM_CREATEFILE_FAILED
Message: Error creating IFF PRImary and SECondary files in – {file name}. Error Code: {error code}.
   
Explanation
Migration Wizard tried to write to a file or disk, but the operation was not successful.
   
User Action
Check the disk for space and errors. Verify that the migration account has Write permissions for the folder that will store the IFF files. Use the error code to determine the cause of the error. For more information about primary and secondary files, see the Exchange online documentation.

Related:

%1: Failed to create the log directory: %2 because of the error: %3. Logs will not be generated until the problem is corrected.

Details
Product: Exchange
Event ID: 6003
Source: MSExchange Common
Version: 8.0
Symbolic Name: FailedToCreateDirectory
Message: %1: Failed to create the log directory: %2 because of the error: %3. Logs will not be generated until the problem is corrected.
   
Explanation

This Error event indicates that the log directory that is specified in the event description could not be created. This event may occur when one or more of the following conditions are true:

  • The path of the log directory is invalid. For example, it contains an unmapped drive.

  • The path of the log directory contains a directory with read-only permission.

  • The object specified in the event description does not have the required permissions to create the directory.

   
User Action

To resolve this Error event, follow these steps:

  • Make sure that the log directory path that is specified in the event description is valid.

  • Make sure that the path of the log directory does not contain any directory with read-only permissions.

  • Search the error message specified in the event description on Search the Support Knowledge Base (KB) on Microsoft Help and Support center.

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: