Principle dbo does not exist in Sql Server

Question

While fetching data through a stored procedure in SQL Server I am getting error like

Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.

I am getting this error only for accessing a particular stored procedure, not for all SP's.

possible duplicate of http://stackoverflow.com/questions/13823354/sql-server-principal-dbo-does-not-exist — Cee McSharpface, May 23 '16 at 07:45

Rahul Tripathi · Answer 1 · 2016-05-23T07:36:27.860

10

Give your database a valid owner. Try this:

ALTER AUTHORIZATION 
ON DATABASE::[YourDatabaseName]
TO [LoginUser];

or you can try to set it like

USE [dbname]
GO
sp_changedbowner 'someLogin'

edited May 23 '16 at 07:36

answered May 23 '16 at 07:32

Rahul Tripathi

168,305
31
280
331

How to give login credential – Nimmi May 23 '16 at 07:35
@Nimmi:- `[LoginCredential]` is the user! I will update it. Sorry for the confusion. – Rahul Tripathi May 23 '16 at 07:36

score 2 · Answer 2 · edited Jul 11 '17 at 20:43

2

ALTER AUTHORIZATION ON DATABASE::Example TO sa;

edited Jul 11 '17 at 20:43

Floern

33,559
24
104
119

answered Jan 02 '17 at 01:01

Vishe

3,383
1
24
23

score 0 · Answer 3 · answered Dec 02 '19 at 05:02

Basically SQL Server login is mapped to database user and this mapping is not properly defined for SQL server principals then login will not be sucessfully for that specific user of database on that specific instance and this user is called orphan user. First, check if the orphaned user is mapped or not.

USE <database>
EXEC sp_change_users_login @Action='Report';

if not mapped then, fix the orphaned user.

USE <database>
EXEC sp_change_users_login @Action='update_one', @UserNamePattern='YOURUSERNAME', @LoginName='YOURUSERNAME';

Principle dbo does not exist in Sql Server

3 Answers3