Hi,
I am using SQL 2019 server,
updates in server a and b from machine 2
reflects in all 4 servers a and b in machine 1 and c and d in machine 2
but updates in c or d is updating only in that server
in replication monitor of Machine 2 , only server in machine 2 is showing error
Agent 'abc\MSSQLSERVER-AdventureWorksLT2019-2' is retrying after an error. 2 retries attempted. See agent job history in the Jobs folder for more details.
can anyone help me to fix this
Thank You
If updates from machines A/B replicate to all nodes but changes on C/D only stay local and the replication agent on Machine 2 shows retries, first check the agent job history and SQL Server error log for the exact error text (that will point to permissions, connectivity, or schema/identity conflicts). Common causes are: the distribution/agent on Machine 2 cannot connect to the distributor or publisher (firewall, port/endpoint, or wrong account), the SQL Server Agent service account lacks necessary permissions, the peer node is disabled or out-of-sync, or there are schema/identity/constraint differences causing the transaction to fail. Actionable steps: 1) open the failing agent job history and copy the full error; 2) verify SQL Server Agent is running and the agent account has rights on all involved instances; 3) confirm distributor accessibility and that TCP ports/endpoints and firewall rules allow replication traffic; 4) compare publication articles/schema and identity ranges to ensure no conflicts; 5) check Windows Event Log and the replication monitor details for the failing peer; and 6) if a node is inconsistent, consider taking it out of the topology, reinitialize it (or re-create its subscription) and then rejoin. Paste the exact agent error text and I’ll give the specific fix/commands to run.
Peer-to-peer replication between two machines may come up short due to organize network issues, firewall limitations, bungled arrangements, confirmation issues, or form incongruence. Confirm authorizations, replication settings, ports, and guarantee both frameworks are legitimately synchronized and reachable.bhulekh up
