jbits1212
asked on
Event ID 1001 scecli
I have a domain with 2 sites across a netgear VPN.everything works fine normally
I recently added a second domain controller at Site B.
since then the ping time between the sites gos upto 4000ms as per the usual 65-80ms,this occurs every 5 minutes or so and is causing disruption.
i had lots of errors in my event logs most of which have gone away after running updates on all servers and restarting them.but i am left with this one
event ID 1001
Security policy cannot be propagated. Cannot access the template. Error code = -536870909.
\\RegencyLodge.local\sysvo
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
i have checked that the above file exists and it does but it is 0KB in size.
i have looked here
http://www.eventid.net/display.asp?eventid=1001&eventno=135&source=SceCli&phase=1
but dont know where to start really
Any help appreciated
thanks
I recently added a second domain controller at Site B.
since then the ping time between the sites gos upto 4000ms as per the usual 65-80ms,this occurs every 5 minutes or so and is causing disruption.
i had lots of errors in my event logs most of which have gone away after running updates on all servers and restarting them.but i am left with this one
event ID 1001
Security policy cannot be propagated. Cannot access the template. Error code = -536870909.
\\RegencyLodge.local\sysvo
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
i have checked that the above file exists and it does but it is 0KB in size.
i have looked here
http://www.eventid.net/display.asp?eventid=1001&eventno=135&source=SceCli&phase=1
but dont know where to start really
Any help appreciated
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the replies,
I have managed to get rid of that error in the log
I do have the setup as outlined above within sites and services and different subnets
to get rid of the error
i noticed that the file below
\\RegencyLodge.local\sysvo
was empty but there was a GptTmpl.TMP file there as well
so i copied the contents of the tmp to the inf and the error went away and i got a message in the event log saying GPolicy had beed applied no problems.
I think that when i added the new domain controller to site b there was some break in the VPN connection during replication and somehow corrupted that .inf file.
I have managed to get rid of that error in the log
I do have the setup as outlined above within sites and services and different subnets
to get rid of the error
i noticed that the file below
\\RegencyLodge.local\sysvo
was empty but there was a GptTmpl.TMP file there as well
so i copied the contents of the tmp to the inf and the error went away and i got a message in the event log saying GPolicy had beed applied no problems.
I think that when i added the new domain controller to site b there was some break in the VPN connection during replication and somehow corrupted that .inf file.
Glad you got it resolved. Kudos for getting your Sites set up before you deployed remote DCs. You would be amazed at how many folks don't.
ASKER
you make the mistake once and you dont do it again
agree with DrUltima as his/her questions are essential.
> since then the ping time between the sites gos upto 4000ms as per the usual 65-80ms
additionally, where is the PING time from? between the two DCs, or any two computers between the sites??
> since then the ping time between the sites gos upto 4000ms as per the usual 65-80ms
additionally, where is the PING time from? between the two DCs, or any two computers between the sites??
bbao,
It's "he". :) I think that the Author resolved the issue himself.
Justin
It's "he". :) I think that the Author resolved the issue himself.
Justin
ASKER
I have awarding points to DrUltima as he did make a valid point about the subnets and site definitions and that information might prove usefull to someone else.
But please read my fix as it did stop the error for me
But please read my fix as it did stop the error for me
maybe this link is helpfull
http://support.microsoft.com/kb/258296