Categories: SQL Server

SQL Server Error : 15150, Severity: 16. Cannot %S_MSG the %S_MSG ‘%.*ls’.

SQL Server Error : 15150 Details


SQL Server Error: 15150
Severity: 16
Event Logged or not: No
Description:
Cannot %S_MSG the %S_MSG ‘%.*ls’.
Severity 16 Description:
Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server SQL server error 15150 from Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

For other ways to read and find error log location please our article https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html

Solution for Resolving the Error SQL server 15150

SQL server error 15150 occurs when while updating the login from dbo to some other login due to incorrect ownership of the database.

To fix this issue we need to change the default owner to ‘sa’

Use <database name>
sp changedbowner 'sa'

To resolve this problem, set the default owner to ‘sa’ and then attempt to update the login.

Furthermore, SQL Server’s ‘sa’ account has the special privileges required to handle the database. As a result, the default account  ‘sa’ is administrative.

This account is disabled by default to prevent unauthorized access to the database for windows authentication only enabled on server properties /installation.

This appears to be a pretty simple blog, yet it is a very important one. I notice this problem with my customer every day, therefore I decided to create a blog article about it today.

Here are some other blogs that are relevant to this blog post:

  1. SQL SERVER – Forgot Username’s Password SA
  2. CHANGE THE SA PASSWORD ON THE SQL SERVER Using Management Studio to Login
  3. Login failed for user ‘username’ on SQL SERVER. A trustworthy SQL Server connection is not connected with the user. (Error 18452, Microsoft SQL Server)

SQL Server Error Code for SQL server error 15150 and solution summary


SQL Server Error: 15150
Severity: 16
Event Logged or not: No
Description:
Cannot %S_MSG the %S_MSG ‘%.*ls’.

SQL server error 15150 happens when updating the login from dbo to some other login due to incorrect ownership of the database.

VRB

Recent Posts

sql server detected logical consistency based error

Learn about SQL Server detecting logical consistency based issues and how to resolve them.

5 months ago

sql server error 1222

Learn about SQL Server error 1222 and how to resolve the lock request time out…

5 months ago

Microsoft SQL Server 2022 New Features

Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…

5 months ago

SQL Server Error 1222 lock request time out period exceeded

SQL Server Error 1222 lock request time out period exceeded   Lock request time out…

5 months ago

SQL Server Error : 427, Severity: 20. Could not load the definition for constr

SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…

10 months ago

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

10 months ago

This website uses cookies.