Microsoft ODBC Driver 17 for SQL Server Login timeout expired after migrating to Windows Server 2019 and SQL Server 2016 Standard RRS feed

  • Question

  • Hi all,

    We are experiencing db connection issues after migrating from Windows Server 2012R2/SQL Server 2016 Enterprise to Windows Server 2019/SQL Server 2016 Standard.

    The message we see in the logs when it happens contains the following: [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired’

    It seems that the message appears when the db is used a lot and there are many connections to it. The errors occur with two out of three applications:

    Windows : .NET (SQLConnection) application

    Linux : PHP7.2/Linux driver

    It does not happen under Windows with SQLOLEDB.

    The issue does not occur consistently which makes it more difficult to reproduce and debug.

    We have checked/tried the following to no avail:

    - SQL user check
    - Temporarily disabling Windows Firewall
    - Temporarily disabled Windows Defender
    - Verified MTU settings
    - Verified DNS
    - Checked all logs

    Other services are fine.

    This is our setup:

    - PowerEdge R730
    - Microsoft Windows Server 2019 Standard
    - 2x Intel Gigabit 4P I350-t rNDC (Driver version
    - NIC-Teaming on two ports (different networkcards no LACL)
    - Microsoft SQL Server 2016 Standard

    Basically the problem started since the upgrade to Windows Server 2019 en downgrade from SQL Server 2016 Enterprise to Standard.

    Any help which would lead us into the right direction is greatly appreciated!! 

    Kind regards,

    Mervin Graves

    Wednesday, August 21, 2019 1:36 PM


  • Hi merovingian.m,


    We don't have your actual environment or the number of connections to reproduce your problem, so it's hard to come up with useful advice.


    Maybe you can ask professional engineer for help, and they will deal with your problem separately and confidentially.https://support.microsoft.com/en-us/assistedsupportproducts


    Best regards,

    Dedmon Dai

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Marked as answer by merovingian.m Tuesday, September 10, 2019 1:32 PM
    Thursday, August 22, 2019 8:46 AM