Microsoft KB Archive/300143

= HOW TO: Use Error Tracking on a Windows 2000 Web Server =

PSS ID Number: 300143

Article Last Modified on 4/30/2003

-

The information in this article applies to:


 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows 2000 Server

-



This article was previously published under Q300143





IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



IN THIS TASK

 * SUMMARY
 * Recommendations for Understanding your Web Server Environment
 * Enabling Error Tracking
 * Troubleshoot
 * REFERENCES



SUMMARY
This step-by-step article describes how to use Error Tracking on a Windows 2000-based Web server.

Recommendations for Understanding Your Web Server Environment
Use the following guidelines to better understand your Web server environment:
 * Understand how you want to define your Web presence.
 * Understand the goals or business requirements of the Web server environment.
 * Understand the resources that you must have to complete your goals and business requirements.
 * Understand that you will logically and physically distribute the required resources.
 * Plan the physical information, logical information, service flow, and administrative topologies for your Web server environment.

For more information about these guidelines, see the &quot;A Blueprint for Building Web Sites Using the Microsoft Windows Platform&quot; white paper. To do so, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndna/html/dnablueprint.asp

back to the top

Enabling Error Tracking
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To enable error tracking in Windows 2000 Server, you can create a REG_DWORD value named EventlogLevel in the following location in the registry:



Use the following table to determine which events are logged in the DNS server log in Event Viewer:

Note When you edit the registry to change this registry value, the change is not effective until you restart the DNS server.

You can use the DNS Server Troubleshooting Tool (Dnscmd.exe) included with the Windows 2000 Support Tools to change this registry value immediately. When you do this, you do not have to restart the DNS server.

For example, to use Dnscmd.exe to change the EventlogLevel value to 1 so that DNS logs only errors without having to restart the DNS server, follow these steps:  Click Start, click Run, type Cmd in the Open box, and then click OK. At the command prompt, type the following command, where  is the DNS server represented by local computer syntax, IP address, fully qualified domain name (FQDN), or host name (if omitted, the local server is used)

dnscmd  /config /EventlogLevel 2 dnscmd /config /EventlogLevel 1

and then press ENTER.

Note The EventlogLevel switch is case-sensitive.

Windows 2000 error tracking is now enabled. You do not have to restart the server.

Note When you install DNS, DNS writes events to the System Log in Event Viewer until you restart the computer. After you restart the computer, DNS creates the DNS Server log in Event Viewer.

back to the top

Troubleshoot
When you use the Dnscmd.exe tool on the DNS server, you receive the following error message:

DNS Server failed to reset registry property.

Status = 9553 (0x00002551)

This issue may occur if you do not use the correct case for the dnscmd parameters. The parameters used with dnscmd are case-sensitive. To confirm the correct case for the parameter that you want, use the /? switch. For example, to confirm the correct case for parameters used with the Dnscmd.exe tool and the config operation, type the following command at the command line, and then press ENTER:

dnscmd config /?

The following information appears:  USAGE: DnsCmd  /Config [|..AllZones]   Server <Property>: /RpcProtocol /LogLevel /EventlogLevel /NoRecursion /ForwardDelegations /ForwardingTimeout /IsSlave /SecureResponses /RecursionRetry /RecursionTimeout /MaxCacheTtl /MaxNegativeCacheTtl /RoundRobin /LocalNetPriority /AddressAnswerLimit /BindSecondaries /WriteAuthorityNs /NameCheckFlag /StrictFileParsing /UpdateOptions /DisableAutoReverseZones /SendPort /NoTcp /XfrConnectTimeout /DsPollingInterval /DsTombstoneInterval /ScavengingInterval /DefaultAgingState /DefaultNoRefreshInterval /DefaultRefreshInterval /DisableNSRecordsAutoCreation Zone <Property>: /SecureSecondaries /AllowUpdate /Aging /RefreshInterval <Value> /NoRefreshInterval <Value> /AllowNSRecordsAutoCreation <IP List> <Value>: New property value. Use 0x prefix to indicate hex value. Note some server and zone DWORD properties must be reset as       part of a more complex operation. Use zone &quot;..AllZones&quot; to apply operation to all zones. See dnscmd help for more information. Command completed successfully. back to the top

<div class="references_section">