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

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
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.
Cause
This problem occurs because of an issue in the Userenv.dll file.
Resolution

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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
File nameFile versionFile sizeDateTimePlatform
Userenv.dll5.2.3790.2688790,01624-Apr-200603:50x86
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Userenv.dll5.2.3790.26881,069,56823-Apr-200613:07x64SP1Not Applicable
Wuserenv.dll5.2.3790.2688790,01623-Apr-200613:07x86SP1WOW
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Userenv.dll5.2.3790.26881,564,67223-Apr-200613:07IA-64SP1Not Applicable
Wuserenv.dll5.2.3790.2688790,01623-Apr-200613:07x86SP1WOW
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
More information
You also see the following in the Userenv.log file and in the Netlogon.log file.

Userenv.log file

USERENV(1c4.704) 14:28:04:390 ProcessGPOs: Calling GetGPOInfo for normal policy modeUSERENV(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 0x80090304USERENV(1c4.704) 14:28:04:390 GetGPOInfo:  Failed to get the machine token with  -2146893052USERENV(1c4.704) 14:28:04:390 GetGPOInfo:  Leaving with 0USERENV(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

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 paused01/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. 0x1401/13 14:28:04 [MISC] NetpDcGetName: <primary DNS suffix>. using cached information01/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 Entered01/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
Content Maintenance 50982
Properties

Article ID: 913463 - Last Review: 01/17/2015 00:30:00 - Revision: 4.0

  • Microsoft Windows Server 2003 Service Pack 1
  • kbnosurvey kbarchive kbautohotfix kbwinserv2003sp2fix kbbug kbfix kbqfe KB913463
Feedback