Sccheduled packages don't run

[Bill Reynolds]

In SQL Server 2000, developer edition (on my desktop), I created a
complex DTS package that truncates several tables and imports fresh
data into them (from Oracle 9i). This package was scheduled and
executed by the SQL Agent with no problem. When I moved the database
to a server, the scheduled job does not run, even though I can
manually run the DTS package successfully. I've recreated the DTS
package, rescheduled the package, and tried to change properties of
the job, all to no avail. I've even uninstalled the developer edition
from my machine and installed the client software from the SQL Server
standard disk.

What do I try next???

Bill Reynolds

[fn]

If you can, go to the server (physically or using something like VNC)
and runs the package in the designer. My guess is that it will fail. And
if it does, it's most likely because the server doesn't have access to
something that you have defined on your machine. This could be any
number of things (mapped drive, TNS file, INI file). But you'll be able
to figure it out by determining which task fails.

FN

Bill Reynolds wrote:

In SQL Server 2000, developer edition (on my desktop), I created a
complex DTS package that truncates several tables and imports fresh
data into them (from Oracle 9i). This package was scheduled and
executed by the SQL Agent with no problem. When I moved the database
to a server, the scheduled job does not run, even though I can
manually run the DTS package successfully. I've recreated the DTS
package, rescheduled the package, and tried to change properties of
the job, all to no avail. I've even uninstalled the developer edition
from my machine and installed the client software from the SQL Server
standard disk.

What do I try next???

Bill Reynolds