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

Has anyone successfully setup AlwaysON Availability group on Windows 2016 datacentre using Azure Hyper-V VM

$
0
0

I have been struggling to resolve the issue in my current environment and i am not able to fix the issue.  I have tried everything that is available in net but nothing is working.  Once again I am giving my problem definition

Environment

2 SQL VM - Windows 2016 Datacenter

2 SQL server 2016 enterprise version

1 Listener VM Windows 2016

My setup runs fine when Primary VM is primary , I can connect to my primary server using Listener IP from any other VMs with no issue.  The problem starts when i move my PRimary to Secondary VM,  It only connected from my Secondary VM using Listener and not connecting from any other machine.  I am getting following error 

C:\windows\system32>sqlcmd -S EMCPRODSQLCAP -E
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: The wait operation timed out.
.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : 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..

C:\windows\system32>

If this issue does not fix I may lose my contract.  I am having strong feeling that I may be hitting a bug in this,


Viewing all articles
Browse latest Browse all 4532

Trending Articles



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