Some computer not updating their computer policy

[Ambient]

It looks like there are a load of errors in the FRSDiag, as can be expected. I arent sure how to copy the results out of it?

 

Just for the sake of it, i'm going to do a re-boot of all 3 of our AD server over lunch, in hope of it fixing the problem...which i realsie is unlikley.

Edited June 10, 2010 by aaronjwilkinson

[Ambient]

------------------------------------------------------------

FRSDiag v1.7 on 10/06/2010 12:20:59

.\COOPER3K on 2010-06-10 at 12.20.59

------------------------------------------------------------

 

 

Detecting this machine's domain role ... Domain Controller (PDC)

Processing File Replication Service Event Log... 96 items.............Done!

Processing Application Event Log... 1000 items.............Done!

Processing System Event Log... 1000 items.............Done!

Processing Directory Service Event Log... 1000 items.............Done!

Processing DNS Server Event Log... 1000 items.............Done!

 

Processing ntfrsutl Version....Done!

Processing ntfrsutl ds......Done!

Processing ntfrsutl sets......(Creating connstat...Done!)...Done!

Processing ntfrsutl configtable.....(Dumping SYSVOL........Done)...Done!

Processing ntfrsutl inlog....Done!

Processing ntfrsutl outlog....Done!

Processing ntfrsutl stage....Done!

 

Processing NTFRS Debug Logs ...

NtFrs_0001.log(03/06/2010 00:25:06) ... Done

NtFrs_0002.log(06/06/2010 10:06:35) ... Done

NtFrs_0003.log(06/06/2010 12:15:50) ... Done

NtFrs_0004.log(10/06/2010 08:10:26) ... Done

NtFrs_0005.log(10/06/2010 12:20:27) ... Done ... Done with all logs!

 

Processing Services and Shares check...Done!

Processing Registry Dump of NtFrs related Keys ...Done!

Processing repadmin /showreps....Done!

Processing repadmin /showconn......Done!

 

All Done!

Please wait, generating .CAB file ..... Done!

 

 

 

------------------------------------------------------------

FRSDiag v1.7 on 10/06/2010 12:20:59

.\COOPER3K on 2010-06-10 at 12.20.59

------------------------------------------------------------

 

Checking for errors/warnings in FRS Event Log ....

