Microsoft KB Archive/913463

= Software deployment policies do not work on some Windows Server 2003-based domain controllers =

Article ID: 913463

Article Last Modified on 10/11/2007

-

APPLIES TO

 Microsoft Windows Server 2003 SP1, when used with:  Microsoft Windows Server 2003, Standard Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition

 Microsoft Windows Server 2003, Standard x64 Edition

 Microsoft Windows Server 2003, Enterprise x64 Edition</li></ul>

 Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems</li></ul> </li></ul>

-

<div class="notice_section">

<div class="symptoms_section">

SYMPTOMS
Consider the following scenario. You are deploying software to a Microsoft Windows Server 2003-based domain controller by using software deployment policies. The software is never deployed. Additionally, the following events appear in the Userenv log when you start the domain controller:

Event 1030 Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1030

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.

Event 1097 Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1097

Description: Windows cannot find the machine account. The Local Security Authority cannot be contacted.

These events indicate that the computer did not query for the list of Group Policy objects. That is, a foreground update did not occur. Because software deployment policies require a foreground update, the software is not installed.

In this scenario, later background updates of Group Policy succeed.

You may also experience the problem even though you are not using software deployment policies.

<div class="cause_section">

CAUSE
This problem occurs because of an issue in the Userenv.dll file.

<div class="resolution_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

Prerequisites
You must have Windows Server 2003 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement
You must restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

<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 2.

<div class="moreinformation_section">

MORE INFORMATION
You also see the following in the Userenv.log file and in the Netlogon.log file.

Userenv.log file
<pre class="fixed_text">USERENV(1c4.704) 14:28:04:390 ProcessGPOs: Calling GetGPOInfo for normal policy mode USERENV(1c4.704) 14:28:04:390 GetGPOInfo: ******************************** USERENV(1c4.704) 14:28:04:390 GetGPOInfo: Entering... USERENV(1c4.704) 14:28:04:390 GetMachineToken: AcceptSecurityContext failed with 0x80090304 USERENV(1c4.704) 14:28:04:390 GetGPOInfo: Failed to get the machine token with  -2146893052 USERENV(1c4.704) 14:28:04:390 GetGPOInfo: Leaving with 0 USERENV(1c4.704) 14:28:04:390 GetGPOInfo: ******************************** USERENV(1c4.704) 14:28:04:390 ProcessGPOs: GetGPOInfo failed. USERENV(1c4.704) 14:28:04:390 ProcessGPOs: No WMI logging done in this policy cycle. USERENV(1c4.704) 14:28:04:406 ProcessGPOs: Processing failed with error -2146893052.

Netlogon.log file
<pre class="fixed_text">01/13 14:28:04 [MISC] DsGetDcName function called: Dom:<downlevel (NetBIOS) domain name> Acct:(null) Flags: DS RET_DNS 01/13 14:28:04 [MAILSLOT] Received ping from <DC name> <primary DNS suffix>. (null) on <Local> 01/13 14:28:04 [MAILSLOT] Returning paused to '<DC name>' since: DS paused 01/13 14:28:04 [MAILSLOT] Ping response 'Sam Pause Response Ex' (null) to \\<DC name> Site: Default-First-Site-Name on <Local> 01/13 14:28:04 [CRITICAL] NetpDcHandlePingResponse: <primary DNS suffix>.: Netlogon is paused on the server. 0x14 01/13 14:28:04 [MISC] NetpDcGetName: <primary DNS suffix>. using cached information 01/13 14:28:04 [MISC] DsGetDcName function returns 0: Dom:<downlevel (NetBIOS) domain name> Acct:(null) Flags: DS RET_DNS 01/13 14:28:04 [SITE] DsrGetSiteName: Returning site name 'Default-First-Site-Name' from local cache. 01/13 14:28:04 [LOGON] SamLogon: Generic logon of <DNS domain name>\(null) from (null) Package:Kerberos Entered 01/13 14:28:04 [LOGON] SamLogon: Generic logon of <DNS domain name>\(null) from (null) Package:Kerberos Returns 0xC00002F5 For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

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

Additional query words: Content Maintenance 50982

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB913463

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.