January 23, 2013 at 1:09 pm
Ihave created thr stg_backup account for back jobs with backup operator preveliges associated with proxy account and I got this error message with failed job;
Message
Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed.
steps;
created the windows authenticated login
Created teh credentials
Created the proxy by selecting (SSIS) option.
Mapped the credentials to login
changed the owner to existing job and used the proxy account
the job failed. I tried to create a new job using this backup proxy account still job failed with the above error message. Please some one help me here. Thanks
January 23, 2013 at 1:20 pm
... My server just crashed and the business is failing... that's immediate help please type needs. This? Not so much.
As a fast fix, stop using DTS/SSIS for backups (good idea in general), and use a script task. Make sure the SQLAgent that's associated with your jobs has the rights it needs for all the file locations and the like as well.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
January 23, 2013 at 2:41 pm
Like Craig said, I would stop using a DTS package to perform the backups.
Here is another thread with the same issue
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 23, 2013 at 2:56 pm
I use the SSIS maintenance plans but they are owned by me (sysadmin) and operated by my service account which is a domain account.
But beyond that you also have to remember (which i don't see in your steps) that the owner of the job isn't the proxy account. The owner can be a non-sysadmin but needs a proxy to execute as since it will not allow you to execute as the service account for elevated security reasons. You need to change the execute as for each individual step to be the proxy account.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply