scheduled DTS package failure

[vionca]

Hi there,

I'm receiving the error below whenever I schedule a package to run via the SQLserverAgent:

Executed as user: remdomain\vionca. ... OnStart: Drop table customer_tbl Step DTSRun OnFinish: Drop table customer_tbl Step DTSRun OnStart: Create Table customer_tbl Step DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: Create Table customer_tbl Step DTSRun OnStart: Copy Data from Results to customer_tbl Step DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_3 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_2 DTSRun OnError: Copy Data from Results to customer_tbl Step, Error = -2147467259 (80004005) Error string: [ProvideX][ODBC Driver][FILEIO]Table is not accessible Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 12 (C) Error string: [ProvideX][ODBC Driver][FILEIO]Table is not accessible Error source... Process Exit Code 19. The step failed.

----------------------------------------------------------

If I am logged in as remdomain\vionca and I right click on the package and execute it, I have no problem. The package runs successfully. If I then schedule the package to run, the error above appears.

I'm wondering if perhaps I'm missing something obvious, or if this has something to do w/ the driver I'm using which is for a ProvideX database and requires an ODBC driver which is installed on the server.

Any ideas or suggestions?

Thanks,
Vionca

 

[MDXer]

I get the [ProvideX][ODBC Driver][FILEIO] error as well and after talking with the people who design and maintain the system I am pulling from we determined it was on the providex side.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[vionca]

Thanks for letting me know!

 

[vionca]

In case anyone is receiving a similar error, here's the solution:

1st: set up the datasource as a system DSN rather than a user DSN

2nd: don't use the mapped drive as the database directory under the DSN configuration. Rather, use the UNC. e.g. \\mas90filesrv\shareddir


Also, I'm not sure of the impact these selection have in this particular scenario, but I've checked off Burst mode, Dirty Read, Silent mode.

I'm no longer seeing the error,
Vionca