May 4, 2005 at 9:52 am
I have a DTS job setup that runs fine when you right click on it and the click Execute, but when I schedule the job, it fails with the following output:
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSActiveScriptTask_1
DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1
DTSRun OnStart: DTSStep_DTSDynamicPropertiesTask_2
DTSRun OnFinish: DTSStep_DTSDynamicPropertiesTask_2
DTSRun OnStart: DTSStep_DTSDynamicPropertiesTask_1
DTSRun OnFinish: DTSStep_DTSDynamicPropertiesTask_1
DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1
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.
I have reinstalled MDAC 2.8 and also reinstalled the drivers for the other system that I am pulling from.
Thanks in advance for any responses to this post.
Will
May 4, 2005 at 10:14 am
Are you using a DSN to define the connections?
May 4, 2005 at 10:15 am
At first glance I would check the ODBC connection on the server for that specific data source referenced and make sure the account associated with the sql server service has the correct credentials associated.
May 4, 2005 at 10:40 am
I have my local server, the destination server setup to use the Local System Account to log into windows.
The DTS package uses an anonymous connection to log into the source server, which doesn't require a password.
The SQL Agent wasn't using the Local System Account. I changed it to the Local System Account and rebooted the server and it works now.
Thanks for the replies.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply