DNS Server Fails to Start Due to Unavailable RPC Server Error

This article was previously published under Q171781
This article has been archived. It is offered "as is" and will no longer be updated.

IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information about how to do this, view the "Restoringthe Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"Help topic in Regedt32.exe.
After your Microsoft Windows NT Domain Name Service (DNS) server starts,you may receive one or more of the following event log error messages:
Event ID: 157
Source: DNS
Description: DNS Server is not root authoritative and no cache file specified. A cache file must be specified when the DNS server is not authoritative for the root domain. The cache file must contain NS record(s) for root DNS servers and corresponding A record(s) for the root DNS servers. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones.
Event ID: 7023
Source: Service Control Manager
Description: The Microsoft DNS Server service terminated with the following error: The system cannot find the file specified.
Event ID: 3
Source: DNS
Description: The DNS Server has shutdown.
You may also see your DNS server in the server list of the DNS Manager witha red X on it, indicating that the DNS service is unavailable, and you maysee the following message in the DNS Manager:
The RPC Server is unavailable.
This behavior can occur when the registry key that determines whether yourDNS server initializes from a boot file or from the registry has not beenupdated properly.
WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved. Use Registry Editor at your own risk

For information about how to edit the registry, view the "Changing Keys AndValues" Help topic in Registry Editor (Regedit.exe) or the "Add and DeleteInformation in the Registry" and "Edit Registry Data" Help topics inRegedt32.exe. Note that you should back up the registry before you edit it.

To resolve this issue, follow these steps:
  1. Start Registry Editor (regedt32.exe) and locate the following subkey:
  2. Edit the following value as appropriate:
       Value Name: EnableRegistryBoot   Value Type: REG_DWORD   Data:       1 or 0  (1 for registry boot, 0 for boot file)						
  3. Quit Registry Editor.
This value is set to 1 when the first zone is created, and by default theboot file's information is then migrated into the registry. When resettingthis registry value back to zero, it disables the DNS server from bootingor initializing from the registry. If the DNS Server does not boot from theregistry, then it must initialize from a boot file. A backup boot file canbe found in the following location:

Copy the backup boot file to the %SystemRoot%\System32\Dns folder, and thenrestart the DNS service.
Microsoft has confirmed this to be a problem in Windows NT version 4.0. Weare researching this problem and will post new information here in theMicrosoft Knowledge Base as it becomes available.

Article ID: 171781 - Last Review: 12/04/2015 17:28:26 - Revision: 1.1

Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbnetwork KB171781
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)