|
I had three sequential packages which were run by three jobs every day. Last weekend first of the packages failed; there was no change from a DBA point of view. I created a job which runs each package in sequence. The job failed again at the first step. The package runs to completion in debug mode. Can anyone offer a clue?
(comments are locked)
|
|
Have the system administrators changed permissions at the file or share level on your source or destinations? Your account may have rights but the SQL services may not.
(comments are locked)
|
|
Not as far as I am aware. I created the job using a domain account which has sysadmin rights on the server Please provide more details. Are your source and destination local or remote? What errors are being presented? What does the first job - at a high level - do? etc.
Nov 26, 2009 at 10:41 AM
Blackhawk-17
The source and destination servers are on our network here. The only error is that the job has failed 'The package execution failed. The step failed.' The first package collects data from the source application/server and drops into RAW data on the distination server. The next two packages transform the data and then this is displayed. The source application runs 24 7 and has not altered in anyway.
Nov 26, 2009 at 12:33 PM
hodkinss
(comments are locked)
|
|
I reported a similar issue yesterday... Rob suggested setting the proxy permissions. It didnt work for me but maybe it will for you/? http://ask.sqlservercentral.com/questions/2171/ssis-package-fails-when-running-as-a-job I have tried this this morning and I got exactly the same error. I am completely stumped as this job has been running for months until last weekend
Nov 27, 2009 at 05:42 AM
hodkinss
(comments are locked)
|
What's the error message?