Event ID 504 — DNS Server Configuration

Event ID 504 — DNS Server Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

The DNS server configuration consists of the settings that determine how the DNS server will function on a network and how those settings are stored and retrieved when they are needed.

 

Event Details

Product: Windows Operating System
ID: 504
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_REG_ZONE_CREATION_FAILED
Message: The DNS server could not create zone %1 from registry data. One or more of the zone registry key values could be corrupted or the zone file is missing. Use the DNS console to replace or repair any corrupted registry key values or confirm that the zone database is available. For more information, see "Configure zone properties" in the online Help.

Resolve
Correct zone data

A registry value that contains information for a zone is corrupt or incorrect and must be corrected. You can use Server Manager to delete the zone and then recreate it.

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

To use Server Manager to recreate a zone:

  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. Expand the DNS server, and then expand the folder that contains the zone.
  4. Right-click the zone, and then click Delete.

    Note: If you cannot delete the zone using this method, you must use Registry Editor to delete the registry key for the zone.

  5. Right-click the folder, and then click New Zone.
  6. Follow the instructions in the wizard to recreate the zone.

To delete the zone key in the registry:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. On the DNS server, click Start.
  2. In Start Search, type regedit, and then press ENTER.
  3. In the console tree, expand the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones
  4. Right-click the key for the zone, and then click Delete.

Verify

To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly.

To verify DNS configuration settings:

  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, double-click Roles, double-click DNS Server, and then double-click DNS.
  3. Right-click the DNS server, and then click Properties.
  4. Review the settings on each tab, and verify that they contain the intended values.
  5. Expand the DNS server.
  6. Expand a zone folder, right-click a zone, and then click Properties.
  7. Review the settings on each tab, and verify that they contain the intended values.
  8. Repeat steps 6 and 7 for each zone.

To verify that DNS client computers can resolve names properly:

  1. On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER.

If the client can resolve the name, the ping command responds with the following message:

Pinging
hostname [ip_address]

Note: The name resolution is successful even if the ping command reports that the destination is unreachable.

If the client cannot resolve the name, the ping command responds with the following message:

Ping request could not find host
hostname

Related Management Information

DNS Server Configuration

DNS Infrastructure

Related:

Event ID 504 — RD Gateway Server Configuration

Event ID 504 — RD Gateway Server Configuration

Published: January 8, 2010

Applies To: Windows Server 2008 R2

For remote clients to successfully connect to internal network resources (computers) through a Remote Desktop Gateway (RD Gateway) server, the RD Gateway server must be configured correctly. The RD Gateway server must be configured to use an appropriate Secure Sockets Layer (SSL)-compatible X.509 certificate, and authorization policy settings must be configured correctly. Remote Desktop connection authorization policies (RD CAPs) specify who can connect to the RD Gateway server. Remote Desktop resource authorization policies (RD RAPs) specify the internal network resources that clients can connect to through an RD Gateway server.

Event Details

Product: Windows Operating System
ID: 504
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_LOG_EVENT_ENABLED
Message: Logging was enabled for the following RD Gateway event: “%1”.

Resolve

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

Related Management Information

RD Gateway Server Configuration

Remote Desktop Services

Related:

() The database engine lost one table called . It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 504
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The database engine lost one table called <name>. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation

This event occurs only when an error is encountered during offline repair.

   
User Action

Perform an application-level integrity check of the database to ensure application-level data integrity.

Related:

process name (process id) nameThe database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 504
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) nameThe database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation
This event occurs only when an error is encountered during offline repair.
   
User Action
Perform an application-level integrity check of the database to ensure application-level data integrity.

Related:

The DNS server could not create zone %1 from registry data. One or more of the zone registry key values could be corrupted or the zone file is missing. Use the DNS console to replace or repair any corrupted registry key values or confirm that the zone database is available. For more information, see “Configure zone properties” in the online Help.

Details
Product: Windows Operating System
Event ID: 504
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_REG_ZONE_CREATION_FAILED
Message: The DNS server could not create zone %1 from registry data. One or more of the zone registry key values could be corrupted or the zone file is missing. Use the DNS console to replace or repair any corrupted registry key values or confirm that the zone database is available. For more information, see “Configure zone properties” in the online Help.
   
Explanation

The DNS registry entries are EnableRegBoot, Forwarders, ForwardingTimeout, IsSlave, and ListenAddress.

   
User Action

To delete the specified registry entry:

1. Click Start, and then click Run.
2. Start a registry editor (Regedit.exe or regedt32.exe).
3. Open the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters subkey.
4. Right-click the specified entry in the right pane, and then click Delete.
5. Close the registry editor and restart the computer.

To recreate the registry entry:

1. In DNS Manager, right-click the DNS server name, and then click Properties.
2. Recreate the specified entry by choosing the appropriate option in the Server Properties dialog box.
3. Click OK.
4. Click DNS on the menu bar, and then click Update Server Data Files. If the RpcProtocol entry is specified, move all your database files to another folder, and then remove and reinstall DNS using Network and Dial-up Connections in Control Panel.

Related:

%1 (%2) %3The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

Details
Product: Exchange
Event ID: 504
Source: ESE
Version: 8.0
Symbolic Name: REPAIR_BAD_TABLE
Message: %1 (%2) %3The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.
   
Explanation

This Warning event occurs only when an error is encountered during offline repair.

   
User Action

To resolve this warning, perform an application-level integrity check of the database to ensure application-level data integrity.

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: