Microsoft KB Archive/842804

= A Windows Server 2003-based computer may stop responding when it is resumed from standby and events 1030 and 1058 are logged in the application log of a domain controller =

Article ID: 842804

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



SYMPTOMS
When you resume a Windows Server 2003-based computer from standby, the computer may stop responding. You may also see the &quot;Applying Personal Settings&quot; message box for up to an hour before the desktop appears.

Typically, when you resume a Windows Server 2003-based computer from standby, the computer is locked. Therefore, you must log on to the computer before you can access the desktop. However, when this problem occurs, the computer is not locked, and the Windows Server 2003 logon screen does not appear.

Additionally, the following event messages may be logged in the application event log on the domain controller after you restart the Windows Server 2003-based computer:

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1058

Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC= ,DC=. The file must be present at the location <\\ \sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted. For more information, see Help and Support Center at http://support.microsoft.com.

or

Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC= ,DC=. The file must be present at the location <\\ \sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ).

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1030

Description: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine. For more information, see Help and Support Center at http://support.microsoft.com.

When you turn on user environment (Userenv) logging, domain Distributed File System (DFS) services may not work after the computer resumes from standby. Additionally, you may receive messages that resemble the following messages in the %SystemRoot%\Debug\UserMode\Userenv.log file.

Note For information about how to turn on Userenv logging, see the Microsoft Knowledge Base article that is referenced in the &quot;References&quot; section.

USERENV(1d8.a84) 21:52:58:718 EvaluateDeferredGPOs: Searching for GPOs in cn=policies,cn=system,DC= ,DC=local

USERENV(1d8.a84) 21:52:58:718 ProcessGPO: Searching 

USERENV(1d8.a84) 21:52:58:718 ProcessGPO: Machine has access to this GPO.

USERENV(1d8.a84) 21:52:58:718 ProcessGPO: GPO passes the filter check.

USERENV(1d8.a84) 21:52:58:718 ProcessGPO: Found functionality version of: 2

USERENV(1d8.a84) 21:52:58:718 ProcessGPO: Found file system path of: <\\ .local\sysvol\ .local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}>

USERENV(1d8.a84) 21:52:58:734 ProcessGPO: Couldn't find the group policy template file <\\ .local\sysvol\ .local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>, error = 0x5.



CAUSE
This problem may occur if the Winlogon process tries to process group policies before other components are running. The service pack that this article describes adds logic to improve the default behavior of the Winlogon process and of the workstation services.

However, there are several other scenarios that may cause this problem. Make sure that the following components are started and that they are configured correctly before you apply this service pack:
 * Netlogon and DFS services are started.
 * Domain controllers have the read and apply rights to the Domain Controllers Policy.
 * NTFS file system permissions and share permissions are set correctly on the Sysvol share.
 * DNS entries are correct for the domain controllers.



RESOLUTION
To resolve this problem, please see the &quot;Service pack information&quot; section that immediately follows. To temporarily work around this problem, please see the &quot;Workaround&quot; section later in this &quot;Resolution&quot; section.

Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Note After you have installed this service pack, please return to this article to complete the procedure that is outlined in the &quot;Registry information&quot; section that immediately follows.

Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista

Note Follow these steps in Windows Server 2003.

After you have applied this service pack, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. In Registry Editor, locate the following registry subkey:

 If the WaitForNetwork entry is missing, you must add the entry. To do this, follow these steps:  Right-click the Winlogon subkey, click New, and then click Dword Value. In the Value name box, type WaitForNetwork . </li> Right-click WaitForNetwork, and then click Modify.</li> In the Edit DWORD Value dialog box, in the Value Data box, type 1, and then click OK.</li> Close Registry Editor.</li></ol>

Workaround
To temporarily work around this issue, you can run the Dfsutil.exe file that is included in Windows Server 2003 Support Tools. You can install Windows Server 2003 Support Tools in two ways. You can run \\Support\Tolls\Suptools.msi from the Windows Server 2003 CD-ROM. Or, you can extract the support tools directly from the \\Support\Tools\Support.cab file. To run the Dfsutil.exe file, follow these steps:
 * 1) Click Start, click Run, type cmd, and then click OK.
 * 2) At the command prompt, type dfsutil /PurgeMupCache, and then press ENTER.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Windows Server 2003 Service Pack 1.

<div class="references_section">