Link to home
Start Free TrialLog in
Avatar of gtrapp
gtrapp

asked on

Login failed for user - Microsoft SQL Server, Error: 4064

Hello,

When I click on properties of a database, users, tables, or any object within SQL Server Management Studio, I get this error:

Cannot show requested dialog.
Cannot open user default database. Login failed.
Login failed for user 'PBTF\bob'. (Microsoft SQL Server, Error: 4064)

The login does exist in the security group. The database is a WSS 3.0 database, with an instance of MICROSOFT##SSEE

In the event log, the event occurs when the error message occurs in SQL Server Management Studio:

The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer.

I ran the following command and there were no errors. It seemed to work, but I tried viewing properties in Management Studio and the error still occurs:

C:\>sqlcmd -E -d master -S THOTH\MICROSOFT##SSEE
1> ALTER LOGIN [PBTF\Group - IT DB Admins] WITH DEFAULT_DATABASE = master
2> go

The error still occurs, any suggestions?

Thanks,

Paul
Avatar of Raja Jegan R
Raja Jegan R
Flag of India image

Try running the script below:

exec sp_defaultdb '[PBTF\Group - IT DB Admins]', 'master'

PS: Run this script from a user having sa rights or securityadmin role..
Avatar of gtrapp
gtrapp

ASKER

Ran the script. It ran successfully. I closed down SQL Server Management Studio and reconnected to the MICROSOFT##SSEE. The 4064 error still occurs.
ASKER CERTIFIED SOLUTION
Avatar of Raja Jegan R
Raja Jegan R
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of gtrapp

ASKER

OK, I think I need to call MS Support. Can't seem to fix the problem.
Avatar of gtrapp

ASKER

rrjegan17 did a good job with the comments, but it did not sovle the problem. I need to call MS for help.
>> Can't seem to fix the problem.

Ok..And if you share the solution which you got from Microsoft once it is resolved, it would be helpful for others who might be visiting this thread later on..