Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Error: 18456, Severity: 14, State: 16.

Author  Topic 

Starting Member

6 Posts

Posted - 2008-09-16 : 05:43:49

Since morning I have observed the following errors in sql 2005 error logs

Error: 18456, Severity: 14, State: 16.
Login failed for user 'sa'. [CLIENT: XXX.XXX.XX.XXX]

(where XXX represents Ip address of client machine)

After that the client machines are not getting connected to sql server. Actually I have 2 applications connected to the same sql server. One is working perfectly fine while the other is not able to connect. Both the applications are connected through sa.

Can someone please help me to solve this issue.

Note : SQL Server version is SQL Server 2005 standard Edition with SP2

Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-09-16 : 05:50:26
Is one of the clients using the wrong password for sa account?

E 12°55'05.63"
N 56°04'39.26"
Go to Top of Page

Aged Yak Warrior

616 Posts

Posted - 2008-09-16 : 09:20:04
The error state of 16 means "The incoming user does not have permissions to log into the target database"

- the user specified a database that they don't have permission to (unlikely with SA).
- you've specified a database that doesn't exist (maybe you misspelled the database's name).
- the target database is in single-user mode.

I find the error state very helpful in trouble-shooting "Login failed" issues

Go to Top of Page

Starting Member

6 Posts

Posted - 2008-09-17 : 05:43:04
Hi ,

Thanks for your reply..

I have checked all the possibility. ie the user access, database existance, muti-user mode. Everything is proper.

The fun out here is that I am able to connect the application with sql server 2000 with same credentials; just a change in ip address of the database server. It's working perfect in sql server 2000 ...

Can you please assist me in finding a solution for the same.

Thanks once again..
Go to Top of Page

Aged Yak Warrior

616 Posts

Posted - 2008-09-17 : 08:58:44
Can you post the two connection strings - remove any sensitive information.

Also , try connecting to the 2005 server with
1. sqlcmd -S<ServerName> -Usa -P<password>
2. sqlcmd -S<ServerName> -Usa -P<password> -d<DatabaseName>
Do this statements succeed? If not, please post the error message.

Can anyone else connect to the server?

Go to Top of Page

Aged Yak Warrior

771 Posts

Posted - 2008-09-17 : 13:08:05
For the interested:
Go to Top of Page

Master Smack Fu Yak Hacker

4507 Posts

Posted - 2008-09-17 : 16:26:16

Gail Shaw
SQL Server MVP
Go to Top of Page

- Advertisement -