SQL Server не может использовать специального пользователя «sa». Microsoft SQL Server, ошибка: 15405
Причина ошибки в SQL Server «не удается использовать специального пользователя ‘sa’. Microsoft SQL Server, ошибка: 15405 “
при импорте базы данных в вашем экземпляре SQL вы обнаружите, что не можете использовать служебного пользователя «sa». Microsoft SQL Server, ошибка: 15405 выскакивает при установке пользователя sa в качестве DBO базы данных.
Откройте SQL Management Studio и нажмите кнопку Создать запрос.
Use mydatabase
exec sp_changedbowner ‘sa’,’ true’
Чтобы изменить владельца базы данных, можно использовать команду sp_changedbowner или ALTER AUTHORIZATION
Еще одна причина ошибки в SQL Server «не может использовать специального пользователя ‘sa’. Microsoft SQL Server, ошибка: 15405 “
«Не удалось войти в систему для пользователя ‘testdomain\test’. Причина: проверка доступа к серверу на основе токенов не удалась из-за ошибки инфраструктуры. Проверьте наличие предыдущих ошибок”
Я не мог использовать никакой другой логин, кроме того, который использовался для установки SQL Server.
Еще одно исправление этой ошибки в SQL Server «не может использовать специального пользователя ‘sa’. Microsoft SQL Server, ошибка: 15405 “
1) Войдите на сервер с той же учетной записью, которая использовалась для настройки SQL Sever.
2) Run-GRANT CONTROL SERVER TO “my login » для каждого пользователя, которому вы хотите предоставить права на сервере.
USE [master]
GO
ALTER LOGIN [sa] WITH DEFAULT_DATABASE=[Test], DEFAULT_LANGUAGE=[us_english]
, CHECK_EXPIRATION=OFF, CHECK_POLICY=(ON / OFF), NO CREDENTIAL
GO
USE [master]
GO
ALTER LOGIN [sa] WITH PASSWORD=N’Strongpassword ‘
GO
В графическом интерфейсе SSMS
1. Войдите в систему с помощью проверки подлинности Windows
2. Свойства при подключении
3. Нажмите кнопку безопасность в правом меню и найдите
проверку подлинности SQL Server и Windows,
b. убедитесь, что установлен флажок” сопоставить с учетными данными».
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:
asked Jan 10, 2011 at 6:27
3
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 way for future development, but since this kind of thing tends to be a one off…)
answered Jan 10, 2011 at 8:59
2
Fix: Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405
When importing a database in your SQL instance you would find yourself with Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the database. To fix this,
Open SQL Management Studio and Click New Query. Type:
USE mydatabase
exec sp_changedbowner 'sa', 'true'
Close the new query and after viewing the security of the sa, you will find that that sa is the DBO of the database. (14444)
Source:
http://www.noelpulis.com/fix-cannot-use-the-special-principal-sa-microsoft-sql-server-error-15405/
Harsh Baid
7,2095 gold badges48 silver badges92 bronze badges
answered Jun 26, 2015 at 9:33
ChiakoChiako
7041 gold badge8 silver badges17 bronze badges
2
This answer doesn’t help for SQL databases where SharePoint is connected. db_securityadmin is required for the configuration databases. In order to add db_securityadmin, you will need to change the owner of the database to an administrative account. You can use that account just for dbo roles.
answered Mar 4, 2013 at 19:50
Table of Contents
when importing a database in your SQL instance you would find yourself with Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the database.
To Fix this Error in SQL Server ” Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 “
Open SQL Management Studio and Click New Query. Type:
USE mydatabase
exec sp_changedbowner ‘sa’, ‘true’
To change the owner of the database, you can use sp_changedbowner or ALTER AUTHORIZATION command
Another Cause of Error in SQL Server ” Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 “
“Login failed for user ‘testdomain\test’. 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.
Another Fix this Error in SQL Server ” Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 “
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.
USE [master]
GO
ALTER LOGIN [sa] WITH DEFAULT_DATABASE=[Test], DEFAULT_LANGUAGE=[us_english]
, CHECK_EXPIRATION=OFF, CHECK_POLICY=(ON/OFF), NO CREDENTIAL
GO
USE [master]
GO
ALTER LOGIN [sa] WITH PASSWORD=N’Strongpassword’
GO
In SSMS GUI
1. Login using Windows Authentication
2. Properties at connection
3. Click Security at Right Menu, and find
a SQL Server And Windows Authentication,
b. Make sure “Map to Credential” is checked
When importing a database in your SQL instance you would find yourself with Cannot use the special principal 'sa'. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the database. To fix this,
Open SQL Management Studio and Click New Query. Type:
USE mydatabase
exec sp_changedbowner 'sa', 'true'
Close the new query and after viewing the security of the sa, you will find that that sa is the DBO of the database.
(59564)
Technical help and scripts for everyday issues of a sysadmin day
Create failed for user sa Microsoft SQLserver smo error 15405 can be resolved with this fix by our experts.
At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support Services.
Let’s take a look at how our SQL Server Support Team is ready to help customers with Create failed for user sa error 15405 error.
Create failed for user sa Microsoft SQLserver smo error 15405
As the error message indicates, Error 15405 prevents creating explicit DB users for user sa. Here, sa is the System Administrator, with unlimited permission in SQL Server. Since we do not assign any extra permissions to user sa, resulting in the error 15405 messages.
Fortunately, our SQL Server experts have come up with an easy resolution for this specific issue. It involves ensuring that the user responsible for updating the database has at least dbowner permission on the MS SQL Server or instance.
Additionally, the Create failed for user sa Microsoft SQLserver smo error 15405 error is often a result of a user without sufficient privileges attempting to upgrade the relevant tables in the database.
Furthermore, if we are not sure whether the user currently updating the database has sufficient privileges, we can log in with Windows authentication mode and ensure that sa authentication is enabled in the server to avoid Create failed for user sa error 15405 error.
We can do this by right-clicking the Server in the SQL Server Management Studio and navigating to Properties > Security> and selecting SQL Server and Windows Authentication mode.
Then click OK and enable the sa login with the following steps:
- Head to Security section on your server and then select Logins.
- Then, right-click sa and select Properties.
- Next, head to Status and choose Enabled under Login and click Ok.
After that, restart SQL and we are ready to go. We will no longer come across Create failed for user sa error 15405 error.
[Need assistance with a different issue? We are available 24/7.]
Conclusion
In a nutshell, our skilled SQL Server Support Engineers at Bobcares demonstrated how to resolve Error 15405.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED