File replication services
- Hello...I have just built a small Windows 2003 server environment with 2 domain controllers. I notice there are hardly any updates in the File Replciation service log. I know when I add scripts to the SYSVOL shared folder they are being replicated over to other DC. I just thought when that occured there would be some sort of logging. I ran the frsdiag.exe tool and here are the results. Just wondering if I should have any concern over the 2 failures. I know they are logs and they probably can't be accessed for this test. Like I said my concern is I thought there should be more logging.
------------------------------------------------------------
FRSDiag v1.7 on 12/1/2009 11:01:44 AM
.\SBUSADCP01 on 2009-12-01 at 11.01.44 AM
------------------------------------------------------------
Detecting this machine's domain role ... Domain Controller (PDC)
Processing File Replication Service Event Log... 17 items...Done!
Processing Application Event Log... 71 items.............Done!
Processing System Event Log... 674 items.............Done!
Processing Directory Service Event Log... 167 items.............Done!
Processing DNS Server Event Log... 30 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(11/9/2009 3:39:26 PM) ... Done
NtFrs_0002.log(11/16/2009 11:29:07 AM) ... Done
NtFrs_0003.log(11/21/2009 9:21:16 AM) ... Done
NtFrs_0004.log(11/27/2009 8:16:27 PM) ... Done
NtFrs_0005.log(12/1/2009 11:01:28 AM) ... 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 12/1/2009 11:01:44 AM
.\SBUSADCP01 on 2009-12-01 at 11.01.44 AM
------------------------------------------------------------
Checking for errors/warnings in FRS Event Log .... passed
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... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <SndCsMain: 2856: 877: S0: 15:09:43> :SR: Cmd 01a8f428, CxtG 645e0e76, WS ERROR_ACCESS_DENIED, To sbusadcp02.domain.local Len: (380) [SndFail - rpc call]
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <SndCsMain: 2856: 904: S0: 15:09:43> :SR: Cmd 01a8f428, CxtG 645e0e76, WS ERROR_ACCESS_DENIED, To sbusadcp02.domain.local Len: (380) [SndFail - Send Penalty]
Found 2 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
......... failed with 2 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 2 error(s)
ZT
Risposte
Hi,
As fa as the Event Logs go, you will not see the detaileed information. The events will only inform you about the issues like Journal Wrap, Journal Size etc. The Warning and Error Events will include Events 13508, 13565 etc.
If you want to get the detailed information then you can use FRS tools like Frsdiag, Sonnar, Ultrasound etc.
But i personally believe that you would not require such details until you get into some serious FRS issue and we exhaust all the available resources. Only then we would go for diagnostic loggings and these in-depth tools.
As of now, we are good to go.
Thanks,
Nitin- Contrassegnato come rispostaBruce-LiuModeratorelunedì 7 dicembre 2009 9.39
Tutte le risposte
- Hi,
File Replication Service is basically responsible for monitoring the System Volume Information (NTFS Journal) every 15 sec and Replicating the changes on to other Domain Controllers having Sysvol Shares. The Replication is done by writing the changes into the Inbound.log and Outbound.log. Domain Controller initiating changes would always send a Change Notification to the Partners, since Replication by default is a PULL Porcess, partners would detect the change and Pull the changes.
In order to get a detailed view on the Engine you can visit following link --
http://technet.microsoft.com/en-us/library/cc962200.aspx
In your scenerio, you can check the 'NtFrs_0005.log' file which would contain the latest logs of the Replication.
Also you can check the Events under File Replication Service in Event Viewer and you should see Event 13516 which signifies that File Replication is working fine.
If you have any other Warning or Error Events, please post them here.
Thanks,
Nitin - Nitin,
Thank you for the reply. Like I said everything seems to be replicating I was just curious why there weren't more informationl messages in the Event logs. I just checked and the last entry was on 11/16/2009:
Event: 13516
The File Replication Service is no longer preventing the computer SBUSADCP01 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I guess everything is good to go.
ZT Hi,
As fa as the Event Logs go, you will not see the detaileed information. The events will only inform you about the issues like Journal Wrap, Journal Size etc. The Warning and Error Events will include Events 13508, 13565 etc.
If you want to get the detailed information then you can use FRS tools like Frsdiag, Sonnar, Ultrasound etc.
But i personally believe that you would not require such details until you get into some serious FRS issue and we exhaust all the available resources. Only then we would go for diagnostic loggings and these in-depth tools.
As of now, we are good to go.
Thanks,
Nitin- Contrassegnato come rispostaBruce-LiuModeratorelunedì 7 dicembre 2009 9.39
