dbTalk Databases Forums  

DTS Package Job Never Completes

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS Package Job Never Completes in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ryan Gregg
 
Posts: n/a

Default DTS Package Job Never Completes - 10-10-2003 , 02:59 PM






I have a DTS package that calls a few other packages and does a lot of data
transformations. Everything seems to run great, except that the package
never finishes executing. When I run it using the DTSRUN command line
program, I see the following at the end of the package:

DTSRun OnFinish: DTSStep_DTSCreateProcessTask_2
DTSRun: Package execution complete.

Yet I never get returned to a command problem. The same problem occurs when
I create an SQL Task to execute the package on a regular basis, the package
executes and runs successfully, but even after everything is done, the job
is stilled listed as running (even hours later).

Any idea what could be causing this behavior?

Thanks,

Ryan Gregg



Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS Package Job Never Completes - 10-10-2003 , 04:24 PM






Try setting everything in the package(s) to execute on the main package
thread through the workflow properties

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Ryan Gregg" <rgregg[at]nospam.wheatlandsystems.com> wrote

Quote:
I have a DTS package that calls a few other packages and does a lot of
data
transformations. Everything seems to run great, except that the package
never finishes executing. When I run it using the DTSRUN command line
program, I see the following at the end of the package:

DTSRun OnFinish: DTSStep_DTSCreateProcessTask_2
DTSRun: Package execution complete.

Yet I never get returned to a command problem. The same problem occurs
when
I create an SQL Task to execute the package on a regular basis, the
package
executes and runs successfully, but even after everything is done, the job
is stilled listed as running (even hours later).

Any idea what could be causing this behavior?

Thanks,

Ryan Gregg





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.