Windows Server 2012R2 Replication Errors

Question

Hi, just working through my 2012R2 exams so this is in a lab environment but would love some help on this one as I've been struggling to find a solution on this one.

Just to give you a bit of history, up until recently I had a single 2012R2 DC Environment on my lab. About 6 months ago, I had to follow the below threads to recover my DC after what I can only assume was an unclean shutdown of my host.

http://blog.shiraj.com/2014/10/how-to-fix-c00002e2-directory-services-could-not-start-blue-screen/

https://support.microsoft.com/en-us/kb/2751452

I have been working through scenarios no problem until recently.

I have added a 2nd DC to the existing domain successfully although upon checking the status of the replication I appear to be coming across some issues in relation the the sysvol folder not replicating correctly on the additional DC.

The folder and subfolders are there but empty on the 2nd DC.

I have ran DCDiag on the original DC today, the majority of tests pass ok (some have failed but I have transferring roles, shutting down the vms on and off as I have used them, but the below has been apparent since I promoted the 2nd DC):

There are warning or error events within the last 24 hours after the

SYSVOL has been shared.  Failing SYSVOL replication problems may cause

Group Policy problems. (from DCDIAG)

I have ran the replication health monitor on the original DC and get the following 2 outputs.

1. The DFS Replication service was unable to recover from an internal database error on volume C:. Replication has stopped for all replicated folders on this volume until the database is automatically rebuilt. If the database is rebuilt successfully, replication will resume after the rebuilding is complete. If the database cannot be rebuilt, a separate event is generated. If you are seeing this error more than two times in seven days, we recommend that you run Chkdsk on the volume that contains the database. Event ID: 2104
2. 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. Event ID: 2004

I have followed threads to try and resolve this issue without any luck, I can also confirm that the disk is not full or failing.

On the 2nd DC the health is as follows:

This member is waiting for initial replication for replicated folder SYSVOL Share and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory Domain Services. After the member detects that it is part of replication group, the member will begin initial replication.

In the event logs on the original DC I have also been picking up the following event logs:

Log Name:      Application

Source:        ESENT

Date:          16/04/2016 13:51:57

Event ID:      516

Task Category: Logging/Recovery

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     server.domain

Description:

DFSRs (1388) \.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: Database \.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: Page 46 (0x0000002e) failed verification due to a timestamp mismatch.  The 'before' timestamp persisted to the log record was 0x10fbb but the actual timestamp on the page was 0x11004.  The 'after' update timestamp 0x11017 that would have updated the on page timestamp.  Recovery/restore will fail with error -567.  If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">516</EventID>

    <Level>2</Level>

    <Task>3</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-04-16T12:51:57.000000000Z" />

    <EventRecordID>7033</EventRecordID>

    <Channel>Application</Channel>

    <Computer>server</Computer>

    <Security />

  </System>

  <EventData>

    <Data>DFSRs</Data>

    <Data>1388</Data>

    <Data>\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: </Data>

    <Data>\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db</Data>

    <Data>46 (0x0000002e)</Data>

    <Data>0x10fbb</Data>

    <Data>0x11004</Data>

    <Data>-567</Data>

    <Data>0x11017</Data>

  </EventData>

</Event>

Log Name:      Application

Source:        ESENT

Date:          16/04/2016 13:51:57

Event ID:      454

Task Category: Logging/Recovery

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      server.domain

Description:

DFSRs (1388) \.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: Database recovery/restore failed with unexpected error -567.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">454</EventID>

    <Level>2</Level>

    <Task>3</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-04-16T12:51:57.000000000Z" />

    <EventRecordID>7034</EventRecordID>

    <Channel>Application</Channel>

    <Computer>server</Computer>

    <Security />

  </System>

  <EventData>

    <Data>DFSRs</Data>

    <Data>1388</Data>

    <Data>\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: </Data>

    <Data>-567</Data>

  </EventData>

</Event>

I think these are related to my initial issue but any advice would be appreciated.

Thanks

Answer 1

Kindly post your query at:

https://social.technet.microsoft.com/Forums/

Server questions are best handled there.

Answer 2

I am getting the error in the health check report "DFS Replication unable to replicate files for replicated folder CAR01 due to insufficent disk space". But enough space available on the server.