Ms Sql Server Error 15405
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies cannot use the special principal sa user mapping of this site About Us Learn more about Stack Overflow the company cannot use the special principal 'dbo' sharepoint Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges 15405 belt Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute:
Cannot Drop The User 'dbo'.
Sign up Cannot use special principal dbo: Error 15405 up vote 25 down vote favorite 2 I am trying to give all the permissions to a user in the User Mapping section of a database. But, I am encountering this error: "Cannot use special principal dbo" Server roles of the user: sql-server share|improve this question asked Jan 10 '11 at 6:27 Cipher cannot alter the user 'dbo' 2,060164598 1 Not an actual answer to the question posted, but since you're granting db_owner to sarin, why are you even trying to assign any other roles? –Damien_The_Unbeliever Jan 10 '11 at 8:02 This is because I am trying to install a CMs on my website and during the installation process, it says, no User or role 'sarin'. See here: i.imgur.com/Intaa.jpg –Cipher Jan 10 '11 at 9:15 1 The user 'sarin' is already db_owner of the database, there's no need to grant any further permissions. If you're still getting this error, then you're not connecting to the database you think you are, but since you've not shown any screenshots of the actual point where you supply server/db/username, or a connection string, it's a little tricky to diagnose further. –Damien_The_Unbeliever Jan 11 '11 at 9:20 add a comment| 3 Answers 3 active oldest votes up vote 32 down vote accepted This is happening because the user 'sarin' is the actual owner of the database "dbemployee" - as such, they can only have db_owner, and cannot be assigned any further database roles
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20122008 R2200820052000LibraryForums Ask a question Quick access Forums home Browse forums users login failed for user sa FAQ Search related threads Remove From My
Sp_changedbowner
Forums Answered by: Cannot use the special principle 'sa' SQL Server >
Alter Authorization On Database
SQL Server Security Question 0 Sign in to vote Ok, here's my issue... SQL 2005. I have about 12 different http://stackoverflow.com/questions/4644233/cannot-use-special-principal-dbo-error-15405 databases, which about 4 of them are have no user mapped to it. Under the SA login, databases are mapped to the "dbo". The 4 I am having issues with have no user mapped. They are blank. Here is https://social.technet.microsoft.com/Forums/sqlserver/en-US/d5ff5f16-4b79-4405-be42-27d37f2eb67f/cannot-use-the-special-principle-sa?forum=sqlsecurity where I am at... Security>Logins>sa>Login Properties>User Mapping The columns are "Map", "Database", "User", and "Default Schema" Here is an example of the correct Selection Map=checked, Database=eDistribution, User=dbo, Default Schema=dbo Now here is an example of a problem database Map=unchecked, Database=FORMS, User=blank, Default Schema=blank Here is the error when trying to add the "dbo" as a user Any ideas? TITLE: Microsoft SQL Server Management Studio------------------------------ Create failed for User 'sa'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+User&LinkId=20476 ------------------------------ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1406&EvtSrc=MSSQLServer&EvtID=15405&LinkId=20476 ------------------------------BUTTONS: OK------------------------------ TITLE: Microsoft SQL Server Management Studio------------------
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » Testing Center » SQL Server Security Skills » SA Lockout Err 15405 Cannot use special... SA Lockout Err 15405 Cannot http://www.sqlservercentral.com/Forums/Topic320530-119-1.aspx use special principal SA Rate Topic Display Mode Topic Options Author Message E McNeillE McNeill Posted Saturday, November 4, 2006 8:27 PM Forum Newbie Group: General Forum Members Last Login: Monday, June 27, 2016 11:52 AM Points: 7, Visits: 26 Using sql Server 2005Everything was working fine, then I got up one morning and everything was haywire. I am working on a web site and when I try to login in I get the error message Login failed for user 'SA' cannot use because the account is currently locked out.
I went to my SQL Server and was able to log in using my windows authentication.1. My Serveris set up for Sql Server and Windows Authentication mode2. Most of the database permissions for sa were gone. When I tried to adder use SA to any database role I got the error message Cannot use the special Principal SA (Sql Server Error message 15405)3. I logged on to the server as SA and got the same cannot use the results listed above.4. I don’t have a problem any other Sql Server logins permissions in my database – it only seems to be a problem with SA.5. I have tried shutting down the server (Sql Server) and restarting it, but that didn’t fix the problem. As I said before, this all seemed to have happened overnight. I am the only one using this server right now so I can’t figure out how these changes happened.I am using the evaluation copy of Windows Server for Small business Server, Build 3790 with SP1. I have only been using it for 3 weeks so I am a long way from the end of the evaluation period, so I don’t think that is the problem.Do you have an explanation or solution for this problem? Any feedback would be appreciated. Post #320530 Greg Edwards-268690Greg Edwards-268690 Posted Monday, November 6, 2006 6:52 AM Right there with Babe Group: General Forum Members Last Login: Today @ 10:23 AM Points: 799, Visits: 8,121 I assume you have an ID which has admin privileges.In SQL Server Management Studio, go to Security, then Logins.Double click on the sa account to bring up the properties sheet.On the general page, note the check boxes for Enforce password policy and Enforce password expiration. This is new for SQL 2005 - sa can be treated like a Domain User account for password complexity and expiration.The Status page will allow you to unloc