Bobcares

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*The maximum is $4000 in credits, Offer valid till November 30th, 2024, New Customers Only, Credit will be applied after purchase and expires after six (6) months

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*The maximum is $4000 in credits, Offer valid till November 30th, 2024, New Customers Only, Credit will be applied after purchase and expires after six (6) months

How to fix SQL server error 15141?

by | Aug 3, 2020

SQL server error 15141 triggers while removing a SQL Server domain login on the instance where AlwaysOn is configured.

As a part of our Server Management Services, we help our Customers to fix SQL related errors regularly.

Let us today discuss the possible causes and fixes for this error.
 

What is SQL server error 15141?

SQL Server Error 15141 triggers when the login to be dropped owns an AlwaysON endpoint. We will be able to remove the login from all databases and server roles, however, we will not be able to delete the login because it owns an endpoint. A typical error message looks like:
 

SQL Server Error 15141

As per the error, one or more endpoints are owned by this login. We can use the below T-SQL code to get the details of endpoint.

SELECT n.name, a.* FROM sys.endpoints a
inner join sys.server_principals n on a.principal_id=n.principal_id
Go

Let us now look into the steps to fix this error message.
 

How to fix SQL server error 15141?

The 15141 error can be fixed by changing the owner of endpoint and then dropping the identified domain login. This breaks the dependency which is the main reason behind the error. We need to change the owner to some other login like the system account sa.

The ALTER Authorization statement can transfer ownership of this endpoint from the existing server-level login to another server-level login. We can not set the ownership to a database-level user. 

Below command can change the owner of the endpoint to a login Domain\test. Please note to replace the login id [Domain\test] with your login.

ALTER Authorization on endpoint::Hadr_endpoint to [Domain\test]
GO

 
After this change, we can drop the login. We can do it by either SQL Server Management Studio or T-SQL. With the SSMS we can perform it by :

1. Connect to target SQL Server Instance.
2. Expand the security folder.
3. Expand the Logins folder.
4. Right-click and choose delete on the identified login which needs to be deleted.
5. Click on the Ok button of the login deletion window.

We can also drop this login with the T-SQL command given below. Please note to change the name of Login_name with your login name which you want to delete.

DROP Login 'LOGIN_NAME'

The login will be dropped successfully this time.

[Need any further assistance in fixing MySQL errors? – We’re available 24*7]
 

Conclusion

In short, SQL server error 15141 triggers while removing a SQL Server domain login. This happens when the login owns an AlwaysON endpoint. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF