Microsoft Sql Server 2012 Error 15405
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: 'sa' User Map error SQL Server > SQL Server Security Question 0 Sign in to vote Hello cannot use the special principal sa user mapping all,I'm having a problem with my sa account, we just migrated from sql
Cannot Use The Special Principal 'dbo' Sharepoint
server 2000 to sql server 2005 and 1 of our production applications is failing on the sa login. I checked the 15405 belt 'User Map' setup to the 'sa' account and the databases that need accessing aren't mapped.When I try to add the map, I get error "Cannot use the special principal 'sa'. (Microsoft SQL Server, Error:
Cannot Drop The User 'dbo'.
15405)". I get the same error when trying to remove a user map for sa (there are a couple db's already mapped), and I don't remember how I mapped them in the first place, but it certainly isn't working now!Thanks in advance,102020 Wednesday, September 13, 2006 6:20 PM Reply | Quote Answers 9 Sign in to vote I found the solution!! Quit simple: exec sp_changedbowner 'sa','true'. Thanks anyway Friday, cannot alter the user 'dbo' February 16, 2007 7:58 AM Reply | Quote 3 Sign in to vote Hey, I find out how to change it using Management Stadio Express: Right click the database to show properties. then change the owner under files to sa then you can map it under Logins . Thursday, March 15, 2007 8:29 PM Reply | Quote 0 Sign in to vote I have fixed this already, thanks though.The problem was that the db owner was the domain admin and not sa, so I couldn't change the mapping.Thanks,102020 Friday, September 15, 2006 4:10 PM Reply | Quote All replies 0 Sign in to vote What is ther error that you get back and for waht operation do you get it back? Please also check the server error log and copy the relevant errors logged there. ThanksLaurentiu Thursday, September 14, 2006 10:07 PM Reply | Quote Moderator 0 Sign in to vote I have fixed this already, thanks though.The problem was that the db owner was the domain admin and not sa, so I couldn't change the mapping.Thanks,102020 Friday, September 15, 2006 4:10 PM Reply | Quote 0 Sign in to vote Hi, I have the same problem. I am trying to add sa to several databases c
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/Data Access/DataSource Controls - SqlDataSource, ObjectDataSource, etc/Cannot use the special principal
Login Failed For User Sa
'sa'. (Microsoft SQL Server, Error:... Cannot use the special principal
Sp_changedbowner
'sa'. (Microsoft SQL Server, Error: 15405) [Answered]RSS 2 replies Last post Jan 03, 2008 01:11 alter authorization on database PM by Snowst ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Reply Snowst https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c2dc1237-5a33-48f8-9c11-e2c51424b198/sa-user-map-error?forum=sqlsecurity 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 updated our Dev SQL 2005dbto be able to use http://forums.asp.net/t/1199655.aspx?Cannot+use+the+special+principal+sa+Microsoft+SQL+Server+Error+15405+ 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 Points 3430 Posts Re: Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405) Jan 02, 2008 10:2
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 http://www.sqlservercentral.com/Forums/Topic320530-119-1.aspx 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, http://saurabhsinhainblogs.blogspot.com/2013/09/cannot-use-special-principal-dbo.html 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' because the account is currently locked out.
I cannot use 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 results listed above.4. I don’t have a problem any other cannot use the 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 @ 8:18 AM Points: 799, Visits: 8,120 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. sysadnot assigned to user database after UAT refresh. User was having "db_owner" but when I tried to assigning him other roles created for specific purpose we get below error "Cannot use special principal DBO" I tried togive other permissions to user in the User Mapping section of a database. But, I am encountering this error. On investigating I found: This is happening because the user is the actual owner of the database - 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 1. sp_changedbowner 2. Alter Authorization 3. From GUI : goto database properties , and change as below screenshot Changing owner of database to sa , will allow you toassign anyrole toyour user Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest 4 comments: Dinesh Dattatray VisheMay 7, 2014 at 5:54 PMHi Saurabha,Done. but unable to change parameter.Regard,DineshReplyDeleteRepliesSaurabh SinhaMay 13, 2014 at 6:18 AMHi DineshAre you not able to change owner of database ?? it can be some valid user only. Please try to replace it wit sa.If you still face issue , Please mail me error and screen shot @ Saurabh.x.sinha@gmail.comDeleteReplyAnonymousSeptember 24, 2014 at 8:13 AMHello Saurabh,your tips above assisted me with setting up my ASPState session db with user sa in cmd.I had all the other settings updated in MySql Studio but not the actual db properties /File Owner. CheersReplyDeleteRepliesSaurabh SinhaSeptember 24, 2014 at 2:46 PMGood to hear ,it worked for youDeleteReplyAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Total Pageviews Follow by Email Followers Categories Audit (2) Backup Restore (14) Checkdb (3) Column Store Index (3) Configuration (1) Connectivity (3) DAC (5) Data Quality Services (1) DBA Scripts (4) Dead Lock (4) Demo (22) Development (2) Difference Between (13) DMV (2) Double-Take (1) DQS (1) DR (1) ERROR (48) Error Log (2) Firewall (2) High Availability (3) Indexes (9) Interview Questions (5) litespeed (1) Log Shipping (3) Login / User (8) Maintenance (1) Memory (4) Migration (1) Must Read (1) Non SQL (4) OS (3) OS Operation Via SQL (10) Partition (1) Patching (6) PDW (5) Performance Issues (13) Performance Scripts (2) Ports (1) Power Shell (4) Protocols (1) Quick Audit (2) Recovery Model (1) R