Domain replication Issue with Event ID 13559

[chicagotech]

Our client is running Windows 2003 DC. They have added another Windows 2003 as second DC. However the replication doesn’t work with the symptoms:

1.Net share doesn’t show netlogon and sysvol on the new DC
2.The Event Viewer has these errors:
Event Type: Warning

Event Source: NTDS Replication

Event Category: Replication

Event ID: 1586

Date: 3/31/2012

Time: 11:10:22 PM

User: NT AUTHORITY\ANONYMOUS LOGON

Computer: SERVER4

Description:

The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.


A full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.


The checkpoint process will be tried again in four hours.


Additional Data

Error value:

1722 The RPC server is unavailable.

Event Type: Error

Event Source: NtFrs

Event Category: None

Event ID: 13559

Date: 4/1/2012

Time: 12:31:43 AM

User: N/A

Computer: SERVER4

Description:

The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.

This was detected for the following replica set:

"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"


Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.


[1] At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.

[2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.

3. DCDiag shows: Unable to connect to the NETLOGON share!

4. netdiag shows: Domain membership test . . . . . . : Failed

[WARNING] Ths system volume has not been completely replicated to the local

machine. This machine is not working properly as a DC.

The original DC doesn’t have any errors. Creating sysvol on the second DC doesn’t fix the problem. How can we fix it?


--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

[chicagotech]

Just based on above-mentioned error message and info, we can know that in this new DC, there are at least existing two aspects errors:

•AD replicating
•Sysvol replication
Since this is the new add DC, then I strongly suggest you rejoin this DC to the domain again. the reason is simple as we need create a healthy environment or conditions when the whole IT structure be built first. Moving on, the specific steps are:

1.First please disjoin this DC from the DC and be a member server
2.And then disable the firewall between PDC and this member server
3.Please clean up the dcpromo.log and dcpromoUI.log under the c:\WINDOWS\Debug folder
4.Next, rename this member server as another server name (in order to avoid conflict)
5.Check the PDC to see if there is navigate critical errors, you can use the DCdiag command and net share command
6.If everything fine, please just promote this member server to be a DC again.

[chicagotech]

I followed the instruction, but that doesn't fix the problem. Now I get these event ID:
In the server2, it received evend ID 13559 and 13568

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13559
Date: 4/14/2012
Time: 9:34:03 PM
User: N/A
Computer: SERVER2
Description:
The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.

[1] At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/15/2012
Time: 9:11:40 AM
User: N/A
Computer: SERVER2
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

In the standby server (server4), received event ID 13508

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 4/14/2012
Time: 8:59:27 PM
User: N/A
Computer: STANDBY
Description:
The File Replication Service is having trouble enabling replication from SERVER2 to STANDBY for c:\windows\sysvol\domain using the DNS name server2.cfibilling.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name servercfi2.cfibilling.com from this computer.
[2] FRS is not running on server2.cfibilling.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 00 00 ....

[chicagotech]

The problem was solved after setting the "nonauthoritative mode restore (D2)" value on the failing domain controller, and the "authoritative mode restore (D4)" value on the working domain controller. The details can be found here:

Event ID 13559: replica root path has changed - ChicagoTech.netApr 1, 2012 ... A single event ID 13508 does not mean anything is broken or not working; simply
look for event ID 13509 to make sure that the problem was ...
www.chicagotech.net/netforums/viewtopic.php?f=3&t=15680

[chicagotech]

Please refer to the following Microsoft KB articles to troubleshoot the issue:


Troubleshooting Active Directory operations that fail with error 8452: "The naming context is in the process of being removed or is not replicated from the specified server."

http://support.microsoft.com/kb/2023704


Troubleshooting Active Directory operations that fail with error -2146893022: The target principal name is incorrect.

http://support.microsoft.com/kb/2090913


Event ID 13552 and 13559 on DFS Replica Members or Domain Controllers That Are Hosting a SYSVOL Replica Set

http://support.microsoft.com/kb/819268


Troubleshooting RPC Endpoint Mapper errors using the Windows Server 2003 Support Tools from the product CD

http://support.microsoft.com/kb/839880


If the issue persists, would you please send me the following log files here for our further research.


Dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt

repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt (if more than one DC exists)

dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)

[chicagotech]

Follow this: create a 0-byte file that is named NTFRS_CMD_FILE_MOVE_ROOT in the root folder of the path that is specified in the Event Viewer description. To do this, follow these steps:

1.Click Start, click Run, type explorer, and then click OK.
2.Locate the root folder of the <var>CurrentLocation</var> folder, where <var>CurrentLocation</var> is the path that is specified in the Event Viewer description.
3.Right-click a blank area in the root folder of the <var>CurrentLocation</var> folder, point to New, and then click Text Document.
4.For the file name of the new text document, type the following, and then press ENTER:
NTFRS_CMD_FILE_MOVE_ROOT
5.You may receive the following message:
If you change a filename extension, the file may become unusable. Are you sure you want to change it?
If you do receive this message, click Yes to save the file without a file name extension.
Ref: http://support.microsoft.com/kb/887440

Also as per event, NETLOGON share is not available. post dcdiag /q and repadmin /replsum result.


--------------------------------------------------------------------------------

[blin]

This is to confirm these steps fix the problem.
1. Stop FRS on all DCs.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore/Process at Startup
4. On the Edit menu, click Add Value, and then add the following registry value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2 ("nonauthoritative mode restore (D2)" value on the failing domain controller)
Value data: D4 (the "authoritative mode restore (D4)" value on the working domain controller).
5. Quit Registry Editor.
6. Restart FRS on all DCs.