Skip to content

Logins & Permissions errors

Failed logins, databases a login cannot open, and permission denied errors on objects, statements and server actions.

18456 Login failed for userAuthentication failed; the state number reveals the real reason. 4060 Cannot open database requested by the loginThe requested database is missing, offline or off-limits to the login. 4064 Cannot open user default databaseThe login default database cannot be opened, so the connection fails. 229 The permission was denied on the objectThe user lacks SELECT, EXECUTE or another object-level permission. 262 Permission denied, unable to run a statementThe user cannot run CREATE, ALTER or another statement-level command. 15247 User does not have permission to perform this actionA security statement such as CREATE USER, CREATE ROLE or CREATE SCHEMA needs a permission the user lacks. 18452 Login failed: the login is from an untrusted domainWindows credentials could not be validated: untrusted domain, SPN or Kerberos/NTLM failure. 916 The server principal is not able to access the database under the current security contextThe login or impersonated user has no user (and no guest access) in the target database. 300 Permission was denied on object (for example VIEW SERVER STATE)A login lacks VIEW SERVER STATE or another permission a DMV or tool checks. 15023 User, group or role already exists in the current databaseThe user or role name is taken, often by an orphaned user after a restore. 15138 The database principal owns a schema and cannot be droppedDROP USER or DROP ROLE fails because the principal still owns a schema; transfer it with ALTER AUTHORIZATION. 15151 Cannot find the login or user because it does not exist or you do not have permissionA user, login, role or schema name was not found in this scope, or the caller lacks permission to change it. 15434 Could not drop login as the user is currently logged inDROP LOGIN is refused while any session (including pooled connections) uses the login. 18461 Login failed: server is in single user modeThe instance was started with -m and its only connection is already taken. 18470 Login failed: the account is disabledThe password was correct but the login is disabled. 18486 Login failed because the account is currently locked outA SQL login was locked by the Windows lockout policy after too many wrong passwords. 18487 Login failed: the password of the account has expiredA SQL login with CHECK_EXPIRATION has a password older than the maximum password age. 18488 Login failed: the password of the account must be changedThe login is flagged MUST_CHANGE and must set a new password before it can connect. 17809 Could not connect because the maximum number of user connections has been reachedA new connection was refused because the instance holds as many user connections as it allows; look for connection leaks first.
No errors in this category match your search. Search the whole library.

Other categories