Error 15405 Cannot Use The Special Principal Sa
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
Cannot Use The Special Principal Sa Microsoft Sql Error 15405
Stack Overflow the company Business Learn more about hiring developers or posting ads cannot use the special principal sa microsoft sql server error 15405 with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow cannot use the special principal sa user mapping is a community of 4.7 million programmers, just like you, 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
Cannot Use The Special Principal 'dbo' Sharepoint
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 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
Cannot Drop The User 'dbo'.
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. 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). T
would find yourself with Cannot use the special principal cannot alter the user 'dbo' 'sa'. Microsoft SQL Server, Error: 15405 popping out when
Login Failed For User Sa
setting the sa user as the DBO of the database. To fix this, Open sp_changedbowner 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. (24149) 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
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Data Access/DataSource Controls - SqlDataSource, ObjectDataSource, etc/Cannot http://forums.asp.net/t/1199655.aspx?Cannot+use+the+special+principal+sa+Microsoft+SQL+Server+Error+15405+ use the special principal 'sa'. (Microsoft SQL Server, Error:... Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) [Answered]RSS 2 replies Last post Jan 03, 2008 01:11 PM by Snowst ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved cannot use Threads Support Options Advanced Search Reply Snowst Member 444 Points 204 Posts Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) Dec 31, 2007 03:43 PM|Snowst|LINK Hello All, I'm hoping someone else has run into this, because I can't findany posts about it that are helpfull. cannot use the I just updated our Dev SQL 2005dbto be able to use new 2005 key words with the script: EXEC sp_dbcmptlevel 'myDbName' , 90 This is all well and good until I notice mysa account no longer has a user mapping to my database.In managment studio when I go to Security - Logins - andsa properties If I try to add user sa to my Db I get the following errors: >>>------------------------------------------------------------------------------------------------------------->>> Create failed for User 'sa'. (Microsoft.SqlServer.Smo) Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) <<<-------------------------------------------------------------------------------------------------------------<<< I'm access the SQL Server through a client on my local machine, the Server is set to mixed authentication, actual check box is labeled Sql Server and WIndows Authentication Mode. Hopefully I'm just doing something dumb, which is highly likely since I'm a developer and not a DBA. Thanks in advance Reply Nai-Dong Ji