November 12, 2001 at 8:04 am
I recently upgrade my Enterprise Manager to Sql 2000 from 7.0 (client tools only). Since then I've noticed that all 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 it 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
Jeff Matthews
Jeff Matthews
November 12, 2001 at 10:05 am
Are you sure they ran? Dbl check the date and times. I had some issues with the schedules getting disabled.
Otherwise, I haven't noticed this specific issues like this. You might try deleteing the schedule and then rescheduling the item.
Steve Jones
November 12, 2001 at 10:14 am
Yes they are enabled and I'm possitive that they ran. The dates are showing that they ran at the correct time. I have also recreated the package and recreated the schedule job, but those have failed as well.
Jeff Matthews
Jeff Matthews
November 12, 2001 at 10:32 am
November 12, 2001 at 12:19 pm
What version and service pack is your SQL Server? I'm assuming when you say you upgraded Enterprise Manager, you're speaking of a client system.
Also, under what set of client tools were the DTS packages created?
The reason I ask is that the non-encrypted DTS packages were incompatible between SQL Server 7 service packs, but it usually failed out with an error.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
November 12, 2001 at 12:43 pm
Steve,
One of the packages is importing data from a text file, manipulating the data then inserting them into it's appropriate table. The others are exporting and importing data from one sql server box to another.
bkelley,
All of the packages were created under Sql Server 7 sp3. My upgrade was to my Sql Server 7.0 box. I upgrade the client tools only to 2000.
Thanks!
Jeff Matthews
Jeff Matthews
November 12, 2001 at 1:20 pm
Can you create any package and have it run scheduled? (Still reaching here).
Steve Jones
November 12, 2001 at 1:35 pm
Yes, I have some full-text incremental packages that run fine. It's just the ones that are calling DTSRun.exe packages. None of these are working. As a matter of fact, I created one that only ran a small batch command (didn't have anything to do with dtsrun.exe) and this DID NOT run successfully. So maybe it has something to do with batch commands?????
Jeff
Jeff Matthews
Jeff Matthews
November 12, 2001 at 1:41 pm
November 12, 2001 at 1:45 pm
Sql Job that runs a batch command
Jeff Matthews
Jeff Matthews
November 12, 2001 at 1:50 pm
Can you execute (call a dts package) from a store procedure? If so this might be a solution (reaching here).
Jeff Matthews
Jeff Matthews
November 12, 2001 at 2:30 pm
YOu can if you can execute sp_startjob, but this is limited to sysadmins (not sure if anyone else).
Steve Jones
November 12, 2001 at 3:35 pm
Well that didn't work, so I'm back at square one.
Jeff Matthews
Jeff Matthews
November 13, 2001 at 7:15 am
Reaching here as well, but you said you tried a batch command and it failed... Can you successfully run xp_cmdshell from say Query Analyzer? Something simple such as a dir command?
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
November 13, 2001 at 9:19 am
Yes, xp_cmdshell executes successfully.
Jeff Matthews
Jeff Matthews
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply