A job in SQL Server 2005 (Microsoft SQL Server 2005-9.00.5000.00) executes a stored procedure in which a dynamic SQL statement uses a linked server (Linked Servers), from another SQL Server servers to obtain data. However, the executive Times "Access to the remote server are denied because the current security context are not trusted". But it is OK to manually execute the stored procedure on the SSMs client.
Encounter this problem is very strange, seems to be a privilege and security reasons, but a lot of homework is also done, but this server encountered this problem. There are a lot of people on the Internet that are experiencing this problem. Officials have some information.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/512991fd-af88-4a87-8b3e-39e0e346040e/ Access-to-the-remote-server-is-denied-because-the-current-security-context-is-not-trusted?forum=sqlsecurity
https://blogs.msdn.microsoft.com/deepakbi/2010/03/02/ Job-fails-on-linked-server-access-to-the-remote-server-is-denied-because-the-current-security-context-is-not-trusted-sqls tate-42000-error-15274/
http://dba.stackexchange.com/questions/114723/ Current-security-context-is-not-trusted-for-job-running-as-a-sql-login-accessi
Https://www.sqlservercentral.com/Forums/Topic579778-146-1.aspx
There are also a variety of solutions available. I tried them all, and the results didn't solve my problem. Finally, follow the following article to solve the problem.
http://stackoverflow.com/questions/10526198/ Access-to-the-remote-server-is-denied-because-the-current-security-context-is-no
Modify the owner of the job to change the account used by the job owner from the SA to the security context of the linked server (Linked server), and solve the problem. Although the problem solved, but still did not understand root cause, and some people have no solution to communicate. Let's record the problem for the time being.
SQL Agent Job Report "Access to the remote server was denied because the current security context isn't trusted"