Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Login Failure issue

Status
Not open for further replies.
Jun 19, 2002
294
US
I am getting a login failure message:

Login failed for user 'user'. [CLIENT: xxx.xxx.xxx.xx]

Error: 18456, Severity: 14, State: 16

I know this normally means the account does not have permission to the default database however the account is successfully logged in and does have public on master (which is the default db). The failure shows multiple times per second. This is a third party application and the failure is coming from only one server though there are many successful connections from that server.

Any suggestions?
 
When using SQL Server 2005 and up, an error with state 16 means that the user doesn't have rights to the target database.

(Look at the first few comments.)

Something either has a bad config file, or it's looking for a database which doesn't exist, or it doesn't have rights to the database.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Was the application's password changed recently? If so, have everyone using the application, close the application and then re-open it. If you change the password while the application is connected, then it continues to use the old password.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
I am guessing it's an issue with one of the application's config files because as I said I have successful logins coming from the same server that is generating the failed login attempts. The application only uses one account (which makes the troubleshooting a little challenging). The password has not been changed recently and the default db is master which has been up and running with no issues. No permission changes were made and since there are a couple hundred successful connections I am really leaning towards a config issue somewhere.

Thanks for the replies.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top