NtFrs 09/06/2010 17:25:09 Warning 13508 The File Replication Service is having trouble enabling replication from COOPERDATA to COOPER3K for c:\windows\sysvol\domain using the DNS name cooperdata.cooper.intranet. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name cooperdata.cooper.intranet from this computer. [2] FRS is not running on cooperdata.cooper.intranet. [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.

NtFrs 08/06/2010 14:37:52 Warning 13508 The File Replication Service is having trouble enabling replication from COOPERDATA to COOPER3K for c:\windows\sysvol\domain using the DNS name cooperdata.cooper.intranet. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name cooperdata.cooper.intranet from this computer. [2] FRS is not running on cooperdata.cooper.intranet. [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.

NtFrs 07/06/2010 13:38:20 Warning 13508 The File Replication Service is having trouble enabling replication from COOPERDATA to COOPER3K for c:\windows\sysvol\domain using the DNS name cooperdata.cooper.intranet. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name cooperdata.cooper.intranet from this computer. [2] FRS is not running on cooperdata.cooper.intranet. [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.

WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!

 

......... failed 1

Checking for errors in Directory Service Event Log .... passed

Checking for minimum FRS version requirement ... passed

Checking for errors/warnings in ntfrsutl ds ... passed

Checking for Replica Set configuration triggers... passed

Checking for suspicious file Backlog size...

ERROR : File Backlog TO server "COOPER\COOPERDATA$" is : 13330 :: Unless this is due to your schedule, this is a problem!

failed with 1 error(s) and 0 warning(s)

 

Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed

Checking for suspicious inlog entries ... passed

Checking for suspicious outlog entries ...

WARNING: 26.98% (17 out of 63) of your outlog contains Security ACL events

......... passed (with 1 warning(s))

Checking for appropriate staging area size ... passed

Checking for errors in debug logs ...

ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : :SR: Cmd 0407f078, CxtG 6a31f30a, WS ERROR_ACCESS_DENIED, To cooperdata.cooper.intranet Len: (376) [sndFail - Send Penalty]

ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : :SR: Cmd 00fcb780, CxtG 852c07d9, WS ERROR_ACCESS_DENIED, To cooperdata.cooper.intranet Len: (376) [sndFail - rpc call]

ERROR on NtFrs_0002.log : "ERROR_ACCESS_DENIED" : :SR: Cmd 00fcb780, CxtG 852c07d9, WS ERROR_ACCESS_DENIED, To cooperdata.cooper.intranet Len: (376) [sndFail - Send Penalty]

ERROR on NtFrs_0005.log : "ERROR_RETRY" : :SR: Cmd 01114d38, CxtG 6a31f30a, WS ERROR_RETRY, To cooperdata.cooper.intranet Len: (376) [sndFail - Send Penalty]

ERROR on NtFrs_0005.log : "ERROR_RETRY" : :SR: Cmd 01114648, CxtG 6a31f30a, WS ERROR_RETRY, To cooperdata.cooper.intranet Len: (376) [sndFail - rpc call]

ERROR on NtFrs_0005.log : "ERROR_RETRY" : :SR: Cmd 01114648, CxtG 6a31f30a, WS ERROR_RETRY, To cooperdata.cooper.intranet Len: (376) [sndFail - Send Penalty]

 

Found 4 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above

Found 11847 ERROR_RETRY error(s)! Latest ones (up to 3) listed above

 

......... failed with 11851 error entries

Checking NtFrs Service (and dependent services) state...passed

Checking NtFrs related Registry Keys for possible problems...passed

Checking Repadmin Showreps for errors...passed

 

 

Final Result = failed with 11853 error(s)

[Ambient]

I've checked the FRS on Cooperdata...and its "started", so it looks like that isnt the issue here.

[Ambient]

From the information given in the FRdiag, its looking to me like the DC "Cooperdata" could be the problem. I could be wrong here though. Could demoting this server, and then promoting it again be a possible solution?

[ajs]

I've read a few online support forums where people have ended up demoting and promoting a DC to fix this sort of issue but there's no guarantee it'll work and I guess you'll never get to the real cause of the problem.

 

Presumably the FRS on COOPER3K is running?

[Ambient]

Yeah, its running on Cooper3k. I'd rather try my best (with help from others) to fix the problem first, but i guess demoting it is my final solution.

[danrhodes]

Searching the net it looks like a demote and re premote may be your only option Aaron.

 

D

[Ambient]

Searching the net it looks like a demote and re premote may be your only option Aaron.

 

D

 

Do you think the issue is with Cooperdata rather then Cooper3k like i do then? I wont hold you to it if i do the demote and it solves nothing though

[danrhodes]

Have you tried restarting CooperData?

 

Given the posts I would think that a demote and promote may be the best option at this time, the trouble you have now is that all your fsmo roles are on the server and will need transfering before you do anything.

 

D

Edited June 10, 2010 by danrhodes

[Ambient]

Oh, i meant demote Cooperdata...which has no roles...it's just part of Active Directory. Cooper3k is the one with all the roles on it.

 

From the logs, im reading it that Cooperdata is the server with the problem...but as i say, i could be very wrong about this.

[danrhodes]

If cooperdata is not a DC then you wont be able to demote if its just a member server as it will never have been promoted to DC status. Try restarting your data server.

[Ambient]

Cooperdata is an Active Directory server (one of 3). We have Cooper3k, Cooperdata and CooperMail (exchange 2003 required this to be an Active Directory Server in order to install).

 

Cooper3k is the PDC, with Cooperdata and Coopermail replicating to it (well, until this problem of course)

[danrhodes]

Then a demote and promote may be your best option in this case, as it has no roles it shouldn't take any longer than half hour and a brew!

 

d

[Ambient]

Yeah, my thoughts exactly.

 

If this fails, i think a full network re-build may be required in the summer. In all honesty, its something i've wanted to do since i took over here...as the C: partition on our PDC is stupidly small...and i can't do windows updates (the guy here before me did this). We'll see though, and i'd rather it didnt come to that.

 

Thanks for everyones help and input, i'll report back how i get on.

[danrhodes]

My fingers are crossed!

 

D

[Ambient]

Good news!

 

After a re-boot of all 3 of my DC's....they all now seem to be getting along with each other and taking to one another again. I'm going to monitor them at different stages through the night just to make sure thay havent had anymore falling outs.

 

Thanks for everyone's help. I dont feel out of the woods with this one yet, but i'm in a better situation then i was a number of hours ago.

 

A