Dns Error 140
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event Message: The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service or reboot the computer. For specific error code, see the Record Data page. Source Event Log Event ID Event Type DNS System 140 Error Explanation: In order for DNS to run, the Remote Procedure Call (RPC) service must be running on the DNS server. User Action: Verify that the Remote Procedure Call (RPC) service has been started: Open Administrative Tools, and double-click Services. If the service has been started, try restarting your computer. If you continue to receive this message, remove and reinstall the RPC Configuration service by using the Services tab network connection in Network and Dial-up Connections in Control Panel. Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful? Yes No Additional feedback? 1500 characters remaining Submit Skip
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an https://msdn.microsoft.com/en-us/library/ms854983.aspx eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 140 Source: DNS Source: DNS Type: Error http://www.eventid.net/display-eventid-140-source-DNS-eventno-4568-phase-1.htm Description:The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service or reboot the computer. The event data is the error code. English: Request a translation of the event description in plain English. Comments: EventID.Net As per Microsoft: "In order for DNS to run, the Remote Procedure Call (RPC) service must be running on the DNS server". See MSW2KDB for more details. x 1 Private comment: Subscribers only. See example of private comment Links: MSW2KDB Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Login here! Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended booksNewsletter Links Follow us on FacebookFiregen Log Analyzers Link to us © Copyright 2001-2016 EventID.Net
Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent https://www.windowsbbs.com/threads/dns-server-problems-keep-having-to-restart-the-dns-service.61307/ Posts More... WindowsBBS Forums > Operating Systems > Windows Server System > This site uses http://www.justanswer.com/computer-networking/4fkv5-dns-snap-in-reports-cannot-contact-dns-server.html cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations. Cookies Registration Notice DNS Server Problems - Keep having to restart the DNS service Discussion in 'Windows Server System' started by dns error markjrees, 2007/01/15. 2007/01/15 markjrees Inactive Thread Starter Joined: 2003/09/02 Messages: 49 Likes Received: 0 Trophy Points: 81 Computer Experience: Experienced For about a week now during the day our office internet connection goes down. When it goes down I have to restart the DNS service on our server which brings the internet back online. Our DNS server has forwarders set-up to send external requests to an external internet based DNS server. We use NAT to share internet dns error 140 access throughout the office. When the connection goes down we can access websites by using IP address. This obviously confirms the problem is DNS based. Whilst restarting the DNS service on our server sorts the problem I do need to find out what's causing it to go down. There are no errors or warning messages in the event log. Any advice welcomed! Chris House MCSE markjrees, #1 2007/01/15 mflynn Inactive Joined: 2002/08/14 Messages: 4,141 Likes Received: 9 Trophy Points: 608 Hey Mark Someting else a required service (for DNS) or something is shutting down therefore DNS. Look closely at the required services for DNS. Additionally and indirectly you may possibly solve this by hard coding just the internet DNS Ip's of your ISP. Even if using DHCP for local LAN IP. This should keep internet up but still does not address the reason DNS goes down. Have you checked the event logs for this? Mike mflynn, #2 Log in or Sign up to hide this advert. 2007/01/15 ReggieB Geek Member Alumni Joined: 2004/05/12 Messages: 2,786 Likes Received: 2 Trophy Points: 608 Location: Worcs. UK Computer Experience: Unabashed deviant What server OS are you using? Setting your ISP's DNS IPs as the secondary DNS via DHCP may help keep the internet connection live - but if you are using 2000 or 2003 server, DNS f
by a Fortune 500 verification firm. Get a Professional Answer Via email, text message, or notification as you wait on our site.Ask follow up questions if you need to. 100% Satisfaction Guarantee Rate the answer you receive. Ask Claws224 Your Own Question Claws224, IEEE Network Engineer Category: Networking Satisfied Customers: 1256 Experience: IEEE, Microsoft 5195814 Type Your Networking Question Here... Claws224 is online now The DNS snap-in reports that it Cannot contact the DNS Server Customer Question The DNS snap-in reports that it "Cannot contact the DNS Server" on two of my 3 DNS/DC/AD servers (all Win2k3 SP2).The Event Log shows Event ID:140 - "The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service or reboot the computer. The event data is the error code."The 3rd server seems fine, however, it cannot replicate due to the RPC errors reported by the other two. One of the two problem servers is the Primary DC and DNS, the other two are backups.I have tried tons of solutions offered by various forums (Google), but came up emty-handed. Looks like I'm going to need your help again, please...G Submitted: 5 years ago. Category:Networking Share this conversation Expert: arsufi replied5 years ago. arsufi : hi,arsufi : what happens when you try to start the RPC dervicearsufi : If it doesn't , have you checked whether all the dependency services are runningCustomer : OK, you need to slow down a bit; I'm not an expert (he left me high and dry...). I cannot start the RPC service; it is greyed out and does not provide the option to start/stop/restart...Customer : What are all the dependency services?arsufi : certain services that is needed for starting a service is called dependency servicesarsufi : have you checked it from the administrator account itselfCustomer : OK, kinda figured that, but which ones are they, so that I can check on my servers...arsufi : can you go to the RPC serviceCustomer : I am only working with the Domain/Enterprise account. Will do; stand by...Customer : OK?arsufi : okCustomer : Ahem.. what next?arsufi : check dependency services are runningCustomer : Ah, ok, I'm catching up... It will take me a few minutes, so will come back shortly with a response.arsufi : koarsufi : okarsufi : can you wait for 15min i shall come backCustomer : Yes, just a quick question - Do I have to start all the dependancy services that are not started? There are quite a lot...Customer : OK, I started a few dependency services that I thought may have relevance, but still no change to the DNS snap-in status (Cannot contact