I know that this issue has came up on this forum a couple of times, but here's the error that I get when I schedule the DTS task:
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
Error string: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
It's the usual DTS problem - The job runs fine when I run it manually in Enterprise Manager, but fails when it's ran as a scheduled task.
The server is logged in under the system account and I have tried to create the system account in SQL server and then setup the task as running under that account with the same results.
I know that it's probably something to do with the rights of the ODBC connection, but I just can't figure out what.
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSDataPumpTask_1
DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
Error string: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1
DTSRun: Package execution complete.
It's the usual DTS problem - The job runs fine when I run it manually in Enterprise Manager, but fails when it's ran as a scheduled task.
The server is logged in under the system account and I have tried to create the system account in SQL server and then setup the task as running under that account with the same results.
I know that it's probably something to do with the rights of the ODBC connection, but I just can't figure out what.