January 26, 2012 at 3:03 am
Hi guys......
I have Windows Authentication but at the time of changing password it porompts the following error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Change password failed for Login 'sa'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1540+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Change+password+Login&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Cannot alter the login 'sa', because it does not exist or you do not have permission. (Microsoft SQL Server, Error: 15151)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=15151&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Also "sa" is disable.
Reply.........thnx
January 26, 2012 at 5:17 am
Why are you trying to change the sa password if you have Windows Authentication?
The sa login is used with SQL Server Authentication.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 26, 2012 at 6:19 am
Hello ,I can guess your problem,
1-First it's not a good idea to using the user sa ,Because it's Build in account:hehe: in sql server
Generally speaking, giving anyone sa access that is not a company employed dba is a bad idea, sorry but it’s even bad for most developers to have it. I’ve supported many vendors and 20 – 30 percent ask for sa access. Out of those I’ve only found 3 who actually needed the sa access. Most times they are too lazy to define exacly what they need. Sql server security is very flexible. of course, make sure the application is not running under an sa access account.
😀 At any way===============>show below
In order for the Enable system administrator (SA) user name check box to be enabled, the following must be true.
The Access project must be connected to a SQL Server 7.0 (or later) database or a Microsoft SQL Server 2000 Desktop Engine.
The SQL Server database must be running on a Windows Server platform.
The SQL Server must be running on the same computer as the Access project.
The current Windows user must be an Administrator for the computer.
The current SQL Server user must be a member of the System Administrator role.
SECURITY Avoid using the built-in system administrator (sa) logon account. Instead, make system administrators members of the sysadmin fixed server role, and have them use their own accounts to log on. Use sa only when there is no other way to log on. To prevent unauthorized access through the sa logon account, you should assign that account a strong, unique password.
After changing the security mode, you can change the SA password by using the Set Login Password command (on the Tools menu, point to Security).
January 26, 2012 at 6:34 am
January 26, 2012 at 6:57 am
First of all, I would also recommend you to use ‘sa’ for admin tasks only. And it should be shared with minimum people (involved in DBA activities).
How to: Change Server Authentication Mode
January 26, 2012 at 7:43 am
check this.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply