What are the challenges you face when working across database platforms? Take the survey

SQL Compare 13 not connecting to AG listener

elsimerelsimer Posts: 2 New member
edited September 27, 2017 5:22PM in SQL Compare
I have an AlwaysOn Availability Group listener (call it AG1) consisting of a primary (SQL01) and a secondary (SQL02). Using SQL authentication, I'm able to connect using SQL Compare with no difficulty. However, when I attempt to connect to AG1 using SQL Compare 13 (latest version attempted was I get an error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).
I get the same message whether I enter the correct password or not, and it works without issue if I attempt to connect directly to the primary or secondary instead of the listener. Same behavior in SQL Data Compare 12/13.
We are running on SQL Server 2016 SP1 Enterprise edition.

Edit: Additionally, this only occurs under SQL Authentication. When using a trusted connection (Windows Authentication) both versions work without issue.

Any ideas?


Sign In or Register to comment.