sammy_bull
asked on
1058 errors and SYSVOL cannot find path
Hello,
I am seeing the folowing error message on one ofour new DC's I installed
Windows cannot access the file gpt.ini for GPO cn={AAB8D770-A485-4F6A-805 D-1BD0519C A229},cn=p olicies,cn =system,DC =domain,DC =local. The file must be present at the location <\\domain.local\SysVol\dom ain.local\ Policies\{ AAB8D770-A 485-4F6A-8 05D-1BD051 9CA229}\gp t.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.
What permissions do I need to verify?
Thanks
I am seeing the folowing error message on one ofour new DC's I installed
Windows cannot access the file gpt.ini for GPO cn={AAB8D770-A485-4F6A-805
What permissions do I need to verify?
Thanks
ASKER
I went directly on the DC and browsed to that GUID and I see it. but for some reason when I try to run the policy from a server that it specifically is for I receive the above error message.
ASKER
I rant the gpotool and found errors. So what I did is the following
I went into sites and services and made sure to replicate between the 2 dc's. I still see errors when I run the gpotool. When I do a compare between the 2 sysvol's they are not identical. In the gpotool it does state that there aree mismatch's.
Cna I just do a copy from the dc that I know has the correct guid's and over to the other. Would this fix the problem?
I went into sites and services and made sure to replicate between the 2 dc's. I still see errors when I run the gpotool. When I do a compare between the 2 sysvol's they are not identical. In the gpotool it does state that there aree mismatch's.
Cna I just do a copy from the dc that I know has the correct guid's and over to the other. Would this fix the problem?
I would try the copy. However this may be a permission issue. What permission does Everyone have to that folder? Also has there been any changes to the DC...new or replaced HW?
Not sure if this will help but MS does have a KB on that error:
http://support.microsoft.com/kb/314494
Brian
Not sure if this will help but MS does have a KB on that error:
http://support.microsoft.com/kb/314494
Brian
ASKER
On both servers the share permission for Everyone is Read.
I will take a look at the KB
I will take a look at the KB
ASKER
the article applies to windows xp station.
I am having an issue between 2 dc's.
I am having an issue between 2 dc's.
ASKER
after running a dcdiag /v /e /c
I see error's as follows
dc2 failed test frsevent
which says that it will affect group policies.
I see error's as follows
dc2 failed test frsevent
which says that it will affect group policies.
What other errors do you have in FRS? It seems you might have a replication problem between the two DCs. Can you post a ipconfig /all for both DCs?
ASKER
Everything looks good how about the Event Logs?
ASKER
Here is the error I get under file replication service event log
The File Replication Service is having trouble enabling replication from C1 toDC2 for c:\windows\sysvol\domain using the DNS name dc1.Domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc1.Domain.local from this computer.
[2] FRS is not running on dc1.domain.local.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This is causing the problem.
The File Replication Service is having trouble enabling replication from C1 toDC2 for c:\windows\sysvol\domain using the DNS name dc1.Domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc1.Domain.local from this computer.
[2] FRS is not running on dc1.domain.local.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This is causing the problem.
Can you ping dc1.Domain.local? Make sure that the A record matches the IP address of the server.
ASKER
I can ping and the name resolves correctly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Brian