Hello There,

I have a very simple SSIS package that I want to schedule to run via SQL
Server Agent Job, but so far I was not able to make to run.

The SSIS package runs fine within SS Management Studio and Business
Intelligence Development Studio (BIDS), but when I tried to run it in a
scheduled job via SQL Server Agent it just fails

error message "The package execution failed. The step failed."

Any troubleshooting ideas on this issue are highly appreciated.
Thanks!

Figured this out, reason SQL server agent jobs does not work, because this
agent uses its own login credentials and the SSIS packages were written using
administrator credentials.

To fix this issue, go to run execute this services.msc then find the SQL
Server Agent go to "Logging" and change the "Log in as" to the credentials
under which the DTS are written, my case the administrator login.

Then the SQL server will execute any scheduled jobs for your SSIS packages.

Hope it helps.



"martino" wrote:

Thanks for following up your own post. It prevents others from wasting their
time trying to help you after you have solved the problem, and it helps
others when you share your solution.


--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"martino" <martino (AT) discussions (DOT) microsoft.com> wrote

Hi Martino,

You may find yourself having problems with other jobs with this solution. As
you have configured SQL Server Agent to run with this new account, all jobs
on the server now run in this context. What you really need to do is to go
edit your job step. Use the "Run As" drop-down to specify a proxy account
that has the credential with the permission to run the package (you need to
configure the credential and proxy before editing the step). This way jobs
previously scheduled are not affected.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk


"martino" wrote:

Hi Charles,

I tried this several times by now, I created a credential and mapped it to
a proxy account to run SSIS packages and still it fails. I used the option
"Run As" and selected the proxy account and nothing, it fails.

I like very much this idea to set up a proxy account , but maybe my
environment, i am working off a laptop that has Windows 2003 enterprise
server and SQL 2005 enterprise installed.

any troubleshooting ideas on this issue, is highly appreciated.

Thanks!





"Charles Kangai" wrote: