Job that uses dtsrun is not working now

• Stringzz

  Ten Centuries

  Points: 1266

  More actions

  November 2, 2011 at 12:46 pm

  #144500

  I have a few jobs that are using the CMDEXEC to run DTSRUN and start a package. These jobs worked fine up until a few days ago. Now the job runs in 2 secs with no errors and these packages take an hour or so to run.

  I remote desktop into server and run the same command line in CMD and it starts and finishes in 2 seconds. The actual packages run fine if they are ran as a package within Enterprise Manager.

  Any ideas what could all the sudden cause these jobs to work correctly?

  _{C:\Documents and Settings\TEMP>DTSRUN /S FTWBIOLAP02 /E /N AutoOCRVerifyImport}

  DTSRun: Loading...

  DTSRun: Executing...

  DTSRun: Package execution complete.

• Lynn Pettis

  SSC Guru

  Points: 442467

  More actions

  November 2, 2011 at 1:25 pm

  #1402395

  Have to ask, has anything changed since the last time everything ran okay?

• Elliott Whitlow

  SSC Guru

  Points: 102402

  More actions

  November 2, 2011 at 3:36 pm

  #1402447

  Are you capturing the output from DTSRUN? I'm guessing that will tell you whats going on, it always helped me..

  CEWII