Job fails for linked server ("Executed as user: 'service accnt name'. Login failed for user 'service accnt name'. [SQLSTATE 28000] (Error 18456). The step failed.")

  • .. Not even a single response... !!!!

    Has anyone come across this issue ever ?

    Thanks

    Smith.

  • Ensure that SPN's are configured on both servers as it could be a Kerberos double hop authentication issue.

  • Hi Smith, I have the same issue as this.  Were you able to fix this and how?

  • vucando wrote:

    Hi Smith, I have the same issue as this.  Were you able to fix this and how?

    There are two different errors in the post - not sure if you are experiencing both. For login failures, check the SQL Server error log and check the state code associated with the error. You can find details for the different state codes in the following article:

    https://sqlblog.org/2011/01/14/troubleshooting-error-18456

    Sue

  • This kind of issue is one reason I avoid using linked servers for ETL type processes.

    If you can use Integration Services (SSIS) that would be a much easier implementation than using a linked server - and could also be configured to avoid issues with a growing transaction log - and improve overall performance of the load process.

    If you don't have access to Integration Services (SSIS) - you could look at scripting a process that runs BCP to extract and load the data.

     

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • I forgot to mention.  This is happening after I backup the database from 2005 and restores back to 2016 and scripts out the SQL jobs from 2005 and bring over....

Viewing 6 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply