Results 1 to 4 of 4

Thread: Repadmin /replicate command gives error DsReplicaSync() failed with status 8452 (0x2104)

  1. #1
    Join Date
    Oct 2004
    Posts
    56

    Repadmin /replicate command gives error DsReplicaSync() failed with status 8452 (0x2104)

    I am getting issue while using Repadmin command between multiple domain controllers. I am having a setup of Windows 2003 servers on my network. Something is causing replication process to fail. I checked Event Viewer. But it is empty. There are no errors listed related to this. But I get error while using the command Repadmin /replicate. the error is related to some DsReplicaSync failure. Does anyone has idea about the same.

  2. #2
    Join Date
    Sep 2004
    Posts
    137

    Re: Repadmin /replicate command gives error DsReplicaSync() failed with status 8452 (0x2104)

    You have to run diags on your domain to figure out the issue and for that you need support tools. If it is not installed in your system then you can try Windows installation disc. There is a link that has ample of information on the same. You can use this to locate proper answer for your issue. It will be quiet helpful.

    Troubleshooting AD Replication error 1256: The remote system is not available.

  3. #3
    Join Date
    Dec 2007
    Posts
    2,291

    Re: Repadmin /replicate command gives error DsReplicaSync() failed with status 8452 (0x2104)

    Have you tried to follow the article based on "Troubleshooting AD Replication error 8452: "The naming context is in the process of being removed or is not replicated from the specified server" from this link - http://support.microsoft.com/kb/2023704. A complete step by step troubleshooting method is given on how to resolve the problem that you are facing.

  4. #4
    Join Date
    Jun 2009
    Posts
    1,112

    Re: Repadmin /replicate command gives error DsReplicaSync() failed with status 8452 (0x2104)

    I am thinking that if UDP is not opened then other ports could be blocked without any knowledge by the network team. There are some important ports like the UDP emepheral ports that are also not supposed to be opened. For a Windows 2003 server the emepheral ports are UDP 1024-5000. Check the below article to see what ports are needed to be opened for AD client and DC to DC communications:

    http://technet.microsoft.com/en-us/l.../bb727063.aspx
    http://technet.microsoft.com/en-us/l...23(WS.10).aspx

Similar Threads

  1. SCSI HDD error: Unexpected SCSI command failed
    By Mr.Ryszard in forum Hardware Peripherals
    Replies: 4
    Last Post: 13-02-2012, 07:54 PM
  2. Where are the Favorites, Command, and status bars in IE9
    By EricTheRed in forum Tips & Tweaks
    Replies: 1
    Last Post: 21-04-2011, 06:44 PM
  3. Replies: 3
    Last Post: 28-10-2010, 12:16 PM
  4. Update failed looking for Status.msi
    By Tiger Memon in forum Hardware Peripherals
    Replies: 5
    Last Post: 07-09-2010, 09:55 PM
  5. Error : command 'gcc' failed with exit status 1
    By _Gentoo_Nile_ in forum Operating Systems
    Replies: 3
    Last Post: 07-08-2009, 06:57 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,675,410,763.37457 seconds with 17 queries