Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account.

  • Trying to execute a maintenance plan that simply checks db integrity, backups the db and the transaction logs and cleans up any .bak/.trn files older than 3 days and am getting:

    "Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed."

    My user is owner of the job and is in the 'sysadmin' server role.

    The SQL Server Agent and SQL Server service accounts are both 'Local System' (I'll fix this later)

    The BUILTIN\Administrators group is a valid login (I'll fix this later)

    'guest' can connect to the 'msdb' database (I'll fix this later)

    What am I missing? These jobs run w/o issue on all my other servers, that are setup the same.

    TIA.

    ----------------------------------------------------------------------------
    Sacramento SQL Server users group - http://sac.sqlpass.org
    Follow me on Twitter - @SQLDCH
    ----------------------------------------------------------------------------

    Yeah, well...The Dude abides.
  • Was your package being run as a job? If so I suspect that the SQL Server Agent account lacks the sufficient rights. Try fixing now instead of later.



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Thanks Alvin. But shouldn't the 'Local System' account have enough privileges to run the job?

    http://msdn.microsoft.com/en-us/library/ms143504.aspx

    I changed the job owner to 'sa' (from my domain account) and it ran correctly. Frustrating that this is occurring, as it seems I've covered all my bases.

    ----------------------------------------------------------------------------
    Sacramento SQL Server users group - http://sac.sqlpass.org
    Follow me on Twitter - @SQLDCH
    ----------------------------------------------------------------------------

    Yeah, well...The Dude abides.
  • dh (7/24/2009)


    Thanks Alvin. But shouldn't the 'Local System' account have enough privileges to run the job?

    You might expect that it should, but don't assume that it will.



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • I guess I shouldn't have asked the question, as it isn't pertinent to the issue. I'm trying to find out why my user is 'broken' now, will post back with any results I find. I did do a named instance un-install on this box, wondering if it's the culprit.

    ----------------------------------------------------------------------------
    Sacramento SQL Server users group - http://sac.sqlpass.org
    Follow me on Twitter - @SQLDCH
    ----------------------------------------------------------------------------

    Yeah, well...The Dude abides.
  • Dan, I am experiencing the same problem with my Main Plan jobs for backup failing and complaining of Non-SysAdmin not having ability to run DTS jobs. I was also running them fine for months and the accts have sysadmin rights.

    Did you ever find a solution to this?

    Gary

  • I am having the same issue, have you found the solution. Thanks.

  • I never found the "why", instead just created a proxy account and used it to run the jobs. A "gotcha" though, if you change an aspect of the job, like the schedule, it will revert the "Run As" portion to the original user.

    Check here for a workaround:

    http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/1e899c89-27d3-4404-b71b-d044b7f58fb2

    ----------------------------------------------------------------------------
    Sacramento SQL Server users group - http://sac.sqlpass.org
    Follow me on Twitter - @SQLDCH
    ----------------------------------------------------------------------------

    Yeah, well...The Dude abides.
  • i had the same issue. The only way i could resolve it was to add the account that is running the sql agent service as an admin on the box the job is running on.

    for me if the sql agent service user is admin on box then i no longer get the issue

  • For solution click here

    Thanks

    Saurabh Sinha

    http://saurabhsinhainblogs.blogspot.in/[/url]

Viewing 10 posts - 1 through 9 (of 9 total)

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