Windows Server

jhoop · Guest

This is a DFS share replicated between two win2003 servers only. On one
server the file replication service will not start. I am also receiving
these event IDs:

1)Event Source: NtFrs Event ID: 13506
Description:
The File Replication Service failed a consistency check
(SEntry->FileSizeInKb <= StagingAreaAllocated)
in "StageReleaseNotRecovered:" at line 520.
The File Replication Service will restart automatically at a later
time. If this problem persists a subsequent entry in this event log
describes the recovery procedure.
For more information about the automatic restart right click on My
Computer and then click on Manage, System Tools, Services, File
Replication Service, and Recovery.

2)Event Source: NtFrs Event ID: 13555
Description:
The File Replication Service is in an error state. Files will not
replicate to or from one or all of the replica sets on this computer
until the following recovery steps are performed: <... deleted... for
the sake of being brief...>

The servers that host the dfs root are not DCs.
I have already increased the "staging space limit in KB" in the
registry w/ no success (I decided to attempt this since "FileSizeInKb"
and "StagingAreaAllocated" in the text for the 13506 error pointed me
in that direction).

I have also found this log in C:\Windows\Debug\NtFrs_001.log that
seemded to indicate a problem w/ c:\windows\ntfrs\jet
---------------------------------------------------------
<FrsPrintEvent: 4984: 607: S0: 22:34:50> :E: STRINGS:

<FrsPrintEvent: 4984: 610: S0: 22:34:50> :E: 0 :
'c:\windows\ntfrs\jet'
<DbgStackInit: 4984: 748: S0: 22:34:50> :S: Symbol
search path is .
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> ++
0x010427db: Unknown Symbol (WStatus ERROR_INVALID_ADDRESS)
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> ++
0x01043143: Unknown Symbol (WStatus ERROR_INVALID_ADDRESS)
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> ++
0x0105b8a7: Unknown Symbol (WStatus ERROR_INVALID_ADDRESS)
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> ++
0x010904ee: Unknown Symbol (WStatus ERROR_INVALID_ADDRESS)
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> ++
0x01093398: Unknown Symbol (WStatus ERROR_INVALID_ADDRESS)
<StageReleaseNotRecovered: 4984: 520: S0: 22:34:50> :S:
ASSERTION FAILURE: SEntry->FileSizeInKb <= StagingAreaAllocated
<DBService: 4984: 3879: S0: 22:34:50> ++ ERROR -
EXCEPTION (000003e3) : WStatus: ERROR_OPERATION_ABORTED
<DBService: 4984: 3883: S0: 22:34:50> :S: FATAL
ERROR - DataBase could not be started or created: FStatus:
-1989316576-???
<FrsSetServiceStatus: 4984: 434: S0: 22:34:50> :SC:
SetServiceStatus(State 1, CheckPoint 0, Hint 90000, ExitCode 1450)
succeeded
---------------------------------------------------------

Help/advice would be great. Thanks.

Paul Williams [MVP] · Guest

Without the steps that you cut out I can't really offer any advice.

Although, from a simplicity standpoint, a non-authorative restore will
probably fix this. Yes, there are better ways, such as deleting and
tweaking the FRS attributes in the FRS Member and/ or Subscriber sets, but
this is quicker, and I'm not going to be around for a week or so as I'm off
on holiday...

NtFrs is already stopped as it can't start. Therefore set BurFlags to D2
[1] and then start FRS (net start ntfrs). Go make a cuppa and come back and
check the event logs.

---
[1] BurFlags is a registry value under this key:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ NtFrs\ Parameters\
Backup/Restore\ Process at Startup

You set this value and start FRS on the machine with the replica that can't
replicate.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

jhoop · Guest

Yes a non authoritative restore fixed this.

File Replication service will not start: Receive events 1350

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1