Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am querying a group under a Central Management Server, which results in the following being logged to the SQL Server Error Log.

Error: 18456, Severity: 14, State: 38. Login failed for user
'domain\account'. Reason: Failed to open the explicitly specified
database. [CLIENT: xx.xx.xx.xx]

This error is only appearing on this one particular SQL Server in this group. Running a Profiler Trace on this server and reproducing the login failure brings up the following User Error Message:

Cannot open database "<multiple>" requested by the login. The login failed.

My account belongs to an AD group which is apart of the sysadmin server level role. The AD group's default database is the master database. The SQL Server's Connection Properties, Connect to database: is set to <default>. Which is no different from any of the other SQL Servers in this group.

Any reason why this would occur?

Edit: Apologies I forgot to add that the error appears in the trace once I click New Query and the window opens. Before any querying actually occurs.

share|improve this question
Are you able to connect to that instance directly? – SQLRockstar Aug 23 '12 at 21:14
I can connect to the instance directly successfully. And when executing the query that runs fine as well. The error appears (in trace) when the query window opens. – jsauni Aug 23 '12 at 23:25
Try removing the server registration and re-add it? – Jon Seigel Aug 24 '12 at 1:56
So, the query window opens...are you able to query that server from that window, despite the error message appearing in a trace? – SQLRockstar Aug 24 '12 at 2:35
@JonSeigel Removed and re-added the server, error still appears. – jsauni Aug 24 '12 at 2:57

I have seen this issue when the default database for your login is set to the wrong database.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.