What does this error message mean ID #1054 Userenv
Posted on 2008-06-17
Here is the error message. I can post more later:
Group policy is not enabled. How do i make sure that it is disabled?
Product: Windows Operating System
Symbolic Name: EVENT_FAILED_DSNAME
Message: Windows cannot obtain the domain controller name for your computer network. (%1). Group Policy processing aborted.
A network connectivity or configuration problem exists. Group Policy settings cannot be applied until the problem is fixed.
To troubleshoot the network connectivity or configuration problem, try one or all of the following:
In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
At the command prompt, type netdiag, and note any errors. Those errors usually have to be resolved before Group Policy processing can continue.
At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again.
To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain.
Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in.
Check to see whether other computers on your network are having the same problem.
If this computer is a part of a cross-forest domain, verify that the forest for the user account is currently available and can be contacted by the computer on which the Group Policy processing failed.
If none of the above actions identified the problem, see the 'Troubleshooting Group Policy in Windows Server 2003' white paper at the Microsoft Web site.
Related Knowledge Base articles
You can find additional information on this topic in the following Microsoft Knowledge Base articles:
" Event ID 1054 Is Logged in the Application Event Log
The following event may be logged in the Application event log: Event ID: 1054 Source: Userenv Type: Error Description: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or...
" Cannot connect to domain controller and cannot apply Group Policy with Gigabit Ethernet devices
Windows XP-based systems that use Gigabit Ethernet devices may not be able to log on to an Active Directory domain, which aborts the Group Policy download process. When this occurs, a series of events are written to the event log. For example:
" XADM: Error Message Received When You Start Exchange System Attendant
When you start the Microsoft Exchange System Attendant service, you may receive the following error message: Could not start the Microsoft Exchange System Attendant service on the local computer. The service did not return an error. This could be...
" Event ID 1054 is logged in the application event log
Describes a problem with Windows XP that receives an Event ID 1054 event message in an application event log. Provides a workaround.
" Group Policy may not install the PolicyMaker Software Update client on a Windows XP Service Pack 2-based computer, and event ID 5719 and event ID 1054 are logged
Describes a problem in which you cannot use Group Policy to install the PolicyMaker Software Update client on a workstation that has Microsoft Windows XP Service Pack 2 (SP2) installed. A resolution is provided.
" Group Policy settings are not applied when you log on to a server by using an account from an MIT Kerberos realm
If you successfully log on to a Microsoft Windows Server 2003-based computer, Group Policy settings from a Microsoft Windows 2000 domain controller are not applied as expected. Additionally, you receive the following event in your Application Log:
" Group Policy application fails on a computer that is running Windows 2000, Windows XP Service Pack 1, or Windows XP Service Pack 2
Fixes a problem that occurs when you try to apply Group Policy or join the Active Directory directory service when you start your computer. After you apply this hotfix, you must add the GpNetworkStartTimeoutPolicyValue registry entry.