Cannot Use The Principal Sa 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 of this site About Us Learn more about Stack Overflow the company Business Learn cannot use the special principal 'dbo' sharepoint more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags cannot use the special principal sa user mapping Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you,
Cannot Drop The User 'dbo'.
helping each other. Join them; it only takes a minute: 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
Microsoft Sql Server Management Studio Error 15405
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 2,055164597 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 cannot alter the user 'dbo' 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. Nor do they need to be. If they're the DB owner, they already have permission to do anything they want to within this database. (To see the owner of the database, open the properties of the database. The Owner is listed on the general tab). To change the owner of the database, you can use sp_changedbowner or ALTER AUTHORIZATION (the latter being apparently the preferred way for future development, but since this kind of thing tends to be a one off...) share|improve this answe
would find yourself with Cannot use the special principal
Login Failed For User Sa
'sa'. Microsoft SQL Server, Error: 15405 popping out when sp_changedbowner setting the sa user as the DBO of the database. To fix this, Open alter authorization on database SQL Management Studio and Click New Query. Type: USE mydatabase
exec sp_changedbowner 'sa', 'true' Close the new query and after viewing the http://stackoverflow.com/questions/4644233/cannot-use-special-principal-dbo-error-15405 security of the sa, you will find that that sa is the DBO of the database. (24093) import databasesecurity Post navigation Previous PostHow to: Clean User's Active Directory Schema from previous Lync installationNext PostFix: Cannot open your default e-mail folders in Outlook Categories Azure Cisco Exchange Hyper-V http://www.noelpulis.com/fix-cannot-use-the-special-principal-sa-microsoft-sql-server-error-15405/ Lync Server MAC Microsoft Network Office 365 OpenText eDocs Outlook Powershell Smartphones SQL Tools Uncategorized VBScript VMWare Windows Yosemite Backup Tag Cloudactive directory antispam azcopy azure backup blacklist blocklist browser cannot open cisco cloud configuration connector domain controller error esxi exchange exchange 2007 exchange 2010 firefox fix free gpo import installation lync lync deployment mailflow migration modification netlogon office 365 office 2003 outlook powershell printer pst public folders router schema sql switch timeout usb wireless device Technical help and scripts for everyday issues of a sysadmin day Recent Posts How to export mailboxes to PST in Exchange 2010 How to: Setup Import Export role in Office 365 Fix: AzCopy.exe Could not finish the operation within specified timeout Fix: Azure RemoteApp GPO login scripts not working Fix: Azure AD Connect unexpected error on sign in Proudly powered by WordPress
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » Testing Center » SQL Server Security Skills http://www.sqlservercentral.com/Forums/Topic320530-119-1.aspx » SA Lockout Err 15405 Cannot use special... SA Lockout Err 15405 Cannot 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 cannot use 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' 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 cannot use the 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 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 Bab