2003 server error

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

any ideas this
zenworksbAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
madison perkinsConnect With a Mentor Network AdministratorCommented:
Check the event log for possible messages previously logged by the policy engine that describes the reason for this?
search the forums before posting?
http://www.experts-exchange.com/Operating_Systems/Win2000/Q_21646836.html

bacically your server can read the group policy from active directory.  there are a number of reason and situations that this can occur. on my server i have the following logged in the application log.

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1030
Date:            2/1/2008
Time:            10:16:38 AM
User:            NT AUTHORITY\SYSTEM
Computer:      AD02
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.

which is preceeded by

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1058
Date:            2/1/2008
Time:            10:16:38 AM
User:            NT AUTHORITY\SYSTEM
Computer:      AD02
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=newellcoach,DC=net. The file must be present at the location <\\domain.net\sysvol\domain.net\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. ). Group Policy processing aborted.

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


an i ignored this because i rebooted a dc and one dc couldn't talk to the other during the reboot.  
0
All Courses

From novice to tech pro — start learning today.