Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-11-15 : 10:03:57
|
| Jeff writes "I recently upgrade my Enterprise Manager to Sql 2000 from 7.0 (client tools only). Since then all of my scheduled jobs that are calling dtsrun.exe's are reporting successful but do not actually run. I think the total process time is 1 sec.The message from View History reports: "The step did not generate any output. Process Exit Code 0. The step succeeded." Every job that uses the dtsrun.exe reports the same message. I've ran the command from DOS and the package runs fine. I can open the DTS package up and manually execute the job from the same server with the same login and it runs fine. I've executed some basic batch commands within the Scheduled Jobs and those fail . Now, I have some other scheduled jobs that do not call dtsruns.exe and those work fine. My production server really depends on these dts packages, so could some please shed some light on this for me.Thanks, Jeff" |
|
|
|
|
|
DTS Scheduled Job reports success but fails