Mssql 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 cannot use the special principal sa user mapping Question 0 Sign in to vote Hello all,I'm having a problem with cannot use the special principal 'dbo' sharepoint my sa account, we just migrated from sql server 2000 to sql server 2005 and 1 of our 15405 belt production applications is failing on the sa login. I checked the 'User Map' setup to the 'sa' account and the databases that need accessing aren't mapped.When I try to add the cannot drop the user 'dbo'. map, I get error "Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 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
Cannot Alter The User 'dbo'
PM Reply | Quote Answers 9 Sign in to vote I found the solution!! Quit simple: exec sp_changedbowner 'sa','true'. Thanks anyway Friday, 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
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 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c2dc1237-5a33-48f8-9c11-e2c51424b198/sa-user-map-error?forum=sqlsecurity security of the sa, you will find that that sa is the DBO of the database. (24374) 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 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 http://forums.asp.net/t/1199655.aspx?Cannot+use+the+special+principal+sa+Microsoft+SQL+Server+Error+15405+ Jan 03, 2008 01:11 PM by Snowst ‹ Previous Thread|Next Thread › Print Share Twitter https://berbagisolusi.wordpress.com/2011/12/07/cannot-use-the-special-principal-sa-error-15405-mssql-server/ Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved 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. I just updated cannot use 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'. cannot use the (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 security node. And you may right click on the sa account, choose “Properties”, and then switch to the ‘Status’ tab, please make sure that you have enabled the login of that account. Thanks. Please mark the replies as answers if they help or unmark if not.Feedba
15405) MsSQLServer Posted by berbagisolusi ⋅ December 7, 2011 ⋅ Leave a comment Filed Under Error: 15405, sa, sqlserver Cannot use the special principal ‘sa'. Microsoft SQL Server, Error: 15405 ERROR: Cannot use the special principal ‘sa'. Microsoft SQL Server, Error: 15405 SOLUTION: run this command in the query editor window for each database exec sp_changedbowner 'sa','true' _____________________________________________________________ I Have this issue running SQL Server 2008 and this message was in the log: "Login failed for user ‘CENTRAL\operacao'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors" I could not use any other login except by the login that was used to install SQL Server. So the solution was: 1) Login in the server with the same account used to setup SQL Sever. 2) Run -- GRANT CONTROL SERVER TO "my login" for each user that you want to grant rights in the server. This worked for me. ___________________________________________________________________ USE [master] GO ALTER LOGIN [sa] WITH DEFAULT_DATABASE=[LIFTest], DEFAULT_LANGUAGE=[us_english] , CHECK_EXPIRATION=OFF, CHECK_POLICY=(ON/OFF), NO CREDENTIAL GO USE [master] GO ALTER LOGIN [sa] WITH PASSWORD=N'JH@46O!IH#NFi349gh' GO You can fix using GUI tools, please login at MSSQL Management Studio, 1. Login using Windows Auth 2. Properties at connection 3. Click Security at Righ Menu, and find a .SQLServer And Windows Auth, b. It’s weird how “Map to Credential” is checked yet there is no credential specified. But that’s what you have to do. also see : http://www.techurbia.com/2009/03/cannot-set-a-credential-for-principal-sa-sql-server-20052008.html Share this:TwitterFacebookLike this:Like Loading... Related About berbagisolusi Berbagi merupakan sebuah bentuk simbol keikhlasan untuk membantu dan menolong, sedangkan solusi adalah cara menyelesaikan masalah. Setiap manusia pasti mengalami masalah, tetapi kita tidak perlu mengalami masalah yang sama jika orang lain pernah mengalami d