Blog Post

Azure Database Support Blog
1 MIN READ

Lesson Learned #142: Login Timeout Expired connecting to Azure SQL Database

Jose_Manuel_Jurado's avatar
Jose_Manuel_Jurado
Icon for Microsoft rankMicrosoft
Nov 19, 2020

These last weeks we got several cases that our customers reported the following error message: Login timeout expired - 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.
TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond, in the following video I would like to share with you what is the issue, how to identify, fix and prevent it. 

 

Enjoy!

Updated Nov 19, 2020
Version 2.0

1 Comment

Sort By
  • ClarkX's avatar
    ClarkX
    Copper Contributor
    Nov 10, 2021

    This helped me a lot, I had changed some steps in a SSIS Job to run packages with the Default Setting RetainSameConnection = TRUE.

    RetainSameConnection is a property of an OLEDB Connection Manager. The default value of this property is FALSE. This default value makes SSIS execution engine open a new OLEDB connection for each task that uses the connection and closes that connection when the task is complete. 

     

    The setting of this property to "TRUE" caused the SSIS Server to run out of ports to open a Connection to the Azure Database - which showed up as various SQL Errors at sporadic times during execution.

     

    This article was a great help and resolved the issue. All open ports were closed once I had restarted the SSIS Server. Thank you!