locked
AG Listener timeout error state 08001 in Native client 11.0 RRS feed

  • Question

  • Client setup system as below

    OS: Windows 2008 R2 64 bit and installed SQL native client 11.0 (SQL 2012) for DSN creation.

    Successfully created DSN when using with default SQL server ODBC driver in client machine. (by using AG listener name)

    when try to connect via SQL native client 11.0 ODBC driver does not allowed and throwing SQL state 08001 error and time out messages.

    Pl. help, how overcome this time out errors? does it require to install any patches?

    Thanks

    Tuesday, August 2, 2016 4:27 AM

Answers

  • Yes.. In client machine win 2008 R2 -  SQL 2012 SSMS installed, I can able connect only AG Listener Name. 

    Does not connect if adding parameter -M (multisubnetfailover).. 

    Maybe this will help (Connection times out when you use AlwaysOn availability group listener with MultiSubnetFailover parameter):  https://support.microsoft.com/en-us/kb/2870437

    As a side note, I'd see if you can talk the client into upgrading from Windows 2008 R2. I would not recommend using it for any new projects.


    I hope you found this helpful! If you did, please vote it as helpful on the left. If it answered your question, please mark it as the answer below. :)


    Tuesday, August 2, 2016 5:19 AM

All replies

  • I recall there being several hotfixes and to-dos to make Availability groups work with Windows 2008 R2.

    Here's one of them: https://support.microsoft.com/en-us/kb/2687741

    It's been quite a while since I've thought about that configuration; so, I can't tell you if it's recommended or not.  Last time I looked into it was 2014 and the answer was don't run a SQL AG on Win 2008 R2.  You're much better off using Windows 2012 or later.

    Again, I don't know if that's changed but I would also question configuring Windows 2008 R2 as a new server mid way through 2016. Didn't mainstream support end in January 2015?

    Here's a supporting reference: http://stackoverflow.com/questions/14954887/are-there-problems-with-using-sql-server-alwayson-availability-groups-with-windo


    I hope you found this helpful! If you did, please vote it as helpful on the left. If it answered your question, please mark it as the answer below. :)


    Tuesday, August 2, 2016 4:48 AM
  • Hi Daniel.

    Thank you for reply...

    Due to application requirement AG Listener connect to windows server 2008 R2 machine.

    Again I tried by using SQLCMD command but still same error reported.

    C:\Users\Administrator>sqlcmd -SAG_NMSL -E -M
    Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : TCP Provider: The remote computer refused the network connection.
    .
    Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.
    Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : 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..
    

    Tuesday, August 2, 2016 4:55 AM
  • Can you connect to the Primary or Secondary directly? Try connecting to them directly

    If you can't connect to the Primary or Secondary from your remote machine. Make sure the firewall is correctly configured and that SQL has remote connections enabled.

    Also, Ping the IP & Name for the listener, Primary, and Secondary. See if you get anything you didn't expect.


    I hope you found this helpful! If you did, please vote it as helpful on the left. If it answered your question, please mark it as the answer below. :)



    Tuesday, August 2, 2016 4:56 AM
  • Yes.. In client machine win 2008 R2 -  SQL 2012 SSMS installed, I can able connect only AG Listener Name. 

    Does not connect if adding parameter -M (multisubnetfailover).. 

    Tuesday, August 2, 2016 5:05 AM
  • I tried to download that hotfix but download option not available from Microsoft .

    https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2687741&kbln=en-us

    Pl. give me correct URL link if any..

    Thanks

    Tuesday, August 2, 2016 5:10 AM
  • Yes.. In client machine win 2008 R2 -  SQL 2012 SSMS installed, I can able connect only AG Listener Name. 

    Does not connect if adding parameter -M (multisubnetfailover).. 

    Maybe this will help (Connection times out when you use AlwaysOn availability group listener with MultiSubnetFailover parameter):  https://support.microsoft.com/en-us/kb/2870437

    As a side note, I'd see if you can talk the client into upgrading from Windows 2008 R2. I would not recommend using it for any new projects.


    I hope you found this helpful! If you did, please vote it as helpful on the left. If it answered your question, please mark it as the answer below. :)


    Tuesday, August 2, 2016 5:19 AM