Login failed. The number of simultaneous users has already reached the limit of %1!s! licenses for this '%2!s!' server. Additional licenses should be obtained and installed or you should upgrade to a full version.%3!s!
Login failed for user '%1!s!'. Reason: Password change failed. The password does not meet Windows policy requirements because ...
Login failed for user '%1!s!'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%2!s! ...
Login failed for user '%1!s!'. Reason: Server is in single user mode. Only one administrator can connect at this time.%2!s! ...
Login failed. The number of simultaneous users already equals the %1!s! registered licenses for this server. To increase ...
Login failed. The number of simultaneous users has already reached the limit of %1!s! licenses for this '%2!s!' server. Additional ...
Login {0} has duplicate security identifier.SQL Server 2005 does not allow duplicate login security identifiers. Remove one ...
Logins cannot be scripted by using a service security ID (SID) from SQL Azure Database to a local instance of SQL Server. ...
Logins that have sysadmin privileges on this instance of SQL Server are administrators on the utility control point. To grant ...
Logins" are server level objects and can not be dropped first since the source and destination are the same server. Dropping ...