Post reply

Stored procedure not executing in Linked Server

  • February 16, 2018 at 5:39 am

    #403118

    Have a problem in which stored procedure is not getting executing it through a SQL Server agent job .Executing the SQL Server job on another SQL Server which is associated by Linked server.
    The error is as follows :
    Executed as user: XYZ\sa Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQL State 28000] [Error 18452]. The Step failed.Would appreciate if you could help out with the same on a quickly basis.

    Thanks in Advance
    Adil

  • February 16, 2018 at 5:46 am

    #1980040

    adilahmed1989 - Friday, February 16, 2018 5:39 AM

    Have a problem in which stored procedure is not getting executing it through a SQL Server agent job .Executing the SQL Server job on another SQL Server which is associated by Linked server.
    The error is as follows :
    Executed as user: XYZ\sa Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQL State 28000] [Error 18452]. The Step failed.Would appreciate if you could help out with the same on a quickly basis.

    Thanks in Advance
    Adil

    That is a very common error, have you investigated it for yourself? What have you tried, in order to resolve it?

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • February 16, 2018 at 5:51 am

    #1980041

    adilahmed1989 - Friday, February 16, 2018 5:39 AM

    Have a problem in which stored procedure is not getting executing it through a SQL Server agent job .Executing the SQL Server job on another SQL Server which is associated by Linked server.
    The error is as follows :
    Executed as user: XYZ\sa Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQL State 28000] [Error 18452]. The Step failed.Would appreciate if you could help out with the same on a quickly basis.

    Thanks in Advance
    Adil

    Please read this & come up with a solution, It's a very common error.

    https://blogs.msdn.microsoft.com/sql_protocols/2008/05/02/understanding-the-error-message-login-failed-for-user-the-user-is-not-associated-with-a-trusted-sql-server-connection/

  • February 16, 2018 at 5:51 am

    #1980042

    Actually there is some issue in user Permission rights; but i am unsure about it. It would be helpful if there is any clarity on the issue so that i can work upon the resolution in a quickest way and get to know what should i do to resolve

  • February 16, 2018 at 5:58 am

    #1980044

    adilahmed1989 - Friday, February 16, 2018 5:51 AM

    Actually there is some issue in user Permission rights; but i am unsure about it. It would be helpful if there is any clarity on the issue so that i can work upon the resolution in a quickest way and get to know what should i do to resolve

    So ... you won't make the effort to learn about it yourself, you just want free consultancy from others who have taken the time. Good luck.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • February 16, 2018 at 6:42 am

    #1980059

    adilahmed1989 - Friday, February 16, 2018 5:39 AM

    Have a problem in which stored procedure is not getting executing it through a SQL Server agent job .Executing the SQL Server job on another SQL Server which is associated by Linked server.
    The error is as follows :
    Executed as user: XYZ\sa Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. [SQL State 28000] [Error 18452]. The Step failed.Would appreciate if you could help out with the same on a quickly basis.

    Thanks in Advance
    Adil

    If you are referring with the "XYZ\sa" account to the SQL sysadmin sa account, you don't specify a domain name in the account notation. Also make sure the instance is configured for SQL Authentication. But note that it is best practice to use "Integrated security", so you should (rebuild to) use a Windows domain account.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • February 18, 2018 at 5:17 pm

    #1980208

    For the love of all that is holy in the world of database security, stop using the SA account for anything.  Setup a separate Active Directory service account and use that instead.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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