SQL Server Errors or Failures from Error: 15175 to Error: 15199
Error: 15175, Severity: 16, Login ‘%s’ is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login.
Error: 15176, Severity: 16, The only valid @parameter value is ‘WITH_LOG’.
Error: 15177, Severity: 16, Usage: sp_dropmessage [, | ‘ALL’]
Error: 15178, Severity: 16, Cannot drop a message with an ID less than 50,000.
Error: 15179, Severity: 16, The message number %u or specified language version does not exist.
Error: 15182, Severity: 16, Cannot disable access to the guest user in master or tempdb.
Error: 15183, Severity: 16, The database principal owns objects in the database and cannot be dropped.
Error: 15184, Severity: 16, The database principal owns data types in the database and cannot be dropped.
Error: 15185, Severity: 16, There is no remote user ‘%s’ mapped to local user ‘%s’ from the remote server ‘%s’.
Error: 15186, Severity: 16, The server principal is set as the execution context of a trigger or event notification and cannot be dropped.
Error: 15187, Severity: 10, The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s).
Error: 15188, Severity: 16, Cannot create an index that does not include all security columns.
Error: 15189, Severity: 16, Cannot have more than one security column for a table.
Error: 15190, Severity: 16, There are still remote logins or linked logins for the server ‘%s’.
Error: 15192, Severity: 16, Cannot alter or drop the security column of a table.
Error: 15195, Severity: 16, The MUST_CHANGE option is not supported by this version of Microsoft Windows.
Error: 15196, Severity: 16, The current security context is non-revertible. The “Revert” statement failed.
Error: 15197, Severity: 16, There is no text for object ‘%s’.
Error: 15198, Severity: 16, The name supplied (%s) is not a user, role, or aliased login.
Error: 15199, Severity: 16, The current security context cannot be reverted. Please switch to the original database where ‘%ls’ was called and try it again.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.