Recently upgraded from 2000 to 2005. Running DTS jobs until we have time to
convert to DTS packages to SSIS. Several times we have gotten a "false
success" on several jobs. By "false success" I mean that the job reports
success, but it actually did not run or do anything. The message we get in
the job is....'Executed as user: <username>. DTSRun: Loading... DTSRun:
Executing... DTSRun: Package execution complete. Process Exit Code 0. The
step succeeded.' As opposed to this message, when the job actually runs
(failure or success) we normally get several lines of detailed run info.

We have verified that the job has not actually done anything. Data does not
get loaded, tables are not deleted or created, etc... It is happening
intermittenly with several different jobs, and not the same job on a daily
basis. It seems to happen to a job that is running at the same time as
another DTS job or TranslogBackup job. The schedule name happens to be the
same name like "Daily 5:30am".

We are running SQL SERVER 2005 64bit Enterprise with SP3 applied on Windows
2008 Server (clustered). The packages are run from the job using the
command...'DTSRun /S <server>\<instance> /E /N "DTSPackageName"'.

We may try to stagger the start times of these jobs, where we can, and see
what happens.

I appreciate any suggestions or being pointed to any links that may be
related to this.

Thanks!

John