If that doesnot work check this
http://support.microsoft.c
Sunray
Main Topics
Browse All TopicsMy 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-945
I have tried doing the MUP fix with no luck.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
If that doesnot work check this
http://support.microsoft.c
Sunray
also check this article, from a site which i find invaluable
http://www.eventid.net/dis
chris
The link that I had given solved the same issue .Not sure it is not working for u
http://www-level3.experts-
Hmm let me try some more
Sunray
also check this article too.
http://www.ntmag.com/Forum
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-945
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 127.0.0.1 to its real IP address. Then rebooted it again. Then I changed the DNS network connection settings on the "problem" DC from 127.0.0.1 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.
http://support.microsoft.c
Business Accounts
Answer for Membership
by: JonybrvPosted on 2003-10-26 at 14:03:38ID: 9623811
Have you tried the following:
/tip5800/r h5874.htm
http://www.jsiinc.com/SUBL
Thats listed for XP, check if it helps you.