The DFS Replication service failed to recover from an internal DB

Discussion:

(too old to reply)

darth lawb

2006-07-27 15:41:02 UTC

Our server had a problem rebuilding its array, so after a reboot the server
came back up it had a problem with DFS. The following errors are being logged
every hour with the exception of 2004.

Any ideas other that chkdsk which is recommended?

Event ID 2106

The DFS Replication service successfully recovered from an internal database
error on volume C:. Replication has resumed on replicated folders on this
volume.

Additional Information:
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR

Event 2104

The DFS Replication service failed to recover from an internal database
error on volume C:. 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: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR

Event ID 2004

The DFS Replication service stopped replication on volume C:. This failure
can occur because the disk is full, the disk is failing, or a quota limit has
been reached. This can also occur if the DFS Replication service encountered
errors while attempting to stage files for a replicated folder on this
volume.

Additional Information:
Error: 9014 (Database failure)
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963

--
There are always two, a master and an apprentice.

Jill Zoeller [MSFT]

2006-07-31 17:04:39 UTC

Permalink

We're discussing this now...
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

Post by darth lawb
Our server had a problem rebuilding its array, so after a reboot the server
came back up it had a problem with DFS. The following errors are being logged
every hour with the exception of 2004.
Any ideas other that chkdsk which is recommended?
Event ID 2106
The DFS Replication service successfully recovered from an internal database
error on volume C:. Replication has resumed on replicated folders on this
volume.
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event 2104
The DFS Replication service failed to recover from an internal database
error on volume C:. Replication has been stopped for all replicated folders
on this volume.
Error: 9210 (There was a write conflict on the database record (-1102))
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event ID 2004
The DFS Replication service stopped replication on volume C:. This failure
can occur because the disk is full, the disk is failing, or a quota limit has
been reached. This can also occur if the DFS Replication service encountered
errors while attempting to stage files for a replicated folder on this
volume.
Error: 9014 (Database failure)
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
--
There are always two, a master and an apprentice.

Jill Zoeller [MSFT]

2006-08-01 16:53:18 UTC

Permalink

Can you contact me offline? We'd like to gather log files to investigate
this further. Please use my email address minus "online."
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

aj_26

2006-08-30 21:22:02 UTC

Permalink

so was there ever a resolution for this?

Post by Jill Zoeller [MSFT]
Can you contact me offline? We'd like to gather log files to investigate
this further. Please use my email address minus "online."
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

Jill Zoeller [MSFT]

2006-08-30 21:49:51 UTC

Permalink

No, I never heard back from the customer.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

Post by aj_26
so was there ever a resolution for this?

Post by darth lawb
Our server had a problem rebuilding its array, so after a reboot the server
came back up it had a problem with DFS. The following errors are being logged
every hour with the exception of 2004.
Any ideas other that chkdsk which is recommended?
Event ID 2106
The DFS Replication service successfully recovered from an internal database
error on volume C:. Replication has resumed on replicated folders on this
volume.
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event 2104
The DFS Replication service failed to recover from an internal database
error on volume C:. Replication has been stopped for all replicated folders
on this volume.
Error: 9210 (There was a write conflict on the database record (-1102))
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event ID 2004
The DFS Replication service stopped replication on volume C:. This failure
can occur because the disk is full, the disk is failing, or a quota
limit
has
been reached. This can also occur if the DFS Replication service encountered
errors while attempting to stage files for a replicated folder on this
volume.
Error: 9014 (Database failure)
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
--
There are always two, a master and an apprentice.

MichaelU

2006-08-31 13:53:02 UTC

Permalink

Hi, Im getting similiar entries in my apps log every hour:
Dfsr (3300) \\.\D:\System Volume
Information\DFSR\database_CC1A_CABD_1ACA_A434\dfsr.db: An attempt to
determine the minimum I/O block size for the volume "\\.\D:\" containing
"\\.\D:\System Volume Information\DFSR\database_CC1A_CABD_1ACA_A434\" failed
with system error 5 (0x00000005): "Access is denied. ". The operation will
fail with error -1032 (0xfffffbf8).

