SQL Server "Login Failure" troubleshooter

Our colleagues over in the SQL Server Security team have developed an open tool for troubleshooting "Login Failure" errors. If you're having an issue with "Login Failure" errors and can't resolve it from the other SQL Protocols blog articles here, check out their blog post and give their tool a try: http://blogs.msdn.com/sqlsecurity/archive/2010/03/29/sql-server-authentication-troubleshooter.aspx


Dan Benediktson
SQL Server Protocols

Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights

Comments (5)

  1. Toby Hensley says:

    I get the following message:

    CCon: open connection on Line 0

    Error (-2147467259) Named Pipes Provider

    Could not open a Connection on Sql Server [2]


  2. Dave Briggs says:

    I got this message when updating ACT by Sage database

    HResult 0x15, Level 16, State 1

    Encryption not supported on the client.

    Sqlcmd: Error: Microsoft SQL Native Client : Client unable to establish connection.

    Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..

  3. SQL Lion says:

    To get more information about Isolation levels in SQL Server including Locks and its impact on database in detail with examples, refer the below link:


  4. atbeat says:

    I have functioning SQL based database, whose server portion of the database program is on server and there are two client parts that are working well. I recently added a 2 new client computers using windows 7 Professional and on one of these two the program is working fine but on the other workstation, I am experiencing difficulty and following error comes on login,

    Connection failed

    SQLState: '01000'

    SQL Server Error: 3

    [Microsoft][ODBC SQL Driver][DBNETLIB]ConnectionOpen


    Connection failed

    SQLState: '08001'

    SQL Server Error: 17

    [Microsoft][ODBC SQL Driver][DBNETLIB]SQL Server does not exist or access denied.

    I would appreciate if someone could help with this error and how to solve.



  5. Steve says:

    I tried using the troubleshooter tool on a SQLEpress 2014 server and got the following message:

    Hello, Meredith! I am so happy to assist you!



    Trying to open connection to the server "meredith-pcsqlexpress"…

    Connection to server "meredith-pcsqlexpress" was successfully established!

    Setting up XEvent session for server "meredith-pcsqlexpress"…

    [SqlException]: The event action name, "sqlserver.database_context", is invalid, or the object could not be found

Skip to main content