Adeona update replica 0 not available

This article describes how to troubleshoot a problem in which Active Directory replication fails and generates an error The target principal name is incorrect. Home users: This article is only intended for technical support agents and IT professionals. If you're looking for help with a problem, please ask the Microsoft Community. This error occurs when the source domain controller doesn't decrypt the service ticket provided by the destination target domain controller. And the KDC has an old version of the password for the source domain controller.

Stop the KDC service on the destination domain controller. To do it, run the following command at a command prompt:. Start replication on the destination domain controller from the source domain controller. For example, if replication is failing on ContosoDC2. Start the Kerberos KDC service on the destination domain controller by running the following command:. If it doesn't resolve the issue, see the Resolution section for an alternative solution in which you use the netdom resetpwd command to reset the computer account password of the source domain controller.

If these steps don't resolve the problem, review the rest of this article. Repadmin commands that commonly indicate the 0x status include but aren't limited to the following ones:. The replicate now command in Active Directory Sites and Services returns the following error message: The target principal name is incorrect.

Right-clicking on the connection object from a source DC and then selecting replicate now fails. The on-screen error message is as follows:. Active Directory events that commonly cite the status include but aren't limited to the following ones:. It may be returned by the following lower layer components for different root causes:. It caused the destination domain controller to connect to the wrong source domain controller in a different Kerberos realm.

The KDC and source domain controller have different versions of the source domain controller's computer account password. You may notice that changes on primary replica are not getting propagated to secondary in a timely manner. To troubleshoot and resolve these problems, try the following:. You can reduce the transaction log sizes by configuring regular Backups at either primary or secondary servers.

Check System and Application event logs for hardware issues and other errors and work with the vendor to fix them. If you are using Virtual machines, check their knowledge base to see if there are any recently reported issues that may be contributing to the problem.

Check if the databases are taking a long time to recover by reviewing the messages in the SQL ErrorLog. Yes, you can set up multiple listeners for the same availability group. See: How to create multiple listeners for same availability group Goden Yao. Is it possible to have a separate NIC card for always on traffic and Client connectivity? Where can I find information on support for distributed transactions in AG configurations?

See: Transactions - availability groups and database mirroring. How to configure alerts for checking if the secondary is lagging behind the primary? Free YouTube Downloader. IObit Uninstaller. Internet Download Manager. Advanced SystemCare Free. VLC Media Player.

MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. Details are in the following Microsoft KB. See Also. Office Office Exchange Server. Not an IT pro? United States English.