Event ID: 1058 on Windows 2003 Server

JIm Peck
JIm Peck used Ask the Experts™
My PDC is running 2000.

On the 2003 server machine i have this error?

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

I have tried doing the MUP fix with no luck.

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you tried the following:


Thats listed for XP, check if it helps you.

Top Expert 2004

If that doesnot work check this




I tried both of those and I still get the errors..
Bootstrap 4: Exploring New Features

Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.

also check this article, from a site which i find invaluable


Top Expert 2004

The link that I had given solved the same issue .Not sure it is not working for u


Hmm let me try some more

sorry sunray didnt mean to step on your toes mate


Still getting it... hmm it seems that most of those sites are targeted around WinXP computers.

I am in a Windows 2003 level domain with 2Domain Controllers running DNS, DHCP, WINS. One DC started receiving Event Id: 1058

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

followed by a Event Id:1030
This occured for about ten days. I finally got concerned and looked at the articles referring to XP SMB signing but decided not to apply XP fixes to a 2003 DC.

I'm happy to say  the errors have gone away, but I'm not sure what I did had any effect on it. Here is what I did. I rebooted the DC which was not receiving the errors. Then changed its network connection DNS setting from to its real IP address. Then rebooted it again. Then I changed the DNS network connection settings on the "problem" DC from to its real address and rebooted it. I've been error free for 2 hours.
This seems high unlikely the DNS settings were to blame, but maybe the rebooting helped. Just a side note, the problem DC is running the PDC emulator FSMO.

It seems microsoft doesn't address this error.
Here is the answer for me.  Really easy and it worked.  I have been having this problem for months and finally found it with the help of our TAM.

830676 isnt available anymore and I am having the problem.  Does anyone have a copy of 830676 or can someone verify that it was changed to 888943?

The KB I found sais there should be a random domain name in the error and my domain names are corect, not random.


I was experiencing exact same issue after I applied SP1 for server 2003.... The article indicated by astronot above fixed mine.. Thanks a stack.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial