dbTalk Databases Forums  

Child Package Fails when not all child steps are run.

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


Discuss Child Package Fails when not all child steps are run. in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
miguel.salles
 
Posts: n/a

Default Child Package Fails when not all child steps are run. - 07-27-2006 , 10:14 AM






Hi,
SQL 2000 SP4 DTS
Windows 2003 Server sp1

We have two diferent packages (parent and child) to load text files.
The child package has a condition node that decides if all steps should
be run or only the mandatory ones (the process checks the number of
files to be processed, if it is = 0 the packes exits withou error).
The child package also has a condition node to loop the steps until all
source files have been processed. (Text_Files.Quantity > 0)

When we call the child step manually it works fine no matter if
optional steps where run. (Text_Files.Quantity = Any)

When all child steps run with sucess (at least once) from a Execute
Package Task at the parent both packages work fine. (optional
step.execution Result = 0) (Text_Files.Quantity >= 1)

Whenever we call the child step from a Execute Package Task (from his
parent) and it exits without runing the optional step it fails
(optional step.execution Result = 1). (Text_Files.Quantity = 0)

Can anyone help us?

Thanks a lot.


Reply With Quote
  #2  
Old   
Davide
 
Posts: n/a

Default Re: Child Package Fails when not all child steps are run. - 07-27-2006 , 11:17 AM






Hello miguel.salles,

Quote:
Hi,
SQL 2000 SP4 DTS
Windows 2003 Server sp1
We have two diferent packages (parent and child) to load text files.
The child package has a condition node that decides if all steps
should
be run or only the mandatory ones (the process checks the number of
files to be processed, if it is = 0 the packes exits withou error).
The child package also has a condition node to loop the steps until
all
source files have been processed. (Text_Files.Quantity > 0)
When we call the child step manually it works fine no matter if
optional steps where run. (Text_Files.Quantity = Any)

When all child steps run with sucess (at least once) from a Execute
Package Task at the parent both packages work fine. (optional
step.execution Result = 0) (Text_Files.Quantity >= 1)

Whenever we call the child step from a Execute Package Task (from his
parent) and it exits without runing the optional step it fails
(optional step.execution Result = 1). (Text_Files.Quantity = 0)

Can anyone help us?

Thanks a lot.

How do you implement the 'exit' form the package ?, and the conditional decision
?
Bye




Reply With Quote
  #3  
Old   
miguel.salles
 
Posts: n/a

Default Re: Child Package Fails when not all child steps are run. - 07-27-2006 , 11:46 AM



Hi,

The exit is made by using a Dynamic Properties task to set the
"ExecutionStatus" of the next step to 4.
The condition is:

If filesys.FileExists("File.txt") = false Then
EndProcessGlobalVariable = 4
else
EndProcessGlobalVariable = 1
end if

So I have a activeXScprit task that check if the file exists, after
that a Dynamic Properties task to set the execution status of the next
step to "EndProcessGlobalVariable".

Thanks a lot

Davide wrote:
Quote:
Hello miguel.salles,

Hi,
SQL 2000 SP4 DTS
Windows 2003 Server sp1
We have two diferent packages (parent and child) to load text files.
The child package has a condition node that decides if all steps
should
be run or only the mandatory ones (the process checks the number of
files to be processed, if it is = 0 the packes exits withou error).
The child package also has a condition node to loop the steps until
all
source files have been processed. (Text_Files.Quantity > 0)
When we call the child step manually it works fine no matter if
optional steps where run. (Text_Files.Quantity = Any)

When all child steps run with sucess (at least once) from a Execute
Package Task at the parent both packages work fine. (optional
step.execution Result = 0) (Text_Files.Quantity >= 1)

Whenever we call the child step from a Execute Package Task (from his
parent) and it exits without runing the optional step it fails
(optional step.execution Result = 1). (Text_Files.Quantity = 0)

Can anyone help us?

Thanks a lot.


How do you implement the 'exit' form the package ?, and the conditional decision
?
Bye


Reply With Quote
  #4  
Old   
Davide
 
Posts: n/a

Default Re: Child Package Fails when not all child steps are run. - 07-27-2006 , 04:05 PM



Hi Miguel,

with the Dynamic Properties task i' d set two properties of the step,
ExecutionStatus and DisableStep using two gloabal vars in this way:

File does not exist ---> ExecutionStatus = 3 ( Inactive) and
DisableStep = -1 (Disabled)
File exists ---> ExecutionStatus = 1 ( Waiting) and
DisableStep = 0 (Enabled)

Try

Bye





miguel.salles wrote:
Quote:
Hi,

The exit is made by using a Dynamic Properties task to set the
"ExecutionStatus" of the next step to 4.
The condition is:

If filesys.FileExists("File.txt") = false Then
EndProcessGlobalVariable = 4
else
EndProcessGlobalVariable = 1
end if

So I have a activeXScprit task that check if the file exists, after
that a Dynamic Properties task to set the execution status of the next
step to "EndProcessGlobalVariable".

Thanks a lot

Davide wrote:
Hello miguel.salles,

Hi,
SQL 2000 SP4 DTS
Windows 2003 Server sp1
We have two diferent packages (parent and child) to load text files.
The child package has a condition node that decides if all steps
should
be run or only the mandatory ones (the process checks the number of
files to be processed, if it is = 0 the packes exits withou error).
The child package also has a condition node to loop the steps until
all
source files have been processed. (Text_Files.Quantity > 0)
When we call the child step manually it works fine no matter if
optional steps where run. (Text_Files.Quantity = Any)

When all child steps run with sucess (at least once) from a Execute
Package Task at the parent both packages work fine. (optional
step.execution Result = 0) (Text_Files.Quantity >= 1)

Whenever we call the child step from a Execute Package Task (from his
parent) and it exits without runing the optional step it fails
(optional step.execution Result = 1). (Text_Files.Quantity = 0)

Can anyone help us?

Thanks a lot.


How do you implement the 'exit' form the package ?, and the conditional decision
?
Bye


Reply With Quote
  #5  
Old   
miguel.salles
 
Posts: n/a

Default Re: Child Package Fails when not all child steps are run. - 07-28-2006 , 09:18 AM



Davide,

We have set the Execution Status and Disable Step properties for all of
the optinal steps in the Package and it is now working fine!!

Thanks very much for your help.

I will now anwer some other DTS user in the forum in order to repay my
debt...

Things are going smooth now...


Davide wrote:
Quote:
Hi Miguel,

with the Dynamic Properties task i' d set two properties of the step,
ExecutionStatus and DisableStep using two gloabal vars in this way:

File does not exist ---> ExecutionStatus = 3 ( Inactive) and
DisableStep = -1 (Disabled)
File exists ---> ExecutionStatus = 1 ( Waiting) and
DisableStep = 0 (Enabled)

Try

Bye





miguel.salles wrote:
Hi,

The exit is made by using a Dynamic Properties task to set the
"ExecutionStatus" of the next step to 4.
The condition is:

If filesys.FileExists("File.txt") = false Then
EndProcessGlobalVariable = 4
else
EndProcessGlobalVariable = 1
end if

So I have a activeXScprit task that check if the file exists, after
that a Dynamic Properties task to set the execution status of the next
step to "EndProcessGlobalVariable".

Thanks a lot

Davide wrote:
Hello miguel.salles,

Hi,
SQL 2000 SP4 DTS
Windows 2003 Server sp1
We have two diferent packages (parent and child) to load text files.
The child package has a condition node that decides if all steps
should
be run or only the mandatory ones (the process checks the number of
files to be processed, if it is = 0 the packes exits withou error).
The child package also has a condition node to loop the steps until
all
source files have been processed. (Text_Files.Quantity > 0)
When we call the child step manually it works fine no matter if
optional steps where run. (Text_Files.Quantity = Any)

When all child steps run with sucess (at least once) from a Execute
Package Task at the parent both packages work fine. (optional
step.execution Result = 0) (Text_Files.Quantity >= 1)

Whenever we call the child step from a Execute Package Task (from his
parent) and it exits without runing the optional step it fails
(optional step.execution Result = 1). (Text_Files.Quantity = 0)

Can anyone help us?

Thanks a lot.


How do you implement the 'exit' form the package ?, and the conditional decision
?
Bye


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.