"Charles Kangai" wrote:

> I have seen a similar error when a Unicode file was mistakenly specified as
> non-unicode, or vice versa. This does not appear to be the problem in your
> case as you have not changed anything in the file manager specification.
>
> Check the LocaleID setting of the parent task to see whether it is
> consistent with the child package's LocaleID property.
>
> You can also try and change the ExecuteOutOfProcess property of the Execute
> Package task to True and see whether that makes any difference.
>
> Charles Kangai, MCT, MCDBA
>
> "Pat" wrote:
>
> > Windows 2003 x64
> > SSIS 2005 x64 SP1 + hotfix 918222
> >
> > I have a number of packages that import csv files from various sources. When
> > I run these packages independently from Visual Studio using "Execute
> > Package", they work fine.
> >
> > I need to have them all run in sequence, so I created a super-package that
> > contains one "Execute Package Task" for each of those csv-import packages.
> >
> > Now when running inside the super-packages, the csv-import packages come up
> > with casting errors, for instance:
> > Error: 0xC0047062 at Load CSV File, Script Component [1651]:
> > System.InvalidCastException: Conversion from string ":4" to type 'Integer' is
> > not valid.
> >
> > Again, running the package on its own, with the same input file, causes no
> > error and the package terminates successfully.
> >
> > Could it be a locale/region setting problem ?
> > Is a packet running inside another package running under another
> > windows/domain account ?
> >
> > All of this inside Visual Studio, and all packages stored on the file
> > system, nothing deployed yet.
> >