Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
DNS Server Fails to Start Due to Unavailable RPC Server Error
Article ID: 171781 - View products that this article applies to.
This article was previously published under Q171781
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the 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
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.
You may also see your DNS server in the server list of the DNS Manager with a red X on it, indicating that the DNS service is unavailable, and you may see the following message in the DNS Manager:
Event ID: 3
Description: The DNS Server has shutdown.
The RPC Server is unavailable.
This behavior can occur when the registry key that determines whether your DNS server initializes from a boot file or from the registry has not been updated properly.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk
For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.
To resolve this issue, follow these steps:
Copy the backup boot file to the %SystemRoot%\System32\Dns folder, and then restart the DNS service.
Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.