Windows 2003 ntfrs replication error

Type the value name exactly as shown above and set the parameter to 1. You may have to wait for 5 min for the replication to take place. To change this registry parameter, run regedit. Click down the key path:. Office Office Exchange Server.

Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. It should be sdc. Also, you should try to keep your server roles separate if you can. Use separate servers as DC's and file servers. Separating the servers is not really an option, as this is a school with a limited budget. Pretty much both servers have had the roles they are serving.

The drive has not been formatted - and the USN journal has not been deleted afaik. Its possible that a checkdisk has truncated it - but I do not remember that happening.

Ok so your domain name is alright then and I can understand your server roles for a limited environment. Is the fileserver found on appserver using the fqdn that the event log entry is saying is missing? Have you checked out any FRS tools?

The primary is the catalogue server - or the one holding the schema. Primary being the one in control, any others being secondary. I haven't tried a checkdsk yet as it indicated that one of the causes of this could be a checkdsk. Just one last thing, although you have the errors, are they actually causing any problems or are you trying to resolve the issue for peace of mind? FRS will keep retrying. Following are some of the reasons you would see this warning.

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.

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. After doing a bit of reading, it seemed like the right thing to do was a non-authoritative resotre, so I went through and created the registry key, then stopped and started the NTFRS service.

Information related to this event is shown below: Computer DNS name is "tisserver. File Replication Service is scanning the data in the system volume. The initialization of the system volume can take some time. It's been a while, but today I had a chance to carry out the journal wrap procedure- this solved the issue. I waited about 10 minutes, forced replication through sites and services, and now I see the netlogon and sysvol folders showing up on the R2 DC. To continue this discussion, please ask a new question.

Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Hey All! Much appreciated, -Chris. Microsoft Corporation Windows Server Windows Server R2 Best Answer. Thai Pepper. Verify your account to enable IT peers to see that you are a professional. View this "Best Answer" in the replies below ».

RobT64 This person is a verified professional. Lee This person is a verified professional. What has the event log got to say? Hey All, Been a little while, sorry for the delay. I've run dcdiag on both domain controllers, and found the following.

It goes on after that to suggest changing the registry parameters. I'm willing to guess that 4 is the cause of this entire issue.