Ms Sql 2008 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
Cannot Use The Special Principal Sa Microsoft Sql Error 15405
policies of this site About Us Learn more about Stack Overflow the cannot use the special principal sa user mapping company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Cannot Use The Special Principal 'dbo' Sharepoint
Badges 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 cannot drop the user 'dbo'. 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 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 cannot alter the user 'dbo' 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 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
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Data Access/DataSource Controls - SqlDataSource, ObjectDataSource, etc/Cannot use the special principal 'sa'. (Microsoft SQL Server, Error:... Cannot use the special principal 'sa'. (Microsoft SQL Server,
Login Failed For User Sa
Error: 15405) [Answered]RSS 2 replies Last post Jan 03, 2008 01:11 PM by sp_changedbowner Snowst ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options
Alter Authorization On Database
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 http://stackoverflow.com/questions/4644233/cannot-use-special-principal-dbo-error-15405 into this, because I can't findany posts about it that are helpfull. 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 http://forums.asp.net/t/1199655.aspx?Cannot+use+the+special+principal+sa+Microsoft+SQL+Server+Error+15405+ 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 Points 3430 Posts Re: Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) Jan 02, 2008 10:29 PM|Nai-Dong Jin - MSFT|LINK Hi, From your description, it seems that you are unable to use sa account to log in your sqlserver, right? In managment studio when I go to Security - Logins - and sa properties If I try to add user sa to my Db I get the following errors: If you are going to add a user called ‘sa’, that’s forbidden since it is a built-in account for SQLServer. Generally you can find the sa account in the logins tab of securit
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » Testing Center » SQL Server http://www.sqlservercentral.com/Forums/Topic320530-119-1.aspx Security Skills » 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 cannot use 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 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 cannot use the 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 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