Post reply

SETUSER error

  • March 10, 2005 at 7:18 pm

    #102427

    Hi everyone,

    We have set up the same job on two servers. The jobs are owned by "sa" and run as "self". The job on each of these two servers uses a linked server to connect to a third server. One of the jobs succeeds while the other fails with the following error:

    Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated by SETUSER. [SQLSTATE 42000]

    So, it's like this:

    A B

    \ /

    C

    Same job on A and B connect to C through linked servers and one job fails.

    Any ideas will be greatly appreciated! Thank you!

  • March 10, 2005 at 7:24 pm

    #546520

    What version of windows and SQL are you running? What action does the job perform?

     

    --------------------
    Colt 45 - the original point and click interface

  • March 11, 2005 at 7:22 am

    #546606

    What is the startup account being used for sql server.  Are they the same on both servers?  Are they both in the same domain.  Do you map the user to a login the same way on both servers within the linked server.

    Tom

  • March 11, 2005 at 12:13 pm

    #546702

    Hi everyone,

    Both are SQL 2K on Win 2K and both SQL and Win have the latest patches applied.

    Both SQL databases have the same startup account, which is a domain user with local admin privilages. And both linked servers are set up to log in using the same username, 'sa'.

  • March 11, 2005 at 1:16 pm

    #546718

    If you can describe what action does the job perform?

Viewing 5 posts - 1 through 5 (of 5 total)

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