Post reply

Job fails due to AdminSQL having insufficient privileges

  • July 25, 2008 at 10:14 am

    #154565

    I have a job (SQL Server 2000) which runs sets of DTS packages. One of the DTS package fails because it is accessing a database which I have access to but AdminSQL doesn't I believe. It throws this error:

    "Step Error Description:Login failed for user 'DED123\AdminSQL'. Step Error code: 80040E4D Step Error Help File: Step Error Help Context ID:0 "

    If I run the same DTS package via my personal login credentials, it works fine.

    Is there a way to specify in the job schedule to make it run from my login credentials and not AdminSQL?

    Thanks for all your help.

    Sumit

  • July 25, 2008 at 11:04 am

    #848598

    The DTS package will run under the credentials of SQL Agent as a job. You need to be sure that this account has rights to the database.

    I think you might be able to set a proxy in SQL 2000 for non-SysAdmins, but probably you should be sure this account (service account for Agent) has rights.

    In SS2K5, you have more proxy options.

  • July 28, 2008 at 8:09 am

    #849208

    Steve,

    Thanks for the prompt reply.

    The SQL server agent can't be given access to that DB because the DB should have a limited access and the server (which happens to be a remote desktop) is used by lot of people who are not supposed to have access to that DB.

    So in turn if we give access to the "agent", everyone can access the DB which is not acceptable.

    Thanks,

    Sumit

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

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