Article ID: 832215 - View products that this article applies to.
Every time that you restart your Microsoft Windows Server 2003-based domain controller, you may receive the following two error events in the application log in Event Viewer.
Event message 1
Event Source: Userenv
Event Source: Userenv
Additionally, the following information appears in the Netlogon.log file:
USERENV(198.4fc) 14:47:41:140 GetMachineToken: AcceptSecurityContext failed with 0x80090304 USERENV(198.4fc) 14:47:41:140 GetGPOInfo: Failed to get the machine token with -2146893052 USERENV(198.4fc) 14:47:41:140 GetGPOInfo: Leaving with 0 USERENV(198.4fc) 14:47:41:140 GetGPOInfo: ******************************** USERENV(198.4fc) 14:47:41:140 ProcessGPOs: GetGPOInfo failed. USERENV(198.4fc) 14:47:41:140 ProcessGPOs: No WMI logging done in this policy cycle. USERENV(198.4fc) 14:47:41:140 ProcessGPOs: Processing failed with error -2146893052.
07/09 13:37:04 [CRITICAL] NetpDcHandlePingResponse: corp.example.com.: Netlogon is paused on the server. 0x14 07/09 13:37:04 [MISC] NetpDcGetName: corp.example.com. using cached information 07/09 13:37:04 [MISC] DsGetDcName function returns 0: Dom:RTMS_PDC Acct:(null) Flags: DS NETBIOS RET_DNS 07/09 13:37:05 [SITE] DsrGetSiteName: Returning site name 'Default-First-Site-Name' from local cache. 07/09 13:37:05 [LOGON] SamLogon: Generic logon of CORP.EXAMPLE.COM\(null) from (null) Package:Kerberos Entered 07/09 13:37:05 [LOGON] SamLogon: Generic logon of CORP.EXAMPLE.COM\(null) from (null) Package:Kerberos Returns 0xC00002F5
This issue may occur if one or more of the following conditions are true:
Note These netlogon ping requests may also originate from the local computer.
In this scenario, domain controller locator requests are unsuccessful. Therefore, the program or service that sends the request cannot locate a domain controller. Typically, this error only occurs while the domain controller starts. The error stops when the services are available. When the Net Logon service resumes from the paused state, other programs and services can again contact the domain controller.
To work around this issue, if you only have one domain controller, add one or more additional domain controllers to your domain. Make sure that the Net Logon service on the domain controllers is configured as Automatic and is started. To do this, follow these steps:
Netlogonhas a dependency on LanmanServer in the following registry subkey:
If the "Turn off background refresh of Group Policy" setting is enabled, the following registry value will exist on the local computer:
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableBkGndGroupPolicyThis policy prevents Group Policy from being applied while users are logged on. If this policy is enabled, policy refresh occurs only when no users are logged on to the computer.
You can enable NETLOGON and USERENV logging to further troubleshoot this issue. Use the nltest /dbflag command for best results. For more information about how to enable USERENV logging, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/221833/ )How to enable user environment debug logging in retail builds of Windows