SQLServer-DBA.com Links

Subscribe to newsletter

Dba_db2_button

Powered by TypePad
Error 18456 - State 5 - SQL Login Failed

25 March,2013 by Jack Vamvas

The SQL Login Failed Error 18456 error was reported by an application owner

Error: 18456, Severity: 14, State: 5.

How to resolve the 18456 login failed message:

1) Identify the state.  It was state 5  meaning : Invalid User ID

2) The most common reasons are wrong user name or misspelling the user name.

3) Is the application attempting to login using SQL Server authentication rather than Windows Authentication?

4) Is the application mistakenly attempting to logon using the database user name rather than the login name?  Depending on how the DBA set mappings, it is possible the connection string was set up with the database user name rather than login name/

5) Use these queries to identify whether a valid logon exists and database users

 

select * from sys.server_principals
select * from sys.database_principals

 Read More

SQL Server - Error: 18456 – Login failed for user - SQL Server DBA

Diary of a DBA – Num 3 – Corporate Audit , SVC, NonClustered Indexes ,failed logon attempts

SQL Server – How to manage Failed Logon attempts



Author: Jack Vamvas (http://www.sqlserver-dba.com)

******** *******

Subscribe to SQLServer-DBA.com

Latest posts delivered to you daily

Delivered by FeedBurner

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment


sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer