I have a problem when I try to execute some DTS packages from SQL Agent jobs.
The DTS Packages collects data from a Paradox (Borland) database located
locally on the SQL Server machine and inserts the data in a SQL Server 2000
database. These packages works perfectly when I Execute them manually in
Enterprise Manager. But when I execute them from a SQL Agent job I receive an
error (11265).

SQL Server and SQL Agent are running under the same account with
administrator rights. This is also the same account I use when I execute the
packages manually in Enterprise Manager with successful results.

I have no problem with other DTS Packages executed from SQL Agent, just the
packages that connects to the Paradox database.

The server runs on Windows Server 2003 sp1.

I hope someone has a solution for this problem.

Hello Johan,

But who owns the job? That could make all the difference.

http://support.microsoft.com/?kbid=269074

Allan

Hello Allan,

It's the same account that runs both SQL Server and SQL Agent that owns the
job.

To me it doesn't seem to be a security problem, because everything else
works perfect. Or are there specific security settings in Microsoft Jet 4.0
or perhaps in the Borland engine that stops the DTS from executing tasks on
the network, when started from SQL Agent?

"Allan Mitchell" wrote:

Hello Johan,


Where are you when you fire the package from EM.? On your PC then you bring
the package to your PC, it is not on the server. As a job it is on the server.
Could it be that the resources (Driver etc) are on your PC and not on the
server?

Allan

Hello again,

I am on the server. I created the job via Remote Server access, but I have
also tried to fire it sitting by the actual server. It's the same result.

Unfortunately I am not responsible and have no control over the network and
server configuration. My customer uses a different company for that.

I have also made a Windos Schedule Task to fire the DTS package and that is
now working after a month of failures. The network guy visited my customer
yesterday and even if he said he didn't change any settings I believe he did.
How could it else be that the Windows Schedule Task is now working again??
But still, firering the DTS-package from an SQL Agent job doesn't work. I
would of course prefer to have it run from SQL Agent since it gives me more
control over the flow.

//Johan

"Allan Mitchell" wrote: