Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Mikehjun
Starting Member
24 Posts |
 Posted - 2010-12-01 : 20:56:14
|
| I created a simple SSIS package that copy table in SQL 2008 to Access. SSIS runs just fine itself in SQL and even through BIDS. No error! Great! However when I try to run as a job, it gives me error. Error message doesn't say much 'the job failed. the job was invoked by user 'me'. the last step to run was step1'The following is what I have done so far.Creating SSIS with no encrytion, use Proxy account, use UNC path, use 32bit runtime.Could you somebody tell me what else I need to change?Thanks, |
|
|
dataguru1971
Master Smack Fu Yak Hacker
1464 Posts |
Posted - 2010-12-01 : 21:08:06
|
Run the job as 'sa' not as yourself.
Poor planning on your part does not constitute an emergency on my part. |
 |
|
|
Mikehjun
Starting Member
24 Posts |
Posted - 2010-12-01 : 21:17:04
|
| Thanks for a quick reply.I tried to run as SA too. no luck. I created Access on local machine where SQL installed but no luck.I even put dtexec on batch file and try to fire up through stored procedure but no luck. However it ran just fine by batch file itself.Driving me insane! |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-12-02 : 07:37:10
|
| Make sure the SQL Agent Service account has permission to do everything you're doing in the package.Also, make sure package protection level is set to "Rely on Server Storage and Roles" |
|
|
|
yavvie
Starting Member
46 Posts |
Posted - 2010-12-17 : 11:18:33
|
| have you looked in the history of the job? it should give you a detailed error report as to why it fails. Usually it's access rights to the dts/folders/source files/database etc. or privileges of the user that runs the job. |
|
|
|
|
|
|
SSIS won't run thruogh SQL Server Agent Job