Problem with merge replicaton on SQL Server 2019

MR BILL 256 Reputation points
2021-06-22T16:58:48.89+00:00

I have setup a managed Windows Server and SQL Server 2019 in Azure. I have restored a database, created the distributor, created a publication for the database on the same SQL server, set the user in the database to be the owner and have rights to the merge stuff. After I zip up the unc folder and download it to a separate device and attempt to sync to the server I get an error of:
The remote server "myservername" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
The remote server "myservername" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
{call sp_helpdistpublisher (N'myservername') }

The machine is setup to allow remote connections.

I have ran the sp_helpdistpublisher and it's there.

What am I missing? Any help is appreciated, and I'll let you know up front I'm not a dba.

SQL Server on Azure Virtual Machines
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.
12,697 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alberto Morillo 32,886 Reputation points MVP
    2021-06-22T20:04:33.103+00:00

    Have you allowed traffic on port 1433 TCP as inbound and outbound on both computers? Have you enabled TCP protocol using SQL Server Configuration Manager? Are you allowing traffic on TCP port 1433 over VNETs? Can you connect to the remote server using SSMS?

    Make sure SQL Server is using mixed mode authentication, you restarted the database engine service after setting mixed mode, and you are using SQL login for authentication.

    This article may be useful.

  2. Seeya Xi-MSFT 16,436 Reputation points
    2021-06-23T05:37:00.567+00:00

    Hi @MR BILL ,

    Based on your description, you encounter the error during the merge replication synchronization process.
    In addition to the previously checked work you said, you also need to do:
    Ensure that the Merge Agent process account is a member of the db_owner fixed database role in publication database and distribution database. For more information, please review this article: Merge Agent Security.

    Best regards,
    Seeya

    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments