SQL Server Error 4060

Why it happens

Error 4060 happens at a very specific point: the login itself passed authentication, so the server knows who you are, but the next step (opening the database named in the connection) failed. The message names the database in quotes, for example Cannot open database "AppDb", which is your fastest clue about what the connection actually asked for.

There are three common reasons the open fails. The database name is wrong or the database does not exist on this server, so there is nothing to open. The database exists but is not ONLINE (it may be OFFLINE, RESTORING, or SUSPECT), so it cannot accept connections. Or the database exists and is online, but the login has no matching database user or CONNECT permission inside it, so the server refuses to let that login in.

This is severity 11, an informational connection error, not a server fault. Note the difference from error 18456: 18456 means the login never authenticated at all (bad password or unknown login), while 4060 means the login was accepted and only the database open step failed.

Examples

Connecting to a database that is OFFLINE or missing

-- The login AppUser is valid, but the target database
-- named in the connection string cannot be opened.
-- Example: the connection asks for AppDb while it is OFFLINE.
ALTER DATABASE AppDb SET OFFLINE;

-- A new connection that requests AppDb now fails to open it.

Cannot open database "AppDb" requested by the login. The login failed.
Login failed for user 'AppUser'.

Login has no user inside the requested database

-- A server login exists, but no matching user was ever
-- created inside AppDb, so the login cannot open it.
CREATE LOGIN AppUser WITH PASSWORD = 'StrongPassw0rd!';

-- Connecting with Initial Catalog = AppDb fails, because
-- AppUser has no user or CONNECT permission in that database.

Cannot open database "AppDb" requested by the login. The login failed.
Login failed for user 'AppUser'.

How to fix it

-- Confirm the database exists and check its state.
SELECT name, state_desc
FROM sys.databases
WHERE name = 'AppDb';

-- If state_desc is OFFLINE, bring it back online.
ALTER DATABASE AppDb SET ONLINE;

USE AppDb;
GO

-- Map the server login to a database user.
CREATE USER [AppUser] FROM LOGIN [AppUser];

-- Grant read access (add db_datawriter too if writes are needed).
ALTER ROLE db_datareader ADD MEMBER [AppUser];

-- Wrong: Initial Catalog points at a database that does not exist.
-- Server=myserver;Initial Catalog=AppDb;User ID=AppUser;Password=...;

-- Right: use the exact, existing database name.
-- Server=myserver;Initial Catalog=ApplicationDb;User ID=AppUser;Password=...;

How to prevent it

Keep connection strings correct and version controlled so every environment points at a real, online database. A single wrong Initial Catalog value is the most common cause of 4060, and it is easy to catch before deployment.

Grant database access as part of deployment. When you provision a login, also create its user in the target database and add the needed roles, so the login can actually open the database it will connect to. Review who can enter each database in the SQL Server security guide.

Common questions