And in the dfs log:
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: 9201 (Access was denied to the database (-1032))
Volume: 2B39205E-A0F1-11D8-A72A-806D6172696F
Database: D:\System Volume Information\DFSR

I have run chkdsk witout any problems and the disk is not full
What should I do?
--
Michael u

Post by Jill Zoeller [MSFT]
No, I never heard back from the customer.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.

Post by aj_26
so was there ever a resolution for this?

Post by darth lawb
Our server had a problem rebuilding its array, so after a reboot the server
came back up it had a problem with DFS. The following errors are being logged
every hour with the exception of 2004.
Any ideas other that chkdsk which is recommended?
Event ID 2106
The DFS Replication service successfully recovered from an internal database
error on volume C:. Replication has resumed on replicated folders on this
volume.
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event 2104
The DFS Replication service failed to recover from an internal database
error on volume C:. Replication has been stopped for all replicated folders
on this volume.
Error: 9210 (There was a write conflict on the database record (-1102))
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
Database: C:\System Volume Information\DFSR
Event ID 2004
The DFS Replication service stopped replication on volume C:. This failure
can occur because the disk is full, the disk is failing, or a quota
limit
has
been reached. This can also occur if the DFS Replication service encountered
errors while attempting to stage files for a replicated folder on this
volume.
Error: 9014 (Database failure)
Volume: 4EB39360-A45D-11DA-986D-806E6F6E6963
--
There are always two, a master and an apprentice.

Ned Pyle [MSFT]

2006-08-31 17:29:11 UTC

Permalink

I actually have a case open where we are seeing these symptoms right now.
Still trying to determine what's going on. As soon as I know more I'll try
to respond here.

If you want immediate assistance, you will need to open your own case though
with PSS. I'm doing debugs, if that gives you an idea of how deep the
troubleshooting has gotten to; well outside the scope of the Newsgroup. :-)

--
Ned Pyle
Microsoft Enterprise Platforms Support

All postings on this newsgroup are provided "AS IS" with no warranties, and
confer no rights.
For more information please visit
http://www.microsoft.com/info/cpyright.mspx to find terms of use.

MichaelU

2006-09-01 06:22:02 UTC

Permalink

This post might be inappropriate. Click to display it.

Ned Pyle [MSFT]

2006-09-01 14:24:12 UTC

Permalink

Ahhh, good deal. That is unfortunately not what we're seeing in the other
case - customer has somehow managed to have 2 DFSR.EXE's running at same
time. :-)

Papastef

2006-09-06 08:47:28 UTC

Permalink

Hello all

Had the same issue here and managed to fix it with the following steps:

1. Disabled all connections with the affected server.
2. Disabled DFS service on the affected server.
3. Deleted the partition that hosts replicated folders.
4. Re-created the partition that hosts replicated folders.
5. Re-enabled DFS service.
6. Restarted the server
7. Re-enabled connections with the other servers.

After enabling connections (7) got events 5012:

The DFS Replication service failed to communicate with partner STN-DFS-01
for replication group Common Site Data. The partner did not recognize the
connection or the replication group configuration.

for every connection that I re-enabled but they were cleaned automatically
after ~15 min.

aj_26

2006-09-07 16:32:01 UTC

Permalink

I was also able to resolve the issue without deleting the partition where the
replicated data resides.

1. deleted replication groups associated with the drive that is not able to
replicate
2. deleted the DFSR directory underneath the System Volume Information
directory (i.e. I:\System Volume Information\DFSR)
3. restarted the DFSR service
4. re-created the replication groups

Post by Papastef
Hello all
1. Disabled all connections with the affected server.
2. Disabled DFS service on the affected server.
3. Deleted the partition that hosts replicated folders.
4. Re-created the partition that hosts replicated folders.
5. Re-enabled DFS service.
6. Restarted the server
7. Re-enabled connections with the other servers.
The DFS Replication service failed to communicate with partner STN-DFS-01
for replication group Common Site Data. The partner did not recognize the
connection or the replication group configuration.
for every connection that I re-enabled but they were cleaned automatically
after ~15 min.