Ms Sql Server 2005 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 cannot use the special principal sa microsoft sql error 15405 company Business Learn more about hiring developers or posting ads with us Stack Overflow cannot use the special principal sa user mapping Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 cannot use the special principal 'dbo' sharepoint 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 2 I am trying to give
Cannot Drop The User 'dbo'.
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,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 cannot alter the user 'dbo' 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). To change the owner of the database, you can use sp_changedbowner or ALTER AUTHORIZATION (the latter being apparently the preferred
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Data Access/DataSource Controls - SqlDataSource, ObjectDataSource, etc/Cannot use login failed for user sa the special principal 'sa'. (Microsoft SQL Server, Error:... Cannot
Sp_changedbowner
use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) [Answered]RSS 2 replies Last post
Alter Authorization On Database
Jan 03, 2008 01:11 PM by Snowst ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads http://stackoverflow.com/questions/4644233/cannot-use-special-principal-dbo-error-15405 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. I just http://forums.asp.net/t/1199655.aspx?Cannot+use+the+special+principal+sa+Microsoft+SQL+Server+Error+15405+ 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 Jin... All-Star 35464 P
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 use special principal SA Rate Topic http://www.sqlservercentral.com/Forums/Topic320530-119-1.aspx 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 http://zamemon.blogspot.com/2012/02/cannot-use-special-principal-sa.html 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' because the account is currently locked out.
I went to my cannot use 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 results listed above.4. I don’t have a problem any other Sql Server logins permissions cannot use the 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 unlock the account.sa already has implied access, there shouldn't be a need to add it to any roles. sysadmin covers quite a bit.Books Online would be goofrom University of Sindh, Jamshoro, Pakistan. Wednesday, February 1, 2012 Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) Yesterday, I start SQL Server 2005 and try to connect with sa user but was enable to connect with the 'sa' user and got this error:Cannot use the special principal 'sa' (Microsoft SQL Server, Error: 15405)After doing some google, I found out the solution which I am sharing so that others can get all the possible solutions from this article.The titled message mean that your sa user is disabled. To enable it, you have to follow below mentioned steps:1) you have to change the authentication mode: go to Management Studio and open Object Explorer. Connect to your server and right-click on the server name, then select Properties. Go to Security tab and under Server Authentication select "SQL Server and Windows Authentication Mode".2) Also, after you follow the directions above, you will also need to explicitly enable the sa account as well. Go to Security->Logins. Right-click on the "sa" account, select "Properties". In the list on the left, select "Status" and under "Login" on the right, make sure "Enable" is selected.3) exec sp_changedbowner 'sa','true' in query editor after selecting the database whom you want to assign user sa.4) You can also change the password of sa (it's better to change the password).After performing all above mentioned changes, Exit with SQL Management Studio. Restart Sql Service from services.msc.Open Management Studio again and try to login "sa". Hopefully, it works. Enjoy! (Please comment if it work for you). Posted by Zeeshan Ahmad Memon at 8:44:00 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: (Microsoft SQL Server, Cannot use the special principal 'sa', Error: 15405, Error: 15405), special principal 'sa' 2 comments: Anonymous said... Thanks for you help. March 16, 2016 at 8:40 AM amit Jain said... Thanks sir, it is working fine.. March 16, 2016 at 11:38 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Visitors Origin Live Traffic Stats About Me Zeeshan Ahmed Memon View my complete profile Subscribe To Posts Atom Posts Comments Atom Comments Blog Archive ► 2016 (8) ► July (2) ► March (1) ► February (1) ► January (4) ► 2015 (3) ► December (1) ► October (2) ► 2014 (2) ► October (1) ► May (1) ► 2013 (4) ► October (1) ► Septem