13508 file replication service error

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.

Connect and share knowledge within a single location that is structured and easy to search. Basically I am making some changes in regards to the DC's in my network. I have created a writable R2 DC called "DC", it is set up and appears to be working fine with one exception. This error corresponds to Event that I am getting and it states:. FRS will keep retrying. Usually these sorts of issues are related to DNS in some way.

Check that all of your domain controllers are in the domain controllers OU in Active Directory and that the security tab for each domain controller is set to inherit permissions from the parent. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Learn more. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory Domain Services replication is required, you must manually delete the duplicate connection objects by following the steps below:.

The re-addition will trigger a full tree sync for the replica set. The service is set to restart after every reboot. It is recommended that you manually restart the service to prevent loss of data in the staging directory. To manually restart the service, do the following:. This will not affect replication unless this volume hosts database, staging, or replica root paths as well. Sample values are shown below.

You can also change the path to the logs directory by changing the following value at the same location. The tracking records in FRS debug logs will have the filename and event time for the suppressed updates. The tracking records have the date and time followed by :T: as their prefix.

Updates that do not change the content of the file are suppressed to prevent unnecessary replication traffic. Following are common examples of updates that do not change the contents of the file. This can occur because of one of the following reasons. Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.

During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. The skipped files will not replicate to other members of the replica set. A list of all the files skipped can be found at the following location. If a directory is skipped, then all files under the directory are also skipped.

Files are skipped during primary load if FRS is not able to open the file. Check if these files are open. These files will replicate the next time they are modified. Files may not replicate until disk space is made available on this volume. File Replication Service doesn't support this configuration.

Files may not replicate until this conflict is resolved. The output of dir command displays the Volume Serial Number before listing the contents of the folder.

DC2 passed test ObjectsReplicated. DC2 passed test Replications. DC2 passed test RidManager. DC2 passed test Services. A warning event occurred. EventID: 0xD. Event String:. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil. DC2 passed test SystemLog. DC2 passed test VerifyReferences. And finally, here is the result from DC DC3 passed test Connectivity. DC3 failed test Advertising. DC3 passed test FrsEvent.

DC3 passed test SysVolCheck. DC3 passed test KccEvent. DC3 passed test MachineAccount. The network name cannot be found.. DC3 failed test NetLogons. DC3 passed test ObjectsReplicated. DC3 passed test Replications. DC3 passed test RidManager. DC3 passed test Services. DC3 passed test SystemLog. DC3 passed test VerifyReferences. Any idea what would be causing this and what my next steps would be?

Let me know if I can get you any more info. Check for Networking problems! DC3 is showing as a not suitable DC. My Linkedin Profile. My MVP Profile. Yeah, it's because of the sysvol situation. It used to show the same thing on DC2, but I forced it into thinking it was replicating. Event Event Inbound from "DC1. Event two of them actually.

One for DC1 and one for DC2. All seems good now. You should find Netlogon and Sysvol shares over there. Also, use dcdiag and repadmin to make sure that your DCs and AD replication are okay. This posting is provided AS IS with no warranties or guarantees , and confers no rights.

It looks like it's still not working. Sysvol isn't showing up under net share and I'm still getting the netlogon and frsEvent fail in dcdiag. My end goal is to create 3 new domain controllers. Two of them are to replace DC1 and DC2 and a third will be created as a spare. DC3 was put in place to replace DC1. I am wanting DC3 to replace DC1's roles. Once DC4 is in place, it will take over DC2's roles. Is there a way to bypass this error for now and have DC3 take over for DC1?

Will that possibly take care of my issues? It must already be shared and the DC must be advertising and available, or migration at each stage will never complete. What if everything is copied over manually, the reg key is set to 1 for sysvol, and the folders are shared out?

Is that still not advisable to do? I'm out of ideas and I haven't been able to find anything to get the FRS replication resolved. I did notice, however, that when trying to do an authoritative FRS restore, I never see the in the event log on the machine I set to D4. The BurFlags go back to 0, but nothing shows up in the event log after that. Could not detect any upstream partners, this server seems to be Orphaned! You should double check this!

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff microsoft. If so, I don't see that type of message anywhere. FRSDiag v1. Following are some of the reasons you would see this warning. Computer DC2 cannot become a domain controller until this process is complete.

The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. The tracking records in FRS debug logs will have the filename and event time for the suppressed updates. The tracking records have the date and time followed by :T: as their prefix.

Updates that do not change the content of the file are suppressed to prevent unnecessary replication traffic. Following are common examples of updates that do not change the contents of the file. Suppression of updates can be disabled by running regedit. Click on Start, Run and type regedit. Checking for errors in Directory Service Event Log Checking for minimum FRS version requirement Checking for Replica Set configuration triggers Checking for suspicious file Backlog size Checking for suspicious inlog entries Checking for suspicious outlog entries This can occur because of one of the following reasons.

Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. The re-addition will trigger a full tree sync for the replica set.

You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

Type the value name exactly as shown above. I'd resolve any issues first if possible. I don't like to introduce new DCs when the domain isn't healthy. Does that seem like a good plan? I'm sort of an AD noob so I guess I'd appreciate some validation on that.

I'm not sure you'll have another option.