Cannot open user default database. Login failed.

Question

Post reply

Cannot open user default database. Login failed.

forum member

Ten Centuries

Points: 1290
More actions
December 6, 2009 at 12:31 am

#213166

All of a sudden i got this error while working please help on how to resolve this
TITLE: Connect to Server
------------------------------
Cannot connect to server
Cannot open user default database. Login failed.
Login failed for user (Microsoft SQL Server, Error: 4064)
Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

luckysql.kinda SSCertifiable Points: 7816 More actions · Answer 1

Server is set on Windows or mixed authentication? Is this user is an admin of this m\c?

Adi Cohn-120898 SSC-Dedicated Points: 33944 More actions · Answer 2

Change the user's default database to a database that exists on the server and is online.

Adi

--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Tom Schuettke SSCarpal Tunnel Points: 4127 More actions · Answer 3

This can happen if your default database is deleted or off-line. Reset it to a database that exists.

wodom Hall of Fame Points: 3813 More actions · Answer 4

I ran across this post because I had a similar problem. Over the weekend an SQL login (Windows authentication) that had been working for months, suddenly quit working. I have SQL actually authenticating on the Windows group, not the individual login.

This is SQL Server 2000 running on Windows Server 2003, by the way.

All the normal measures wouldn't work. Even when I put the username into the Administrators group in Windows, it wouldn't give access (the only improvement was that now the Enterprise Manager could tell whether or not the server was running, and the green arrow showed up). I messed around with individual database permissions, etc., all to no avail.

I specified the individual Windows username instead of the group, and SQL Server said that username didn't exist. That was the clue that convinced me to delete the username from the actual Windows server, and re-add it (also re-inserting it into the appropriate Windows group). Suddenly everything worked.