DFSR Failure after BESR restore Event ID 2104 & 2004
We had a server 2008 box go down last week. I restored the system back using a Backup Exec System recovery image. The server had 2 partitions, C: F:. During the restore we resized the drives, c: was 20gb and d: was 140. We made c:\ 60 and f:\100. Anyway, replication is now failing between the other sites and the event log is filled with the errors listed below.
We have 4 AD sites, each with a DC. 3 sites have server 2003 and 1 has 2008. VPN's connect all sites. All vpn's are up and ptr records functioning properly.
We have 4 AD sites, each with a DC. 3 sites have server 2003 and 1 has 2008. VPN's connect all sites. All vpn's are up and ptr records functioning properly.
Error event 1
Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 2104
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The DFS Replication service failed to recover from an internal database error on volume Volume Letter:. Replication has been stopped for all replicated folders on this volume.
Additional Information:
Error: 9204 (The volume hosting the database is out of free space (-1808))
Volume: Volume GUID
Database: Volume Letter\System Volume Information\DFSR
Error event 2
Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 2004
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The DFS Replication service stopped replication on volume Volume Letter:. 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: Volume GUID
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was afraid of that but I guess I could just re-do the DFS. At least it is friday so the re-syncing will take place off hours.
ASKER
I removed the server from DFS replication as well as AD site replication, stopped the dfsr service and tried to rename the DFSR folder under f:\System Volume Information. I tried to rename it to DFSR.old, the folder then dissapears. When I refresh the folder comes back with the original name, DFSR
Might have to wait for AD replication?
ASKER
I tried to force replication through AD Sites and Services and then the error in the event log shows up. I forced the replication from another site.
ASKER
Well I have Microsoft on the phone to look at the issue. I will reply back with their repair steps. I will also award points to Datedman since they are the only user to reply.
Please let me know what you find out. Almost every time I've ever called them I've figured it out before they do but they do have decent people if you can get to them.
ASKER
I tried to rename the DFSR folder using the command prompt
cd "f:\System Volume Information"
rename DFSR DFSR.old
Then started the DFS services and replication started again.
cd "f:\System Volume Information"
rename DFSR DFSR.old
Then started the DFS services and replication started again.
ASKER
Thanks for responding.
no kidding, wonder if maybe you had show file extensions off and that messed up doing it with the GUI or something?
ASKER
Yep, im not sure why it worked while in the command prompt but it sure shocked the Windows tech who was about to hack up my registry. Hopefully this can save someone a lot of time and frustration.
BTW if it were me, I'd have just moved the folder out instead of renaming it.
ASKER