Login failed for user '(Null)'

Our QA guy just asked me for some help because he suddenly got the (dreaded)
"Login failed for user '(Null)'" message when connecting to the QA database
from his desktop.
There have been no (known) changes since he last used it a week, or two ago
and I've validated his login, Windows auth, ping from his bot to the DB
server, telnet to server 1433 and a few other things.
His password hasn't changed either.
Not sure what to do?Solved.
Non-domain local account and the password had expired.
Arggg!!! Why didn't Microsoft just say "Can't login", or "No Password", or
something.
"Jay" <nospam@.nospam.org> wrote in message
news:O9Wa$vUMIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Our QA guy just asked me for some help because he suddenly got the
> (dreaded) "Login failed for user '(Null)'" message when connecting to the
> QA database from his desktop.
> There have been no (known) changes since he last used it a week, or two
> ago and I've validated his login, Windows auth, ping from his bot to the
> DB server, telnet to server 1433 and a few other things.
> His password hasn't changed either.
> Not sure what to do?
>

Login failed for user '(Null)'

Our QA guy just asked me for some help because he suddenly got the (dreaded)
"Login failed for user '(Null)'" message when connecting to the QA database
from his desktop.
There have been no (known) changes since he last used it a week, or two ago
and I've validated his login, Windows auth, ping from his bot to the DB
server, telnet to server 1433 and a few other things.
His password hasn't changed either.
Not sure what to do?
Solved.
Non-domain local account and the password had expired.
Arggg!!! Why didn't Microsoft just say "Can't login", or "No Password", or
something.
"Jay" <nospam@.nospam.org> wrote in message
news:O9Wa$vUMIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Our QA guy just asked me for some help because he suddenly got the
> (dreaded) "Login failed for user '(Null)'" message when connecting to the
> QA database from his desktop.
> There have been no (known) changes since he last used it a week, or two
> ago and I've validated his login, Windows auth, ping from his bot to the
> DB server, telnet to server 1433 and a few other things.
> His password hasn't changed either.
> Not sure what to do?
>

Login failed for user '(Null)'

Our QA guy just asked me for some help because he suddenly got the (dreaded)
"Login failed for user '(Null)'" message when connecting to the QA database
from his desktop.
There have been no (known) changes since he last used it a week, or two ago
and I've validated his login, Windows auth, ping from his bot to the DB
server, telnet to server 1433 and a few other things.
His password hasn't changed either.
Not sure what to do?Solved.
Non-domain local account and the password had expired.
Arggg!!! Why didn't Microsoft just say "Can't login", or "No Password", or
something.
"Jay" <nospam@.nospam.org> wrote in message
news:O9Wa$vUMIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Our QA guy just asked me for some help because he suddenly got the
> (dreaded) "Login failed for user '(Null)'" message when connecting to the
> QA database from his desktop.
> There have been no (known) changes since he last used it a week, or two
> ago and I've validated his login, Windows auth, ping from his bot to the
> DB server, telnet to server 1433 and a few other things.
> His password hasn't changed either.
> Not sure what to do?
>

Login error: 18456, Severity: 14, State: 11.

Hi,
we did an clean install of MOSS2007 and SQL2005. Both on different servers.
Everything worked well and suddenly we are getting this error and MOSS2007
stops working. The second message in the error log is: 'Login failed for user
'Domain\user'.
If I put the user in the SysAdmin serverrole they are able to connect.
Strange thing is that this is also happening on our SP2003/SQL2000 servers.
But on these servers it's gone after an short period.
Someone any idea?
--
Robert Hartskeerl, MCTS, MCITPHi Robert
State 11 is "Login is valid, but server access failed." my guess is that the
default database is wrong or you don't have access to it. You could try
logging in as that user and use SQLCMD or osql to change the database you
connect to. sp_defaultdb can be used to change the default database.
John
"Robert Hartskeerl" wrote:
> Hi,
> we did an clean install of MOSS2007 and SQL2005. Both on different servers.
> Everything worked well and suddenly we are getting this error and MOSS2007
> stops working. The second message in the error log is: 'Login failed for user
> 'Domain\user'.
> If I put the user in the SysAdmin serverrole they are able to connect.
> Strange thing is that this is also happening on our SP2003/SQL2000 servers.
> But on these servers it's gone after an short period.
> Someone any idea?
> --
> Robert Hartskeerl, MCTS, MCITP|||Hello, Robert
Maybe one of following will help:
http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Razvan Socol
SQL Server MVP|||Thanks for your response John.
We already solved this with the information on connect.microsoft.com.
We had created extra tcp enpoints for different users. What happens is that
SQL Server removes the public role from TCP-Connect. So while the other
applications that used the non-default endpoints only sa's are able to
connect to the default endpoint.
After adding TCP-Endpoint to the public role we can connect.
Robert Hartskeerl
--
Robert Hartskeerl, MCTS, MCITP
"John Bell" wrote:
> Hi Robert
> State 11 is "Login is valid, but server access failed." my guess is that the
> default database is wrong or you don't have access to it. You could try
> logging in as that user and use SQLCMD or osql to change the database you
> connect to. sp_defaultdb can be used to change the default database.
> John
>
> "Robert Hartskeerl" wrote:
> > Hi,
> >
> > we did an clean install of MOSS2007 and SQL2005. Both on different servers.
> > Everything worked well and suddenly we are getting this error and MOSS2007
> > stops working. The second message in the error log is: 'Login failed for user
> > 'Domain\user'.
> >
> > If I put the user in the SysAdmin serverrole they are able to connect.
> >
> > Strange thing is that this is also happening on our SP2003/SQL2000 servers.
> > But on these servers it's gone after an short period.
> >
> > Someone any idea?
> > --
> > Robert Hartskeerl, MCTS, MCITP