Select the product you need help with

A “Netlogon event ID 5719” event message is logged when you start a Windows based computer

Article ID: 247922 - View products that this article applies to.

This article was previously published under Q247922

SYMPTOMS

When you start a Windows based server, Event Viewer may record an event that resembles the following:

Netlogon Event ID 5719:
No Windows NT Domain Controller is available for domain <domain_name>.
The following error occurred:
This event is expected and can be ignored when booting with the No Network Hardware Profile.

After the server logs this event at startup, you can log on to the domain normally. The event occurs when you start the computer. This event may repeat frequently if the Windows OS needs to setup communications with other domain controllers. Windows 2000 Server and later domain controllers are highly impacted and may log thousands of 5719s in the system event log.

Additionally, the Windows “Service Control Manager” may report the following condition after repeated NETLOGON 5719 events, if the “System Center Management service” is installed:

Log Name: System
Source: Service Control Manager
Date: <Date> <time>
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <servername>
Description: The System Center Management service entered the stopped state.

This entry may be seen in the netlogon.log file after a reboot if Netlogon Debug Logging is enabled on the computer generating the Netlogon error event: MM/DD HH:MM:SS [INIT] Netlogon.dll has been unloaded (recover from it).

Note To enable Netlogon Debug Logging simply run the nltest.exe command shown in Step 6 of MSKB 109626 and restart the service. Or in this case, reboot the computer to generate the event.

109626 Enabling debug logging for the Net Logon service
http://support.microsoft.com/default.aspx?scid=kb;EN-US;109626

(http://support.microsoft.com/default.aspx?scid=kb;en-us;109626)