- Remove From My Forums
-
Question
-
Backup job for User databases is failing.
I found below errors
View job historyStep 0:
The job failed. The job was invoked by schedule 4(DBMP_User). The last step to run was step 1(subplan)
Step 1:Message: Executed as user ServernameSystem. The package execution failed. The step failed
Appln-event log:
SQL server scheduled job DBMP_User failed. Invoked on 2007-12-24 , the job was failed.
Sql server error log
Database backed up. DBname creation,date()time……paged dumped 8434659,first LSN: 21126:101410:48,last LSN :21128:933:1, number of dump devices:1, device information: file=1,type=disk (E:MSSQLBACKUP )
This is an informational message only. No user action is requiredError log:
Date:
Log: SQL Agent (current …)
Message:
(396) An idle CPU condition has not been defined-OnIdle job schedules will have no effect.Please advice how to proceed?
Answers
-
Backup job for User databases is failing.
I found below errors
View job historyStep 0:
The job failed. The job was invoked by schedule 4(DBMP_User). The last step to run was step 1(subplan)
Step 1:Message: Executed as user ServernameSystem. The package execution failed. The step failed
Appln-event log:
SQL server scheduled job DBMP_User failed. Invoked on 2007-12-24 , the job was failed.
Sql server error log
Database backed up. DBname creation,date()time……paged dumped 8434659,first LSN: 21126:101410:48,last LSN :21128:933:1, number of dump devices:1, device information: file=1,type=disk (E:MSSQLBACKUP )
This is an informational message only. No user action is requiredError log:
Date:
Log: SQL Agent (current …)
Message:
(396) An idle CPU condition has not been defined-OnIdle job schedules will have no effect.If we look at the error message «An idle CPU condition has not been defined», it seem like that while taking backup the CPU goes on idle for a long period of time. Probably more than 10 min. We can try setting the properties of SQL Server Agent by right
clicking and select «Advanced» option or extend the time for Idle CPU condition. For more details refer
http://msdn.microsoft.com/en-us/library/ms189065(v=sql.90).aspxOne reason for going CPU idle when the job is running can be due to space issue in the server. Here we have a solution where the user cleanup some backup files and the issue got resolved. Refer
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=94668
Regards, RSingh
-
Proposed as answer by
Saturday, February 1, 2014 10:54 AM
-
Marked as answer by
Kalman Toth
Monday, February 10, 2014 1:59 PM
-
Proposed as answer by
Периодически останавливается Агент, запускаю вручную и он работает, проходит неделя-две — опять остановился, в заданиях только бэкап 1С
вот лог — мне он ничего не говорит, может кто подскажет ?
Дата,Источник,Серьезность,Сообщение
04/11/2011 11:12:44,,Предупреждение,[396] An idle CPU condition has not been defined — OnIdle job schedules will have no effect
04/11/2011 11:12:44,,Предупреждение,[260] Unable to start mail session (reason: No mail profile defined)
04/11/2011 11:12:44,,Сведения,[129] SQLSERVERAGENT starting under Windows NT service control
04/11/2011 11:12:44,,Ошибка,[364] The Messenger service has not been started — NetSend notifications will not be sent
04/11/2011 11:12:40,,Сведения,[432] There are 11 subsystems in the subsystems cache
04/11/2011 11:12:39,,Сведения,[339] Local computer is TERM01 running Windows NT 5.2 (3790) Service Pack 2
04/11/2011 11:12:39,,Сведения,[310] 16 processor(s) and 8183 MB RAM detected
04/11/2011 11:12:39,,Сведения,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
04/11/2011 11:12:39,,Сведения,[102] SQL Server ODBC driver version 9.00.4035
04/11/2011 11:12:39,,Сведения,[101] SQL Server TERM01 version 9.00.4035 (0 connection limit)
04/11/2011 11:12:39,,Сведения,[100] Microsoft SQLServerAgent version 9.00.4035.00 ((Unknown) unicode retail build) : Process ID 5960
04/08/2011 09:21:12,,Сведения,[098] SQLServerAgent terminated (normally)
04/08/2011 09:21:09,,Сведения,[131] SQLSERVERAGENT service stopping due to a stop request from a user<c/> process<c/> or the OS…
04/08/2011 08:49:11,,Предупреждение,[396] An idle CPU condition has not been defined — OnIdle job schedules will have no effect
04/08/2011 08:49:11,,Предупреждение,[260] Unable to start mail session (reason: No mail profile defined)
04/08/2011 08:49:11,,Сведения,[129] SQLSERVERAGENT starting under Windows NT service control
04/08/2011 08:49:11,,Ошибка,[364] The Messenger service has not been started — NetSend notifications will not be sent
04/08/2011 08:49:09,,Сведения,[432] There are 11 subsystems in the subsystems cache
04/08/2011 08:49:09,,Сведения,[339] Local computer is TERM01 running Windows NT 5.2 (3790) Service Pack 2
04/08/2011 08:49:09,,Сведения,[310] 16 processor(s) and 8183 MB RAM detected
04/08/2011 08:49:09,,Сведения,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
04/08/2011 08:49:09,,Сведения,[102] SQL Server ODBC driver version 9.00.4035
04/08/2011 08:49:09,,Сведения,[101] SQL Server TERM01 version 9.00.4035 (0 connection limit)
04/08/2011 08:49:09,,Сведения,[100] Microsoft SQLServerAgent version 9.00.4035.00 ((Unknown) unicode retail build) : Process ID 3584
04/08/2011 08:49:07,,Сведения,[393] Waiting for SQL Server to recover databases…
04/08/2011 08:48:52,,Сведения,[098] SQLServerAgent terminated (normally)
04/08/2011 08:48:48,,Сведения,[131] SQLSERVERAGENT service stopping due to a stop request from a user<c/> process<c/> or the OS…
03/29/2011 08:39:24,,Предупреждение,[396] An idle CPU condition has not been defined — OnIdle job schedules will have no effect
03/29/2011 08:39:24,,Предупреждение,[260] Unable to start mail session (reason: No mail profile defined)
03/29/2011 08:39:24,,Сведения,[129] SQLSERVERAGENT starting under Windows NT service control
03/29/2011 08:39:24,,Ошибка,[364] The Messenger service has not been started — NetSend notifications will not be sent
03/29/2011 08:39:21,,Сведения,[432] There are 11 subsystems in the subsystems cache
03/29/2011 08:39:21,,Сведения,[339] Local computer is TERM01 running Windows NT 5.2 (3790) Service Pack 2
03/29/2011 08:39:21,,Сведения,[310] 16 processor(s) and 8183 MB RAM detected
03/29/2011 08:39:21,,Сведения,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
03/29/2011 08:39:21,,Сведения,[102] SQL Server ODBC driver version 9.00.4035
03/29/2011 08:39:21,,Сведения,[101] SQL Server TERM01 version 9.00.4035 (0 connection limit)
03/29/2011 08:39:21,,Сведения,[100] Microsoft SQLServerAgent version 9.00.4035.00 ((Unknown) unicode retail build) : Process ID 3484
LEXX
-
#1
Добрый день, коллеги! Помогите с проблемой — не получается выполнить план обслуживания SQL server 2019. Ошибка внутри Агента
Сообщение
[298] Ошибка SQLServer: 15404, Не удалось получить сведения о пользователе или группе Windows NT «DOMENJulia», код ошибки: 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
Подскажите что не так…
Последнее редактирование: 20.09.2021
-
#2
Еще вижу пару ошибок, не ясно относится это к делу или нет
Дата 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 использоваться не будут
-
#3
Попробуйте использовать SA а не «DOMENJulia
-
#4
Можно попробовать пересоздать план обслуживания
-
#5
Попробуйте использовать SA а не «DOMENJulia
А где это делать ??
-
#7
Создала план обслуживания заново, заработало)
-
#8
Как я понял, это происходит из-за изменения названия домена или имени ПК (при этом изменяется имя сервера). А у пользователя остаётся предыдущее имя. Например, у вас было имя «DOMENJulia», соответственно имя сервера «DOMEN». Вы меняете имя компьютера на другое, имя сервера тоже меняется на «дргуое», а ваше имя остаётся «DOMENJulia», вместо «другоеJulia». Точнее, оно меняется, но при создании объектов в поле «владелец» записывается старое имя, которое уже не проходит проверку безопасности.
Вот что у меня сейчас и вот что показывает, когда создаю новую БД:
Помогло изменение владельца на sa.
Scheduled tasks fail with this error message:
«[396] An idle CPU condition has not been defined — OnIdle job schedules
will have no effect»
The OS is Windows Server 2003 R2 Std Edition SP2
SQL Server 2005 Developer Edition (9.0.3042)
Analysis Services is running.
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00
(srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.2.3790
What is the problem and the solution?Hi,
Goto properties of SQL Server Agent —> Advanced —> Check «Idle CPU
condition» and define appropriate values.
HTH,
Dinesh|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. what is kind of your job?
2. Does your SQL Server Agent Service account has administrator permission?
If not, what is the result if you use a local administrator as your SQL
Server Agent Services startup account?
3. Does this issue occur always or intermittently?
Also, for further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the SQL error logs which are located in the
folder %ProgramFiles%Microsoft SQL ServerMSSQL(.n)LOG by default.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
«Tools/Options/Read: Get 300 headers at a time» to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please «Reply to Group» via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided «AS IS» with no warranties, and confers no rights.
======================================================|||Thank you. That did it.
<dinu_babu@.hotmail.com> wrote in message
news:1185349324.238775.247870@.x40g2000prg.googlegroups.com…
> Hi,
> Goto properties of SQL Server Agent —> Advanced —> Check «Idle CPU
> condition» and define appropriate values.
> HTH,
> Dinesh
>|||I needed to go to properties of SQL Server Agent —> Advanced —> Check
«Idle CPU
condition» and define appropriate values. as described by Dinesh|||Hi,
Thanks for your updating and response.
I am glad to hear that this issue has been fixed by Dinesh’s suggestion. If
you have any other questions or concerns, please feel free to let us know.
It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
«Tools/Options/Read: Get 300 headers at a time» to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please «Reply to Group» via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided «AS IS» with no warranties, and confers no rights.
======================================================
Перейти к контенту
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:
[Output:sql] type=File filename=/var/opt/mssql/log/pallog.txt [Logger:security] level=debug outputs=sql
Let’s take a look at the messages in PALLOG:
03/12/2022 12:36:56.448761588 Debug [security.kerberos] <0000040947/0x00000200> Processing SSPI operation 0x0000000F 03/12/2022 12:36:56.439366379 Error [security.ldap] <0000040947/0x00000200> Initializing credentials for use in new cache failed: Keytab contains no suitable keys for red4$@SQLREPRO.EDU 03/12/2022 12:36:56.439613575 Debug [security.kerberos] <0000040947/0x00000200> Import name [ADMINISTRATOR@SQLREPRO.EDU] returned [ADMINISTRATOR@SQLREPRO.EDU] 03/12/2022 12:36:56.439633375 Debug [security.kerberos] <0000040947/0x00000200> Import name [red4$] returned [red4$] 03/12/2022 12:36:56.439753473 Debug [security.kerberos] <0000040947/0x00000200> Import name [RED4$] returned [RED4$] 03/12/2022 12:36:56.439905471 Debug [security.kerberos] <0000040947/0x00000200> Import name [red4$] returned [red4$] 03/12/2022 12:36:56.440014469 Error [security.kerberos] <0000040947/0x00000200> GSS MAJOR: 851968 GSS MINOR: 39756033 Error acquiring credentials in AcquireCredCaseInsensitive 03/12/2022 12:36:56.440029069 Error [security.kerberos] <0000040947/0x00000200> Unspecified GSS failure. Minor code may provide more information 03/12/2022 12:36:56.440039869 Error [security.kerberos] <0000040947/0x00000200> No key table entry found for red4$@SQLREPRO.EDU 03/12/2022 12:36:56.440053069 Debug [security.kerberos] <0000040947/0x00000200> SSPI operation 0x0000000F returned status: KerberosStream.cpp:2021 Operation unsuccessful 03/12/2022 12:36:56.440119868 Debug [security.kerberos.libos] <0000040961/0x0000020c> GetSecContextByUserABI() return value: 0x80090304 03/12/2022 12:36:56.468617991 Debug [security.kerberos.libos] <0000040961/0x0000020c> QueryContextAttributes() return value: 0x00000000 03/12/2022 12:36:56.468748289 Debug [security.kerberos.libos] <0000040961/0x0000020c> QueryContextAttributes() return value: 0x00000000 03/12/2022 13:56:26.489370580 Debug [security.kerberos.libos] <0000040961/0x0000020c> LookupAccountSid() return value: 0x00000001
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.
- If SQL Server uses a machine account like Local System or Network System, the machine has to be trusted by the Windows User domain.
- Use a SQL Server account
[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.
GET STARTED
I am creating a SQL Server Replication using a script. When I try to execute
The job failed. Unable to determine if the owner (STARmoorer7) of job L3BPT2M-Atlas-14 has server access (reason: Could not obtain information about Windows NT group/user 'STARmoorer7', error code 0x5. [SQLSTATE 42000] (Error 15404)).
This is a job created by a script that defines replication.
How do I debug this?
asked Aug 5, 2009 at 17:13
Raj MoreRaj More
46.5k33 gold badges128 silver badges194 bronze badges
3
Active Directory is refusing access to your SQL Agent. The Agent should be running under an account that is recognized by STAR domain controller.
magnattic
12.4k13 gold badges63 silver badges114 bronze badges
answered Aug 5, 2009 at 17:30
Remus RusanuRemus Rusanu
285k40 gold badges429 silver badges564 bronze badges
7
For me, the jobs were running under DOMAINAdministrator and failing with the error message "The job failed. Unable to determine if the owner (DOMAINadministrator) of job Agent history clean up: distribution has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINadministrator', error code 0x5. [SQLSTATE 42000] (Error 15404)).
To fix this, I changed the owner of each failing job to sa
. Worked flawlessly after that. The jobs were related to replication cleanup, but I’m unsure if they were manually added or were added as a part of the replication set-up — I wasn’t involved with it, so I am not sure.
answered Sep 19, 2016 at 15:00
Derreck DeanDerreck Dean
3,6581 gold badge25 silver badges45 bronze badges
0
We encountered similar errors in a testing environment on a virtual machine. If the machine name changes due to VM cloning from a template, you can get this error.
If the computer name changed from OLD to NEW.
A job uses this stored procedure:
msdb.dbo.sp_sqlagent_has_server_access @login_name = 'OLDAdministrator'
Which uses this one:
EXECUTE master.dbo.xp_logininfo 'OLDAdministrator'
Which gives this SQL error 15404
select text from sys.messages where message_id = 15404;
Could not obtain information about Windows NT group/user '%ls', error code %#lx.
Which I guess is correct, under the circumstances. We added a script to the VM cloning/deployment process that re-creates the SQL login.
answered Feb 16, 2012 at 21:43
Craig CelesteCraig Celeste
11.9k9 gold badges41 silver badges48 bronze badges
In my case I was getting this error trying to use the IS_ROLEMEMBER()
function on SQL Server 2008 R2. This function isn’t valid prior to SQL Server 2012.
Instead of this function I ended up using
select 1
from sys.database_principals u
inner join sys.database_role_members ur
on u.principal_id = ur.member_principal_id
inner join sys.database_principals r
on ur.role_principal_id = r.principal_id
where r.name = @role_name
and u.name = @username
Significantly more verbose, but it gets the job done.
Raj More
46.5k33 gold badges128 silver badges194 bronze badges
answered Jan 3, 2013 at 18:44
Bacon BitsBacon Bits
30k5 gold badges55 silver badges63 bronze badges
Just solved this problem. In my case it was domain controller is not accessible, because both dns servers was google dns.
I just add to checklist for this problem:
- check domain controller is accessible
answered Aug 4, 2014 at 11:26
RailRail
7008 silver badges12 bronze badges
1
I was having the same issue, which turned out to be caused by the Domain login that runs the SQL service being locked out in AD. The lockout was caused by an unrelated usage of the service account for another purpose with the wrong password.
The errors received from SQL Agent logs did not mention the service account’s name, just the name of the user (job owner) that couldn’t be authenticated (since it uses the service account to check with AD).
answered Mar 4, 2015 at 0:51
I had to connect to VPN for the publish script to successfully deploy to the DB.
answered Apr 25, 2015 at 17:42
PetePete
1492 silver badges14 bronze badges
In our case, the Windows service account that SQL Server and SQL Agent were running under were locked out in Active Directory.
answered Jul 12, 2019 at 12:57
I just got this error and it turns out my AD administrator deleted the service account used by EVERY SQL Server instance in the entire company. Thank goodness AD has its own recycle bin.
See if you can run the Active Directory Users and Computers utility (%SystemRoot%system32dsa.msc), and check to make sure the account you are relying on still exists.
answered May 26, 2020 at 22:03
Hello,
I’m having trouble running jobs with my active directory (ADS) account. I’ve setup my SQL services to run under an ADS account, but jobs cannot seem to query ADS for user information. We’re running Windows Server 2003 and SQL Server 2005 SP2.
Here is the error message:
==
The job failed. Unable to determine if the owner (ADSme) of job eFASRtest has server access (reason: Could not obtain information about Windows NT group/user ‘ADSme’, error code 0x5. [SQLSTATE 42000] (Error 15404)).
==
also this message in log:
==
[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user ‘ADSme, error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
==
I have done a *lot* of searching and cannot find the solution. I believe the 0x5 code is access denied.
The same job runs if I change the owner to a SQL login that’s not an ADS account.
I’m not certain how to confirm that the SQL Agent account is the account actually querying ADS, also.
Any help would be greatly appreciated!
Thanks,
-Tony
- Remove From My Forums
-
Question
-
Hello,
Thank you all in advance for a reply (and hopefully a solution!).
Intermittently, we receive the following error when a SQL Agent Job is started:
The job failed. Unable to determine if the owner (DOMAINsvcaccount) of job SolveMe has server access (reason: Could not obtain information about Windows NT group/user ‘DOMAINsvcaccount’, error code 0x3a. [SQLSTATE 42000] (Error 15404)).
Again, the key word is intermittently. Our processes work most nights, but sometimes the above error pops up. This happens for various jobs at various times.
Additionally, this error has been seen with DTS packages in SQL Server 2000.
I do not believe this is a permissions issue with the service account, because as I said, most of the time it works. However when it doesn’t, our on call gets paged in the middle of the night to simply restart the process. That is no fun at all!
Any ideas??
- Remove From My Forums
-
Question
-
Hello,
Thank you all in advance for a reply (and hopefully a solution!).
Intermittently, we receive the following error when a SQL Agent Job is started:
The job failed. Unable to determine if the owner (DOMAINsvcaccount) of job SolveMe has server access (reason: Could not obtain information about Windows NT group/user ‘DOMAINsvcaccount’, error code 0x3a. [SQLSTATE 42000] (Error 15404)).
Again, the key word is intermittently. Our processes work most nights, but sometimes the above error pops up. This happens for various jobs at various times.
Additionally, this error has been seen with DTS packages in SQL Server 2000.
I do not believe this is a permissions issue with the service account, because as I said, most of the time it works. However when it doesn’t, our on call gets paged in the middle of the night to simply restart the process. That is no fun at all!
Any ideas??
- Remove From My Forums
-
Question
-
I have created a Job which will run the script generated by LiteSpeed for a particular DB Restore. However when i run the job, it is failing with the following error:
The job failed. Unable to determine if the owner (REDMONDv-kamir) of job Restore_Job has server access (reason: Could not obtain information about Windows NT group/user ‘REDMONDv-kamir’, error code 0x5. [SQLSTATE 42000] (Error 15404)).
I ran the script through SSMS and it works fine. Any ideas how to fix this?
Answers
-
Hello,
Error 0x5 means access denied.
Try to changing the owner of the jobs to the sa account, on the properties of the job.
If the above does no help, please change the service account for the SQL Server agent service to account with proper permissions.
http://technet.microsoft.com/en-us/library/ms345578.aspx
Hope this helps.
Regards,Alberto Morillo
SQLCoffee.com
- Proposed as answer by
Friday, December 31, 2010 3:20 AM
- Marked as answer by
Kazim Ali Tabrez Mir
Friday, December 31, 2010 5:56 PM
- Proposed as answer by
SQL Server Agent 15404 Error
If you encounter in the Sql Server Agent Log «SQLServer Error: 15404, Could not obtain information about Windows NT group/user ‘ISTMRKSQLHOSTAdministrator’, error code 0x534. [SQLSTATE 42000] (ConnIsLoginSysAdmin)» this is related with Sql Server Agent job security.
Open Sql Server Management Studio, go to Object Explorer select Jobs under SQL Server Agent. Find your Maintenance Plan and right click on it, select Properties. On the General Page change Owner to ‘sa‘. Then execute the maintenance plan again.
Popular posts from this blog
On HP 3PAR Storage, disks are grouped inside magazines. So when it comes to replacing a failed disk, magazine that holds the disk has to be brought offline using a servicemag start command.
In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three
Recently I have to export the user list for a particular domain. Luckily Zimbra has Admin GUI with a search feature. When you search accounts, you can download search results as a comma-separated csv file. So I did a search and download the result file, but the result did not have all the columns I need and also there is no option for customizing columns for search results. So I had to write a bash script to get the desired list. Here is the bash script ( It can be customized by adding or removing field names. Run it under zimbra user like ./zimbra_account_list.sh <domain_name_here> ):
-
#1
Добрый день, коллеги! Помогите с проблемой — не получается выполнить план обслуживания SQL server 2019. Ошибка внутри Агента
Сообщение
[298] Ошибка SQLServer: 15404, Не удалось получить сведения о пользователе или группе Windows NT «DOMENJulia», код ошибки: 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
Подскажите что не так…
Последнее редактирование: 20.09.2021
-
#2
Еще вижу пару ошибок, не ясно относится это к делу или нет
Дата 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 использоваться не будут
-
#3
Попробуйте использовать SA а не «DOMENJulia
-
#4
Можно попробовать пересоздать план обслуживания
-
#5
Попробуйте использовать SA а не «DOMENJulia
А где это делать ??
-
#7
Создала план обслуживания заново, заработало)
-
#8
Как я понял, это происходит из-за изменения названия домена или имени ПК (при этом изменяется имя сервера). А у пользователя остаётся предыдущее имя. Например, у вас было имя «DOMENJulia», соответственно имя сервера «DOMEN». Вы меняете имя компьютера на другое, имя сервера тоже меняется на «дргуое», а ваше имя остаётся «DOMENJulia», вместо «другоеJulia». Точнее, оно меняется, но при создании объектов в поле «владелец» записывается старое имя, которое уже не проходит проверку безопасности.
Вот что у меня сейчас и вот что показывает, когда создаю новую БД:
Помогло изменение владельца на sa.