Userenv errors 1058 & 1030 on both Windows 2003 Domain Controllers
Home > IT Answers > Microsoft Windows > Userenv errors 1058 & 1030 on both Window...
ITBird
15 pts.
0
Q:
Userenv errors 1058 & 1030 on both Windows 2003 Domain Controllers
Windows Server 2003, Event ID, Userenv errors, Event ID 1030, Event ID 1058
I'm getting these 2 errors on both my Windows 2003 domain controllers:-

1030: 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.

1058: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=techset,DC=local. The file must be present at the location <\\techset.local\sysvol\techset.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted.

I've been right through Article ID: 887303 and have checked everything. Its only the 2 domain controllers that are affected, all the other computers on the network are fine and are loading group policies without any problems. The Sysvol shares are there on both DC's and permissions are spot on. DNS settings are fine, and everything else in the article checks out ok. The one thing that puzzles me in in error 1058 is when it says Access is denied to gpt.ini because all the permissions are exactly as they should be.

Does anyone have any idea what might be causing these errors to appear? Thanks in advance.
ASKED: Feb 8 2008  4:19 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
The Geek
145 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
***buddy***
go into your control panel > power settings and check to see if there are any standby settings set in power options. from what I have found so far this could be an issue if the system comes out of a standby state. check the following kb from microsoft:

http://support.microsoft.com/kb/842804

***/buddy***

I have had similar problems with these two repeating errors when I restarted both domain controllers at the same time and only one of them was a global catalog server. For some reason, when more than one domain controller exists, the one that isn't the global catalog server tries to authenticate itself and can't. You then start getting these errors in the logs. Try rebooting the server in question and see if the error goes away. I now follow a procedure whereby I reboot the global catalog server--in my case, the Exchange server--first and then reboot the other domain controller. Of course, you could simply make both of the servers function as global catalog servers.

The Geek
Last Answered: Feb 13 2008  1:38 AM GMT by The Geek   145 pts.
Latest Contributors: Buddyfarr   6835 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

ITBird   15 pts.  |   Feb 14 2008  9:49AM GMT

Thanks Buddy and The Geek for your suggestions, but there are no standby settings in power options and both domain controllers are already global catalogue servers. Any more suggestions from anyone?

IT Bird

 
0