SQL Server 2000 Data Transformation Services (DTS)

[Gorthog]

Using SQL Server 2000 Data Transormation Services (DTS), I have created a package which imports data from an external database (Fourth Shift Titanium MDBS) via the OLE DB Provider for ODBC. The package designer produces the following error message whenever I edit the import step:

Package Error
Error Source: Microsoft OLE DB Provider for ODBC Drivers
Error Description: Unspecified Error

After dismissing the error message, I can continue editing the import step without any problems. Also, the package executes successfully when run manually (from within the DTS Package Designer or from the DTS Local Packages context menu).

The problem arises when the package is executed as a scheduled SQL Server Agent Job. Every time the job is executed, the following error is recorded in the Job History Log:

DTSRun:  Loading...    DTSRun:  Executing...
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:  	Specified driver could not be loaded due to system error  126 (Fourth Shift Client-Server).
Error source:  Microsoft OLE DB Provider for ODBC Drivers
Help file:        Help context:  0

Error Detail
Records:
Error:  -2147467259 (80004005); Provider Error:  160 (A0)
Error string:  Specified driver could not be loaded due to system error  126 (Fourth Shift Client-Server).
Error source:  Microsoft OLE DB Provider for ODBC Drivers
Help file:        Help context:  0
DTSRun OnFinish:  DTSStep_DTSDataPumpTask_1
DTSRun:  Package execution complete.  Process Exit Code 1.  The step failed.

Does anyone have any suggestions for resolving this problem?

[brouse]

Just a wild guess, but it could be user permissions. For a test, try changing the login of the SQLSERVERAGENT service to your login, then run the job.

You could also double check the values in your data source objects in the DTS.

[Gorthog]

Chaning the agent account login did not help. The job still produces the error previously posted.