Hi All,
We recently discovered the following message in our application eventlog :-
event ID 467, source: ESENT
"ntfrs (6416) Database c:\windows\ntfrs\jet\ntfrs.jdb: Index GFileGuidIndex of table OUTLOGTable00001 is corrupted (0)."
We've seen a string of approximately 20 messages (all the same) appear daily. The time they appear is not consistent. I've checked out the ntfrs log and it has several errors in it over the past week but they are all as follows :-
"The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs
to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
[1] At the first poll which will occur in 5 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The
files may or may not be deleted from the old location depending on whether they are needed or not."
Obviously, I'm slightly concerned about these messages and was wondering if anyone can give me any information about correcting them. I have seen this article :-
but the error message in this case appears to be slightly different which is why I'm hesitant about following that particular solution. If anyone can offer any clues or advice, I'd greatly appreciate it!
The server is a virtualised SBS 2011 server and is the primary DC.
Tony