August 9, 2023 at 11:42 pm
Hi There.
I'm trying to get replication to be able to look at a subscriber which is using AG listener but it is not working.
I have a standalone server (P1) which is both publisher and distributor and it replicates to a subscriber that is in an AG (S1, S2) and I want it to be able to see the listener and not the actual server name. I've checked and found that it is not possible, but I've already done this before and it worked so I'm not sure why it's not working for this particular situation. Let me know if more info is required.
Any help would be appreciated.
August 10, 2023 at 11:16 pm
One thing that might be a factor is the SQL server version as it is a difference in the current set up I am attempting compared to other ones I did before.
When Publisher is SQL server 2014 replicating to subscriber SQL server 2016 - it works. I went around the wizard by scripting out the steps and then putting in the listener name in place of the actual server name and executing that to get the system to accept it. However, when;
Publisher is SQL server 2016, even scripting out the steps and running that doesn't work. The script executes successfully and everything looks good. However, it keeps saying;
Message:
Replication-Replication Distribution Subsystem: agent <replication job name> failed. The process could not connect to Subscriber <listener name>
and later started giving this other message;
Message:
Replication-Replication Distribution Subsystem: agent (null) failed. The subscription to publication <publisher server name> has expired or does not exist.
I've seen a couple of articles about using linked servers but I'm not really sure how it'll work for my case.
September 30, 2023 at 7:09 am
Fixing transactional replication issues in SQL Server requires a systematic approach that involves identifying the issue, checking the replication configuration, agents, distribution database, publication and subscription databases, reinitializing the subscription if necessary, and monitoring replication.
Upgrading the SQL server publication to 2016 could have caused issues with the replication process components. You could repair or clear the replication settings, and data. Please try using a domain user with admin permissions if already not done so.
You could delete the replication publication and Subscription, and set it up from scratch after SQL server 2016 upgrade after reviewing the errors.
DBASupport
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply