Не удалось получить сведения о пользователе или группе windows nt код ошибки 0x534

А что делать есть в сообщении указан не текущий логин, а старое имя компьютера? Как сказать SQL-серверу, что у меня новое имя компьютера? Вроде бы воспользовался командой

T-SQL

1	ALTER AUTHORIZATION ON DATABASE::[mydbname] TO [DOMAIN\user]

, где [mydbname] – имя базы данных, DOMAIN и user – имя ПК и пользователя соответственно, а ошибка всё равно сохранилась, а владелец не изменился (при том, что SQL запрос прошёл успешно)

Добавлено через 23 минуты
Удалось получить доступ, переименовав имя для входа в «безопасность, имена для входа». Не думал, что это как-то исправит ошибку

Источник

Добрый день, коллеги! Помогите с проблемой — не получается выполнить план обслуживания SQL server 2019. Ошибка внутри Агента

Сообщение
[298] Ошибка SQLServer: 15404, Не удалось получить сведения о пользователе или группе Windows NT «DOMEN\Julia», код ошибки: 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

Подскажите что не так…

Последнее редактирование: 20.09.2021

Еще вижу пару ошибок, не ясно относится это к делу или нет

Дата 20.09.2021 11:35:22
Журнал Агент SQL Server (Текущий — 20.09.2021 11:35:00)
Сообщение
[408] SQL Server MSSQLSERVER является кластеризованным сервером — возможность автозапуска (AutoRestart) отключена

Дата 20.09.2021 11:35:22
Журнал Агент SQL Server (Текущий — 20.09.2021 11:35:00)

Сообщение
[396] Не определено условие простоя процессора — расписания заданий типа OnIdle использоваться не будут

Попробуйте использовать SA а не «DOMEN\Julia

Можно попробовать пересоздать план обслуживания

Попробуйте использовать SA а не «DOMEN\Julia

А где это делать ??

Создала план обслуживания заново, заработало)

Как я понял, это происходит из-за изменения названия домена или имени ПК (при этом изменяется имя сервера). А у пользователя остаётся предыдущее имя. Например, у вас было имя «DOMEN\Julia», соответственно имя сервера «DOMEN». Вы меняете имя компьютера на другое, имя сервера тоже меняется на «дргуое», а ваше имя остаётся «DOMEN\Julia», вместо «другое\Julia». Точнее, оно меняется, но при создании объектов в поле «владелец» записывается старое имя, которое уже не проходит проверку безопасности.

Вот что у меня сейчас и вот что показывает, когда создаю новую БД:

Помогло изменение владельца на sa.

Источник

I have a Windows 2012 Server running SharePoint 2010 using an SQL Server Express locally installed. Unfortunately my logs are currently flooding with message «An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user ‘DOMAIN\user’, error code 0x5.» It can be 20 such messages every second!

(…and the ‘DOMAIN\user’ happens to be my personal account.)

Are there a job running that has missing rights? «Qoute from https://serverfault.com/questions/277551/mssqlserver-exception-occurred-while-enqueueing-a-message-in-the-target-queue-e «Try to changing the owner of the jobs to the sa account, on the properties of the job.» If I’m correct the express version of SQL server cannot run jobs? Or is there someone/something that wants access to our AD? Why do that account wants to obtain information about my account 20 times every second?

I do find lot’s of blogs and hints about this task, but I just dont understand the solutions. One says «To repair this, login as one of the SA accounts and grant SA access for the account that needs it.» But what account needs sa access?

asked Sep 15, 2014 at 10:22

Change the owner to sa. Here are the steps I took to solve this issue:

Right-Click on the database and select properties
Click on Files under the Select a page
Under the Owner, but just below the Database Name on the right-hand pane, select sa as the owner.

ΩmegaMan

29.6k12 gold badges100 silver badges123 bronze badges

answered Aug 21, 2017 at 10:09

olasammyolasammy

6,7364 gold badges26 silver badges32 bronze badges

In my case, sa was not the owner of the DB, I was. When I tried to execute CLR configuration that required sa privileges, I got the error too.

The solution:

USE MyDB 
GO 
ALTER DATABASE MyDB set TRUSTWORTHY ON; 
GO 
EXEC dbo.sp_changedbowner @loginame = N'sa', @map = false 
GO 
sp_configure 'show advanced options', 1; 
GO 
RECONFIGURE; 
GO 
sp_configure 'clr enabled', 1; 
GO 
RECONFIGURE; 
GO

I used help from the db team at work and this post to find the answer.

starball

22.1k8 gold badges47 silver badges286 bronze badges

answered Nov 17, 2014 at 21:46

Chaim EliyahChaim Eliyah

2,7734 gold badges24 silver badges37 bronze badges

In my case the owner of the database was a domain account Domain\Me.

The error message was

Error: 15404, State: 19. Could not obtain information about Windows NT
group/user ‘Domain\MyAccount’

The problem was that the database didn’t know what to do with the domain account — so the logical thing to do was to use a local account instead.

I tried changing the owner of the database, but things still wouldn’t work correctly.

In the end I dropped and recreated the entire database MAKING SURE THAT THE OWNER WAS SA

I also set the Broker to Enabled in the settings

Thing started magically working after this

answered May 6, 2015 at 11:38

No Domain Authentication

Failure was ultimately due to the fact that it was not able to authenticate when I was not vpn-ed into the corporate network.

For I was connecting to a local db on my work laptop, however the User ‘DOMAIN\user’ needed to be authenticated by AD on the corporate network.

Error was resolved as soon as I reconnected and refreshed; the error disappeared.

ΩmegaMan

29.6k12 gold badges100 silver badges123 bronze badges

answered Jun 26, 2020 at 7:59

Ameet BhatAmeet Bhat

911 silver badge1 bronze badge

to do a bulk update for all databases, run this script and then execute its output:

 SELECT 'ALTER AUTHORIZATION ON DATABASE::' + QUOTENAME(name) + ' TO [sa];' 
 from sys.databases
     where name not in ('master', 'model', 'tempdb')

answered Mar 26, 2018 at 17:05

avs099avs099

11k6 gold badges60 silver badges110 bronze badges

I had this error from a scheduled job in sql Server Agent, in my case, just after I changed the hostname of the Windows Server. I had also ran sp_dropserver and sp_addserver. My database was owned by «sa», not a Windows user.

I could login into SQL as the Windows user NEWHOSTNAME\username (I guess after a hostname change, the SID doesn’t change, that’s why it worked automatically?).

However, in SQL, in Security/Logins node, I had SQL logins defined as OLDHOSTNAME\username. I connected to SQL using «sa» instead of Windows Integrated, dropped the old logins, and create new ones with NEWHOSTNAME\username.

The error disappeared.

answered Jan 11, 2016 at 14:26

Thierry_SThierry_S

1,5361 gold badge16 silver badges25 bronze badges

I was having the same problem. In my case it was due to the fact that my machine was part of a domain, but I was not connected to the company VPN. The problem was solved after connecting to the VPN (so the domain user could be resolved by the SQLAgent).

answered Mar 1, 2021 at 13:41

erionpcerionpc

3783 silver badges16 bronze badges

I had the same issue where my domain login was not being recognized. All I did was go into the SQL Server configuration manager and start the services as Network Services instead of a local service. The sql server / agent was then able to recognize the AD logins for the jobs.

answered Jun 14, 2019 at 12:42

HaliHali

413 bronze badges

In my case, it was VPN issue. When I turned on the VPN to connect with my office network & then tried to start the snapshot agent again, it started successfully.

answered Oct 29, 2019 at 18:37

Ankush JainAnkush Jain

5,6944 gold badges32 silver badges57 bronze badges

I was facing the same issue.
Fix for me was changing the log-on from NT User to global user in Sql Server Configuration Manager => Sql Server Service => Sql Server Agent => Properties => Account name.

answered Apr 4, 2020 at 9:10

Jitan GuptaJitan Gupta

4646 silver badges18 bronze badges

You should be connected with your domain. (VPN)

answered Feb 8, 2022 at 8:53

WouterWouter

2,56019 silver badges31 bronze badges

Источник

(…and the ‘DOMAIN\user’ happens to be my personal account.)

asked Sep 15, 2014 at 10:22

Change the owner to sa. Here are the steps I took to solve this issue:

Right-Click on the database and select properties
Click on Files under the Select a page
Under the Owner, but just below the Database Name on the right-hand pane, select sa as the owner.

ΩmegaMan

29.6k12 gold badges100 silver badges123 bronze badges

answered Aug 21, 2017 at 10:09

olasammyolasammy

6,7364 gold badges26 silver badges32 bronze badges

In my case, sa was not the owner of the DB, I was. When I tried to execute CLR configuration that required sa privileges, I got the error too.

The solution:

USE MyDB 
GO 
ALTER DATABASE MyDB set TRUSTWORTHY ON; 
GO 
EXEC dbo.sp_changedbowner @loginame = N'sa', @map = false 
GO 
sp_configure 'show advanced options', 1; 
GO 
RECONFIGURE; 
GO 
sp_configure 'clr enabled', 1; 
GO 
RECONFIGURE; 
GO

I used help from the db team at work and this post to find the answer.

starball

22.1k8 gold badges47 silver badges286 bronze badges

answered Nov 17, 2014 at 21:46

Chaim EliyahChaim Eliyah

2,7734 gold badges24 silver badges37 bronze badges

In my case the owner of the database was a domain account Domain\Me.

The error message was

Error: 15404, State: 19. Could not obtain information about Windows NT
group/user ‘Domain\MyAccount’

The problem was that the database didn’t know what to do with the domain account — so the logical thing to do was to use a local account instead.

I tried changing the owner of the database, but things still wouldn’t work correctly.

In the end I dropped and recreated the entire database MAKING SURE THAT THE OWNER WAS SA

I also set the Broker to Enabled in the settings

Thing started magically working after this

answered May 6, 2015 at 11:38

No Domain Authentication

Failure was ultimately due to the fact that it was not able to authenticate when I was not vpn-ed into the corporate network.

For I was connecting to a local db on my work laptop, however the User ‘DOMAIN\user’ needed to be authenticated by AD on the corporate network.

Error was resolved as soon as I reconnected and refreshed; the error disappeared.

ΩmegaMan

29.6k12 gold badges100 silver badges123 bronze badges

answered Jun 26, 2020 at 7:59

Ameet BhatAmeet Bhat

911 silver badge1 bronze badge

to do a bulk update for all databases, run this script and then execute its output:

 SELECT 'ALTER AUTHORIZATION ON DATABASE::' + QUOTENAME(name) + ' TO [sa];' 
 from sys.databases
     where name not in ('master', 'model', 'tempdb')

answered Mar 26, 2018 at 17:05

avs099avs099

11k6 gold badges60 silver badges110 bronze badges

I could login into SQL as the Windows user NEWHOSTNAME\username (I guess after a hostname change, the SID doesn’t change, that’s why it worked automatically?).

The error disappeared.

answered Jan 11, 2016 at 14:26

Thierry_SThierry_S

1,5361 gold badge16 silver badges25 bronze badges

answered Mar 1, 2021 at 13:41

erionpcerionpc

3783 silver badges16 bronze badges

answered Jun 14, 2019 at 12:42

HaliHali

413 bronze badges

In my case, it was VPN issue. When I turned on the VPN to connect with my office network & then tried to start the snapshot agent again, it started successfully.

answered Oct 29, 2019 at 18:37

Ankush JainAnkush Jain

5,6944 gold badges32 silver badges57 bronze badges

answered Apr 4, 2020 at 9:10

Jitan GuptaJitan Gupta

4646 silver badges18 bronze badges

You should be connected with your domain. (VPN)

answered Feb 8, 2022 at 8:53

WouterWouter

2,56019 silver badges31 bronze badges

Источник

Содержание

MSSQLSERVER_15404
Сведения
Объяснение
Действие пользователя
Fixing Maintenance Plan Error code 0x534
Sql server error 15404 error code 0x534
Answered by:
Question
Sql server error 15404 error code 0x534
Answered by:
Question
SQLServer Error 15404 | How-to-fix
How to resolve SQLServer Error 15404
Conclusion
PREVENT YOUR SERVER FROM CRASHING!

MSSQLSERVER_15404

Применимо к: SQL Server (все поддерживаемые версии)

Сведения

attribute	Значение
Название продукта	SQL Server
Идентификатор события	15404
Источник события	MSSQLSERVER
Компонент	SQLEngine
Символическое имя	SEC_NTGRP_ERROR
Текст сообщения	Не удалось получить сведения о пользователе/группе Windows NT «пользователь«, код ошибки код_ошибки.

Объяснение

15404 используется при проверке подлинности, если указан недопустимый участник. Или олицетворение учетной записи Windows не выполняется, так как не существует связи полного уровня доверия между учетной записью SQL Server и учетной записью домена Windows.

Действие пользователя

Убедитесь, что участник Windows существует и его имя указано верно.

Если эта ошибка — результат отсутствия связи полного уровня доверия между учетной записью службы SQL Server и учетной записью домена Windows, то ошибку можно устранить одним из следующих способов.

Используйте для службы SQL Server учетную запись из домена, к которому относится пользователь Windows.

Если SQL Server использует учетную запись компьютера, например Network Service или Local System, то домен, на котором находится пользователь Windows, должен доверенную связь с компьютером.

Источник

Fixing Maintenance Plan Error code 0x534

Have you ever changed Server name on which SQL Server instance is installed? One of my friends changed the hostname of a Windows server with SQL Server already installed. After this, the SQL Server maintenance plan jobs started to fail. As we know, internally SQL Server still shows the old hostname this must be dropped manually. Otherwise your SQL Server maintenance plan jobs fail with this error.

The Job failed: Could not obtain information about Windows NT group/user ‘XXXXXXAdministrator’, error code 0x534. [SQLSTATE 42000] (Error 15404))

In this post, I will show you the procedure to resolve the errors and execute the SQL Server Agent Maintenance Plan jobs successfully. Below is the error screenshot showing job failure in the SQL Server agent logs. The error is highlighted in the image in red.

First, connect to your SQL Server instance with SQL Server Management Studio and run the below queries to check SQL Server name:

In the below screenshot, the server name and machine name are different.

Run the below shown T-SQL scripts to drop the old server name, and then it add back the SERVERNAME to match the operating system’s hostname.

In the below screenshot, first we dropped old server name.

In the below screenshot, we have added new server name using T-SQL.

Now, log into the SQL Server with a “sysadmin” privileged user. Go to SQL Server logins, and you can still see the oldServernameadministrator login bound with the SQL Server engine.

Drop the login “OldServernameadministrator” and create a new windows login as “NewServernameadministrator”, adding the sysadmin Server role.

In the below screenshot, we have added “DB01administrator” login.

The owner of the job associated with maintenance plan is OldServernameadministrator. We need to reset the ownerid using the below T-SQL Update query.

Now, We need to reset the owner of the job associated with the maintenance plan by running the below T-SQL query. In below screenshot, reset the owner of the job.

Right click on SQL Server job and select properties and change the owner of job to “sa” login.

Delete old maintenance plan and re-create the maintenance plan. Right click and click execute maintenance plan. You can see maintenance plan executed successfully. J

Источник

Sql server error 15404 error code 0x534

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==

We recently moved our database server from SQL Server 2000 to SQL Server 2005. All applications on our intranet development server stay the same [VS.NET 2003], but recently resources in our Dev DB server ran out of space. While doing a thorough investigation, I noticed ERRORLOG file was occupying about 35 Gig of HDD space. I immediately checked SQL Server error log and noticed an entry which says –

Date 7/7/2006 4:45:37 PM

Log SQL Server (Current — 7/7/2006 4:45:00 PM)

The activated proc [dbo].[SqlQueryNotificationStoredProcedure-5eaf8465-d0cb-4be7-93b6-44bb979dd41c] running on queue BW_Content.dbo.SqlQueryNotificationService-5eaf8465-d0cb-4be7-93b6-44bb979dd41c output the following: ‘Could not obtain information about Windows NT group/user ‘BWCINCHoffK’, error code 0x534.’

What is this SqlQueryNotificationService in my database? Is it a SQL Server 2005 thing? Why the same kind of stored procedure does not exist in other databases, but BW_Content? This error is getting repeated most probably every second and is filling up our server.

I believe our corporate IT people removed our domain accounts from BWCINC domain to BWCORP domain and probably some application which is using BWCINCHoffK credential is getting errored out. I tried to locate this application and was not successful.

Is there anyway that I can stop this ERRORLOG from growing? How can I delete these log entries so that I can make space on our Hard Drive? Is there an easy way in SQL Server 2005 to locate which application is creating this error?

Источник

Sql server error 15404 error code 0x534

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==

Date 7/7/2006 4:45:37 PM

Log SQL Server (Current — 7/7/2006 4:45:00 PM)

Источник

SQLServer Error 15404 | How-to-fix

by Nikhath K | Apr 3, 2022

SQLServer Error 15404 can be resolved with Bobcares by your side.

At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support.

Let’s take a look at how our Support Team is ready to help customers resolve SQLServer Error 15404.

How to resolve SQLServer Error 15404

SQL server error 15404 occurs due to the specification of an invalid principal. Furthermore, the error may also pop up when the impersonation of a Windows account fails due to no full trust relationship between the domain of the Windows account and the SQL Server service account.

For instance, suppose we run a few high privilege T-SQL statements like sp_addsrvrolemember or Create Login, we may find ourselves facing Error 15404.

In this scenario, we will see notice messages in PALLOG. In case the PALLOG is disabled, we have to enable it manually by creating /var/opt/mssql/logger.ini with the following content:

Let’s take a look at the messages in PALLOG:

As seen above, queries like Create login require checking permissions. The first time this is done, current permission is invalidated. When we repeat it, the permission check is rechecked. Furthermore, during the permission check, the SQL Server will go through the myssql.keytab to find the machine entry key or MSA key

In case the SQL Server cannot find the entries or finds invalid entries, it results in an error.

If we find ourselves facing this particular error, our Support Engineers suggest ensuring the Windows principal exists in addition to not being misspelled. Here are a few more troubleshooting tips courtesy of our Support Team to resolve this issue:

Ensure we use an account from the same Windows user domain for the SQL Server service.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our skilled Support Engineers at Bobcares demonstrated how to fix SQLServer Error 15404.

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.

Источник

The Job failed: Could not obtain information about Windows NT group/user 'XXXXXXAdministrator', error code 0x534. [SQLSTATE 42000] (Error 15404))

First, connect to your SQL Server instance with SQL Server Management Studio and run the below queries to check SQL Server name:

use master
select @@SERVERNAME -- The current hostname SQL Server recorded
select SERVERPROPERTY('machinename') -- The hostname the operating system recorded

In the below screenshot, the server name and machine name are different.

Run the below shown T-SQL scripts to drop the old server name, and then it add back the SERVERNAME to match the operating system’s hostname.

In the below screenshot, first we dropped old server name.

In the below screenshot, we have added new server name using T-SQL.

Now, log into the SQL Server with a “sysadmin” privileged user. Go to SQL Server logins, and you can still see the oldServernameadministrator login bound with the SQL Server engine.

Drop the login “OldServernameadministrator” and create a new windows login as “NewServernameadministrator”, adding the sysadmin Server role.

CREATE LOGIN [NewServernameadministrator] FROM WINDOWS;
GO
EXEC sp_addsrvrolemember N'NewServernameadministrator', N'sysadmin';

In the below screenshot, we have added “DB01administrator” login.

The owner of the job associated with maintenance plan is OldServernameadministrator. We need to reset the ownerid using the below T-SQL Update query.

Now, We need to reset the owner of the job associated with the maintenance plan by running the below T-SQL query. In below screenshot, reset the owner of the job.

Right click on SQL Server job and select properties and change the owner of job to “sa” login.

Delete old maintenance plan and re-create the maintenance plan. Right click and click execute maintenance plan. You can see maintenance plan executed successfully. J

Regards,

Ganapathi varma

Senior SQL Engineer, MCP

Email: Gana20m@gmail.com

== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==

===========================================================================================

Date 7/7/2006 4:45:37 PM

Log SQL Server (Current — 7/7/2006 4:45:00 PM)

Source spid77s

Message

===========================================================================================

Response from Remus:

