Tuesday, August 26, 2008

Event ID 1030 & 1058: Can't Access the File GPT.INI

For some time, two (only two) of our domain controllers have been receiving the following errors every 5 minutes:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 8/26/2008
Time: 11:24:10 AM
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


and

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 8/26/2008
Time: 11:24:10 AM
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain.com\sysvol\domain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


After many hours of research, I tried each of the below to fix the errors with no success:
  1. Domain.com\Domain Controllers group was added manually on the security of GPT.ini file - removed this as it is not the default setting
  2. Added the Everyone group to the Default Domain Policy->Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights Assignment ---- REMOVED ---- as this did not fix the problem
  3. Removed DNS servers that are no longer running DNS
  4. Added Registry Key HKLM\software\microsoft\windowsnt\currentversion\winlogon\WaitForNetwork DWORD and set it to 1
None of these changes corrected the problem. Finally, after reading the following article: http://support.microsoft.com/kb/840669 (which says it only applies to Windows 2000, Windows XP SP1 and SP2) I added the Registry Key HKLM\software\microsoft\windowsnt\currentversion\winlogon\GpNetworkStartTimeoutPolicyValue set to decimal 60 on each of these servers.

According to the article, "
If the TCP/IP protocol registers with NDIS before the network adaptor driver, for a short time it prompts higher user mode networking components that network connectivity is not available. During this short time, the Group Policy startup script cannot be downloaded." Reading on, "This problem is more likely to occur on fast networks that use 1-gigabit network adaptors or in teaming environments where the network takes several additional cycles to negotiate link speed."

Both of these conditions are true on these servers:
  1. They have teamed network cards
  2. They have gigabit ethernet cards
After setting the Registry key, I rebooted and the errors have not returned.

No comments: