Connection even reached Server? RRS feed

  • Question

  • Hello, I have SQL Server connection auditing enabled for both Successful & Failed login attempts within SQL Server level properties logs.

    One of our App teams is able to connect but frequently drops connections periodically with following error:

    Database driver error...
    Function Name :Connect
    Database Error: Failed to connect to database using user [AppUserName] and connection string [TargetSQLServerName]

    When I checked the SQL Server security log it doesn't even show a Failed login attempt.

    My question is if it doesn't show in above SQL logs does that mean their SQL connection attempt never even reached the Windows Server itself or is it possible it did reach the Windows Server but didn't make it within SQL Server?

    Thanks in advance.

    Thursday, August 22, 2019 6:58 PM

All replies

  • Dear Friend,

    yes, it may not have reached the database. Have you checked the eventviewer?
    Does this tool log into DB or use something like ODBC? Have you checked Firewall yet?

    Jefferson Clyton Pereira da Silva - [MCSA | MCP | MCTS | MTA | Analista de Banco de Dados - Sql Server e Oracle ]

    Thursday, August 22, 2019 9:00 PM
  • Hi,

    This error usually happens when we have a wrong connection string. But as you said that it's happing periodically, this option may not be considered. I'd suggest you to start a SQL Trace for the events "Security Audit" and see if it is shown.


    Thursday, August 22, 2019 9:05 PM
  • It appears that the application produces its own generic message. It would help if you had the full error message from the client API. This can give you more information where things went wrong.

    Erland Sommarskog, SQL Server MVP,

    Thursday, August 22, 2019 9:47 PM
  • The App side is using Informatica.

    Believe it's on the client side driver error as message lists and never even made it to the SQL Server.

    Any idea how to fix this on the client side driver?

    Thanks everyone.

    Sunday, August 25, 2019 6:06 PM
  • Hi,

    A failed login would show in the SQL error log too, but it sounds like this is an app level error.  You should get more detail than that though so it may be possible to get more of an error.

    If its intermittent then you will need verbose logging on the app to get more info really.  If it works sometimes then you know the details can work, so I would assume this is something Informatica related.



    Sunday, August 25, 2019 6:16 PM
  • Hi,

    Was this resolved?



    Saturday, August 31, 2019 11:38 PM
  • Researched around and strongly points to client side driver issue and never even reached targeted Windows server that the SQL Server resides on.

    Would anyone know how to troubleshoot/fix on client side?

    Thanks for everyones replies.

    Tuesday, September 3, 2019 3:03 PM