Link to home
Start Free TrialLog in
Avatar of tl121000
tl121000Flag for United States of America

asked on

DTS package execute fine manually, but as job I get...

I created a DTS package that simply select values from a table and exports them to a .txt file.

The package runs just fine if I execute the package manually.

However, when i set it up as a schedule job, the job fails;  the job log details are as follows...

The job failed.  The Job was invoked by Schedule 71 (Horizon --> Midas \ sis$).  The last step to run was step 1 (Horizon --> Midas \ sis$).

Executed as user: TENEX\SYSTEM. DTSRun:  Loading...   DTSRun:  Executing...   DTSRun OnStart:  DTSStep_DTSDataPumpTask_1   DTSRun OnError:  DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)      Error string:  Error opening datafile: Access is denied.         Error source:  Microsoft Data Transformation Services Flat File Rowset Provider      Help file:  DTSFFile.hlp      Help context:  0      Error Detail Records:      Error:  5 (5); Provider Error:  5 (5)      Error string:  Error opening datafile: Access is denied.         Error source:  Microsoft Data Transformation Services Flat File Rowset Provider      Help file:  DTSFFile.hlp      Help context:  0      DTSRun OnFinish:  DTSStep_DTSDataPumpTask_1   DTSRun:  Package execution complete.  Process Exit Code 1.  The step failed.
Avatar of SRigney
SRigney
Flag of United States of America image

You are getting the error.  Error opening datafile: Access is denied.     Most likely the user that the job is running as does not have permissions to something that you have permissions to.
Avatar of tl121000

ASKER

the owner of the job is the domain admin - the job is being run as the domain admin manually - any thoughts?
ASKER CERTIFIED SOLUTION
Avatar of SRigney
SRigney
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
delted and recreated the dts task using the sql account for db connectivity and the domain admin as job owner...

It was set up this way previously - no matter it works now

Thanks,
Tim