The ‘SqlQueryNotificationService-…’ is the service created by SqlDependency when you call SqlDependency.Start (). The problem you describe appears because the ‘dbo’ user of the database is mapped to the login that originally created this database. The SqlDependency created queue has an EXECUTE AS OWNER clause, owner is ‘dbo’ and therefore this is equivalent to an EXECUTE AS USER = ‘dbo’. The error you see is reported by the domain controller when asked to give information about the original account ‘dbo’ mapps to (that is, BWCINCHoffK’): Error code: (Win32) 0x534 (1332) — No mapping between account names and security IDs was done.

To find the databases that have this problem, run this query:

select name, suser_sname(owner_sid) from sys.databases

The databses that have the problem will show NULL on the second column.

To remove the entries, use sp_cycle_errorlog to force a new errorlog file, then delete the huge log file.

—————————————

I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.

===============================================================

Date 7/10/2006 1:16:55 PM
Log SQL Server (Current — 7/10/2006 1:17:00 PM)

Source spid20s

Message

The query notification dialog on conversation handle ‘{6BDE95F7-0EFB-DA11-9064-000C2921B41B}.’ closed due to the following error: ‘<?xml version=»1.0″?><Error xmlns=»http://schemas.microsoft.com/SQL/ServiceBroker/Error»><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-c15bb868-ed56-47d2-bf91-ce18b320989a' because it does not exist.</Description></Error>’.

===============================================================

Should I be concerned about this error?

Thanks

-Binoy

== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==

===========================================================================================

Date 7/7/2006 4:45:37 PM

Log SQL Server (Current — 7/7/2006 4:45:00 PM)

Source spid77s

Message

===========================================================================================

Response from Remus:

To find the databases that have this problem, run this query:

select name, suser_sname(owner_sid) from sys.databases

The databses that have the problem will show NULL on the second column.

To remove the entries, use sp_cycle_errorlog to force a new errorlog file, then delete the huge log file.

—————————————

I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.

===============================================================

Date 7/10/2006 1:16:55 PM
Log SQL Server (Current — 7/10/2006 1:17:00 PM)

Source spid20s

Message

===============================================================

Should I be concerned about this error?

Thanks

-Binoy

== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==

===========================================================================================

Date 7/7/2006 4:45:37 PM

Log SQL Server (Current — 7/7/2006 4:45:00 PM)

Source spid77s

Message

===========================================================================================

Response from Remus:

To find the databases that have this problem, run this query:

select name, suser_sname(owner_sid) from sys.databases

The databses that have the problem will show NULL on the second column.

To remove the entries, use sp_cycle_errorlog to force a new errorlog file, then delete the huge log file.

—————————————

I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.

===============================================================

Date 7/10/2006 1:16:55 PM
Log SQL Server (Current — 7/10/2006 1:17:00 PM)

Source spid20s

Message

===============================================================

Should I be concerned about this error?

Thanks

-Binoy

_Лотос_

21.03.2012, 00:23. Показов 13150. Ответов 2

Здравствуйте, я только начал общаться с SQL Server из под VS2010. Создаю свою первую БД. В обозревателе серверов создал новое подключение, создал в нём несколько таблиц и попытался создать схему данных. Этого мне сделать не удалось. Появились 2 сообщения (см. вложения) про отсутствия действующего пользователя. Я 2 раза нажимаю ОК и получаю ошибку 0x534 «Не удаётся получить сведения о пользователе или группе Windows NT «Имя_компаЛогин»». В настройках подключения указано «использовать проверку подлинности Windows» В сообщении об ошибке указан текущий логин с правами администратора.
Подскажите в чём проблема и как её решить?

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь

412 / 263 / 25 Регистрация: 03.10.2011 Сообщений: 1,079
21.03.2012, 01:48	2
1

Титан_1

14 / 14 / 3

Регистрация: 24.05.2014

Сообщений: 1,001

06.06.2021, 14:02

T-SQL

1	ALTER AUTHORIZATION ON DATABASE::[mydbname] TO [DOMAINuser]

Содержание

Fixing Maintenance Plan Error code 0x534
Код ошибки 0x534 sql
Answered by:
Question
Код ошибки 0x534 sql
Answered by:
Question
Код ошибки 0x534 sql
Answered by:
Question
Код ошибки 0x534 sql
Answered by:
Question