RE: DFSR Database Error - Event ID 2104

Hi Loren,
Somewhere there is a suggestion that the staging area has to be 5 x the size
of the largest file being replicated.
I just had a similar problem, which resulted in a new Initial Replication
from the other Partner resulting in massive Dataloss, (apparently works as
designed http://msdn.microsoft.com/en-us/libr...26(VS.85).aspx ) .

Be wary of event 4102 (requesting initial Replication) and if 4104 (Initial
replication Complete) happens, check the data and especially the
ConflictandDeleted Folder.

My suggestion is delete the DFSR Group, delete the data on that server and
start again.


"Loren" wrote:

> Hello -
> I am receiving a bunch of Event ID 2104's & 2106's on one of our (2003R2,
> SP2) file servers. they are occurring once every hour and it has been
> doing this for the last seven days. it appears that DFS is recovering
> from the db error however it quickly fails again.
>
> Here are the exact errors:
>
> Event Type: Error
> Event Source: DFSR
> Event Category: None
> Event ID: 2104
> Date: 7/23/2008
> Time: 6:51:51 AM
> User: N/A
> Computer: SERVER1
> Description:
> The DFS Replication service failed to recover from an internal database
> error on volume D:. Replication has been stopped for all replicated
> folders on this volume.
>
> Additional Information:
> Error: 9210 (There was a write conflict on the database record (-1102))
> Volume: 152B338C-4CC9-11DC-834F-806E6F6E6963
> Database: D:\System Volume Information\DFSR
>
> Event Type: Information
> Event Source: DFSR
> Event Category: None
> Event ID: 2106
> Date: 7/23/2008
> Time: 6:51:12 AM
> User: N/A
> Computer: SERVER1
> Description:
> The DFS Replication service successfully recovered from an internal
> database error on volume D:. Replication has resumed on replicated folders
> on this volume.
>
> Additional Information:
> Volume: 152B338C-4CC9-11DC-834F-806E6F6E6963
> Database: D:\System Volume Information\DFSR
>
>
> When I run a diagnostics report on the replication group the server has
> the following errors:
>
> a.. A database problem is blocking replication on volume D:
> b.. Volume D: is full or failing
> c.. Cannot access DFS Replication performance counters
> d.. Cannot access the local WMI repository
> The D: drive has over 120GB of free space so disk space is not an issue.
> I've ran chkdsk on D: as well but that didn't seem to fix anything. I'm
> willing to bet that once the database problem is rectified that these
> other errors may correct themselves.
>
> Anyway, has anyone seen this before? any suggestions on how to fix this
> problem?
>
> Thanks in advanced!
>
>