I have set up a Job to run several DTS packages, each package is simple and
contains only one step. Basicly it copies a table from another ODBC database
to the SQL server. What occurs from time to time is that the job fails.
I can go into enterprise manager and run the DTS package manually and it
runs fine, but if I click on the job and click on start job, the job
fails. Why would a job fail if the package runs fine manually. I have
looked in the job history and it shows it as failed but gives no good
reason, or maybe I don't understand the reason.
Here is the error message I get but it does not make sense to me.

Executed as user: PLUMASNT\Administrator. DTSRun: Loading...
Error: -2147467259 (80004005); Provider Error: 4064 (FE0) Error
string: Cannot open user default database. Login failed. Error source:
Microsoft OLE DB Provider for SQL Server Help file: Help
context: 0. Process Exit Code 1. The step failed.Executed as user:
mydomain\Administrator. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 4064 (FE0) Error string: Cannot open user
default database. Login failed. Error source: Microsoft OLE DB
Provider for SQL Server Help file: Help context: 0. Process
Exit Code 1. The step failed.

Any help appreciated..
Dennis

In message <#pZ1mp8IEHA.3720 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, Den
<nomail (AT) nowhere (DOT) com> writes
This is due to the change in location and security context when executed
as a job compared to manually.

269074 - INF: How to Run a DTS Package as a Scheduled Job
(http://support.microsoft.com/?kbid=269074)


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org