Azure SQL Database
An Azure relational database service.
6,311 questions
SQL Replication with error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 44%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Andrew Lamb
0
Reputation points
Error "Agent message code 20084. The process could not connect to Distributor " in distributor agent, how do I fix this
Azure SQL Database
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,492 questions
{count} votes
-
Olaf Helper 47,416 Reputation points2024-03-28T09:56:14.98+00:00 Have you check if the distributor is running and can be connected to?
-
MikeyQiaoMSFT-0444 3,300 Reputation points2024-03-28T10:12:27.9466667+00:00 Can you provide more detailed information, such as your system information, the latest errorlog, etc
-
Andrew Lamb 0 Reputation points
2024-03-28T12:55:24.28+00:00 This is a newly created SQL Managed Instance with a large restored database with a single publication with around 550 articles. 4 subscriber databases (SQL 2022 Web Version recently deployed) - SNapshot agent created snapshot to Azure storage - this took around 6 hours. On completion 4 subscributuin distribution agents started 3 of these have successfully played the snapshots and are now in syn. 4 one has this error. I drop the subscription and recreated - still the same error.
So yes distribution DB is accessibledistribution history:
Starting agent.Distribution agent for subscription added.
Agent History:
Repeated these messages- Message
LogonUser for wcow repl user succeeded
2) MessageThe replication agent has been successfully started. See the Replication Monitor for more information.
3) Message2024-03-28 12:50:49.325 Copyright (c) 2016 Microsoft Corporation
2024-03-28 12:50:49.325 Microsoft SQL Server Replication Agent: distrib
2024-03-28 12:50:49.325
2024-03-28 12:50:49.325 The timestamps prepended to the output lines are expressed in terms of UTC time.
2024-03-28 12:50:49.325 User-specified agent parameter values:
-Subscriber 10.1.34.77 -SubscriberDB <Redcated> -Publisher <Redcated>.database.windows.net -Distributor <Redcated>.database.windows.net -DistributorSecurityMode 1 -Publication FullBusinessPublication -PublisherDB <Redcated> -Continuous -XJOBID 0x8042CFA7078BFD4DA2FCFC333A131E67 -XJOBNAME <Redcated>-10.1.34.77-78 -XSTEPID 2 -XSUBSYSTEM Distribution -XSERVER <Redcated>.database.windows.net -XCMDLINE 1 -XDB -XHOST \\.\pipe\_DB24C_2-bd21fd8bb0ec\sql\query -T 500 -T 504 -XCancelEventHandle distribCancel ```2024-03-28 12:50:49.325 Startup Delay: 2451 (msecs) 2024-03-28 12:50:51.844 Connecting to Distributor '<Redcated>.database.windows.net' 2024-03-28 12:50:52.016 Agent message code 20084. The process could not connect to Distributor '<Redcated>.database.windows.net'. 4) Message The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information. As mention 3 other subscription setup identically and working fine -
Greg Low 1,980 Reputation points Microsoft Regional Director2024-04-02T09:40:46.0933333+00:00 Are they all at the same version and build level (CU level) of SQL Server?
Are they all fully patched to the latest CU?
Sign in to comment
Sign in to answer