September 6, 2017 at 9:23 am
Hi,
I am trying to configure Merge Replication between 2 instances of SQL Server 2016 Enterprise Edition.
On ServerA\sql1, I configure a new Publication with the server acting as its own distributor
I use a snapshot folder, e.g. \\serverA\mergerepl that the domain account (sql and agent under same account) has permissions to
I select the database that I want to publish: DB1
Select Merge Replication
Select SQL Server 2008 or later
Select the table I want to replicate (only 1 at the moment: tab1test)
Select 'Create a snapshot immediately' and 'Schedule the Snapshot Agent to run at the following times' (left at default)
On the Snapshot Agent Security, I select 'Run under the SQL server Agent service account'. Connect to the Publisher by impersonating the process account
Create the publication, and give it a name 'MergeRepl'
According to the wizard, this completes successfully.
I then right click on the Publication and select New Subsriptions
Select the Publisher I have just created: 'MergeRepl'
Select Run all agents at the Distributor
Add a new Subscriber, selecting ServerB\sql2
Select 'New Database', which I call DB1
On the Merge Agent Security, I select 'Run under the SQL server Agent service account' and leave the other options as impersonating the process account.
Select run continuously on the synchronisation schedult
Create the initial subscription immediately
And a 'server' subscription type
Then I create the subscription, which again, according to the wizard, completes successfully.
I connect to ServerB\sql2 via SSMS and can see the new db: DB1.
However, I cannot see tab1test
When I collect to the Replication Monitor, the Initialisation is 100%, but the other steps are 0%. The message for the selected session is
Error messages:
The process could not connect to Subscriber 'ServerB\sql2'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. (Source: MSSQLServer, Error number: -1)
Get help: http://help/-1
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (Source: MSSQLServer, Error number: -1)
Get help: http://help/-1
Login timeout expired (Source: MSSQLServer, Error number: 0)
Get help: http://help/0
The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQLServer, Error number: 0)
Get help: http://help/0
The subscription to publication 'MergeRepl' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)
Get help: http://help/MSSQL_REPL-2147201019
In the SQL Server error log, the following messages are written:
Replication-Replication Merge Subsystem: agent ServerA\sql1-PR101-MergeRepl-ServerB\sql2-1 failed. The process could not connect to Subscriber 'ServerB\sql2'.
Further information:
The SQL Server service and SQL Server Agent service are both running under the same domain account: dom\sqlsvc
dom\sqlsvc is a local administrator on ServerA and ServerB
dom\sqlsvc is a sysadmin in SQL Server on ServerA and ServerB
The \\serverA\mergerepl folder is shared with 'Everyone' full control
I am logged onto both instances with the dom\sqlsvc account.
SQL Server Browser service is running
Windows Firewall is off
Any help appreciated.
Thanks
Andrew
September 6, 2017 at 2:04 pm
Did you check ServerB\sql2 to make sure remote connections is enabled?
You can sometimes track down connection issues by creating a linked server on ServerA\sql1 to connect to ServerB\sql2 - if possible, try using the same account you are using for the merge agent.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply