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: https://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

  • Anonymous
    April 12, 2010
    The comment has been removed

  • Anonymous
    May 08, 2010
    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..

  • Anonymous
    May 25, 2010
    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: www.sqllion.com/.../transaction-isolation-levels-in-sql-server

  • Anonymous
    October 28, 2014
    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 (Connect()). 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. Thanks MSP

  • Anonymous
    December 18, 2014
    The comment has been removed