<p><a href="http://wincert.net/wp-content/uploads/2015/01/windows-7.jpg"><img class="alignnone size-full wp-image-546" src="http://wincert.net/wp-content/uploads/2015/01/windows-7.jpg" alt="Windows 7 Box,install,printers,set network location,graphic card memory, aero peek,screensaver,synch,windows live,movie maker,remote desktop,destination path,driver signing,thinkvantage,printers,sensor,print drivers,grace period,8024402C,language pack,theme,memory dump,godmode,computer info,keys,folder,windows 7 profile" width="720" height="340" /></a></p>
<p>If you&#8217;re getting this error in the event log &#8220;NTDS General error 1173&#8221; on domain controllers followed by Internal event: Active Directory has encountered the following exception and associated parameters.</p>
<p><strong>Exception:</strong></p>
<p><strong>e0010004</strong><br />
<strong> Parameter:</strong><br />
<strong> 0 </strong></p>
<p><strong>Additional Data</strong><br />
<strong> Error value:</strong><br />
<strong> -1603</strong><br />
<strong> Internal ID:</strong><br />
<strong> 2050344</strong></p>
<p>You are probably having replication issues, here&#8217;s what you should do:</p>
<p>Run the following repadmin command on the primary domain controller (PDC) to create a .csv file that contains the list of destination domain controllers:</p>
<p><strong>repadmin /showrepl * /csv >;showrepl.csv</strong></p>
<p>Open the .csv file in Microsoft Excel, and then identify replication failures on destination domain controllers that have failed the incoming replication process and that display Win32 error 8451.<!--more--></p>
<p>On the domain controllers that log the &#8220;Win32 error 8451&#8221; error message, make sure that diagnostic logging for the 5 Replication Events registry entry is set to a value of 1. To do this, follow these steps:</p>
<p>Click Start, and then click Run.</p>
<p>In the Open box, type regedit, and then click OK.</p>
<p>Locate and then click the following registry key:</p>
<p><strong>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics</strong></p>
<p>In the details pane, double-click 5 Replication Events, type 1 in the Value data box, and then click OK.</p>
<p>Close Registry Editor.</p>
<p>On the destination domain controllers, verify that Directory Service event 1692 is logged in the Directory Service log. The event displays changes to the “memberâ€Â attribute of the security group or to other LVR-replicated attributes and to the lingering object GUIDs.</p>
<p>Remove the lingering objects from the Windows Server 2008-based or Windows Server 2003-based destination domain controllers by using the <strong>repadmin /removelingeringobjects</strong> command.</p>
<p>For more information about the <strong>Repadmin /removelingeringobjects </strong>command, click the following article number to view the article in the Microsoft Knowledge Base:</p>
<p>Disabling strict replication consistency functionality in the registry of Windows Server 2008-based or Windows Server 2003-based destination domain controllers does not resume replication. You must not set the value of the Strict Replication Consistency registry entry to 0 to unblock replication of directory partitions.</p>
<p>Do not force replication of directory partitions on source domain controllers by using the repadmin <strong>/sync</strong> command or an equivalent command together with the <strong>/force</strong> switch.</p>