The job runs with “domain\ User” and the following error is encountered:
JOB RUN: 'Product_JobTest' was run on 2016/10/27 at 4:30:00
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. Unable to determine if the owner (domain\user) of job Product_JobTest has server access (reason: Could not obtain information about Windows NT group/user 'domain\user', error code 0x5. [SQLSTATE 42000] (Error 15404)).
Read the following reference articles:
http://www.cnblogs.com/kerrycode/p/3339558.html
http://www.cnblogs.com/kerrycode/p/5551994.html
http://consulting.risualblogs.com/blog/2013/03/01/could-not-obtain-information-about-windows-nt-groupuser-domainuser-error-code-0x5-sqlstate-42000-error-15404-connisloginsysadmin/
We started to try to modify the owner of the job as SA, and encountered two problems:
1. For the report subscription job generated by the report service, the subscription scheduling time of 2008R2 failed to be modified, and this problem was not encountered in 2014.
2. For the cross-server access job deployed by the business, it will be verified with the startup account of SQL Server Agent service, and the access permission of LINKEDSERVER needs to be configured.
Solutions:
On the domain controlled Server, add the startup account of SQL Server service to “BUILTIN\Windows Authorization Access Group”, and then let the job run with “Domain \ User” as the owner, and no error will be reported.
Read More:
- SQL Server 2008 login 4064 error solution
- Solution to SQL Server Error: 4064
- SQL Server 2008 18456 error and SA unable to login solution
- The solution of PL / SQL can’t connect to the remote server after installing Oracle locally
- Prompt SQL server error 15023 solution memo when modifying user mapping
- Solution of error converting data type varchar to datetime in SQL Server
- SQL server remote computer refused network connection, error: 1225, specific solution steps.
- Microsoft SQL server, additional database error: error 916 solution
- SQL 2005 remote connection error (provider: SQL network interface, error: 28 – the server does not support the requested protocol
- SQL Server SSPI handshake failed Error
- SQL Server “login failed for user ‘domain account”. [sqlstate 28000] (error 18456). “Problem solving
- Java 11.0.11 SQL Server connection error
- Version problem of SQL Server
- About installing SQL server 0 in Windows 10 20h2 × 84bb0001 is one of the solutions
- Navicat remote connection SQL Server 2014 express report 08001 error
- install sql server 2016 Error code 0x84B20001
- SQL Server 2005, unable to log in, forget sa password, 15405 error!
- 12-web security — error injection based on SQL Server — and, convert, cast
- Reporting Services Catalog Database File Existence” error during installing SQL Server 2008 R2
- Insert into / delete / update / select of SQL Server database table