Setuser failed because of one of the following reasons: the database principal ‘%.*ls’ does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permissi

Error Message:
Msg 15157, Level 16, State 1, Line 1
Setuser failed because of one of the following reasons: the database principal ‘%.*ls’ does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

Severity level:
16.

Description:
This error message appears when you try to use SETUSER with an unknown user.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Errors of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. The user you want to use with SETUSER must be known prior to execution to SQL Server.

Versions:
All versions of SQL Server.

Example(s):
SETUSER ‘abc’
GO
SETUSER

Remarks:
In the above example we try to use SETUSER with the user ‘abc’. Because this user is not known to the system, the error is raised.




Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |