Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The PrintQueue Container could not be found because the DNS Domain name could not be retrieved. Error: <error code>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of a DNS server?
This error was occurring at boot-up on a Windows Server 2003 domain controller because DNS was not loading quickly enough to service the print spooler and other services. We changed the server's own DNS entry to point to another DNS server in the domain instead of itself, and all the errors went away. The solution is simple: Add the IP address of another DNS server on your domain as a secondary DNS entry in TCPIP. At boot-up, if the primary DNS server (the server booting) cannot respond to requests, it will use the secondary DNS server. Boot-up should process without errors, and once DNS is started, the server will use its own DNS for subsequent DNS queries. This appears to be a known issue with Windows AD domain controllers.
Peter Van Gils
This error occurs on print servers that have moved from a Windows 2000 or 2003 domain, to an NT4.0 domain. If you used to have the "List in the directory" option (Sharing tab of the printer’s properties) enabled, the printer server will look for a DNS server that can provide it with the necessary Active Directory info. You can solve this error by removing and then reinstalling all the printers, or you can just ignore it.
- Error code: 0x547 - For me the problem was cured by removing the “.spl” files (8000+ of them) from "%windir%\system32\spool\printers". Have a look at MSKB ME264662 for more details.
As per Microsoft: "The print spooler could not locate the domain controller or could not bind to the directory service on the domain controller. This might be because DNS cannot resolve the domain controller's IP address, or because the domain controller or directory service is not functioning correctly". See MSW2KDB for more details on this event.
See ME832219 for a workaround.
Error 0x547 (1351 decimal) = "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied."
From a newsgroup post: "This event can occur if you have some published printers on your machine and, for various reasons, can't contact a Domain Controller on your domain. For instance, you may see this if you are disconnected from the network. When your machine is reconnected (or whatever the problem was that prevented your machine from contacting a DC), all pending updates to the Directory will be executed automatically. Therefore, you don't need to do anything special to fix the problem (other than reconnect to the network at your leisure). Sometimes your machine can be connected to the network and you'll still get this event because of domain, network, router, etc., configuration problems. In these instances, you may wonder why a printer isn't getting published and this event (and others like it) can help solve the puzzle.
Error 0x6BA (1722 decimal) = "The RPC server is unavailable." - no info.
Error 0x54B (1355 decimal) = "The specified domain either does not exist or could not be contacted." - Verify that you have connectivity to the domain controller. Verify DNS is functional.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated