"Feruis" wrote:

> Hello Gouti,
> The child package is the last task called in the parent package, and yes, I
> am using an "Execute Package Task". Like I said in my first post, when I
> execute the package in the designer (BIDS), it works like it should. It just
> doesn't work when I schedule it through a SQL Server Agent job or from the
> command prompt.
>
> The protectionlevel property is set to "EncryptSensitiveWithUserKey" on both
> packages and they seem to work well when run from the designer.
>
> Thank you for looking at this issue. I brings some relief to my frustration!!
>
>
>
> "Gouti" wrote:
>
> > Is the child package called using Execute Package task.
> > Check the encryption properties of the packages . In addition, you might
> > also want to see your workflow. Disable the subpackage and connect a test
> > script task or execute sql task and see if it comes there.
> >
> > Are there any other tasks following the subpackage task ?
> >
> >
> >
> > "Feruis" wrote:
> >
> > > Hello,
> > > I have a package that calls another package using the "Execute Package
> > > Task". When I execute the parent package from BIDS or designer, the parent
> > > package calls the child package without a problem. If I execute the package
> > > from a SQL Server Agent job, the child package does not execute. This is
> > > true when the job is of type "SQL Server Integrated Service Package" or
> > > "Operating System (CmdExec)" using "dtexec". I've tried imported both
> > > packages into SQL Server and I've tried it leaving the packages on the file
> > > system and the result is the same.
> > >
> > > I've also tried executing the package from the command prompt using "dtexec"
> > > and still only the parent package gets executed.
> > >
> > > Anyone out there has had the same or similar experience that could provide
> > > me with some information on this issue?
> > >
> > > This is very frustrating and any help on this will be greatly appreciated!!
> > >