Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Error adding Replica to SQL AlwaysOn failover cluster

$
0
0

Hi All -

I'm getting an error adding Replica to SQL AlwaysOn failover cluster in the new availability group wizard.  When I enter the name of the target node (secondary replica) server and press connect, I get the following:   

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) (Microsoft SQL Server, Error: 2)

The system cannot fine the file specified

The SQL Browser service is up and running on the target.  I am using an Azure VM for my SQL instance.  This cluster spans geographies from our on-premise site to Azure via a VPN.  This is a multi-subnet cluster. I'm attempting to create a new AG from the primary replica node and the target is a node on Azure called SSASNodeAz03. 

I'm reviewing all the setup docs again, but I'm hoping you have some recommendations.

Many Thanks,

JBP

Screen shots:

http://1drv.ms/1FDrHVb

Full error:

Connect to Server

Cannot connect to ssasnodeaz03

Additional information:

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) (Microsoft SQL Server, Error: 2)

The system cannot fine the file specified


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>