Hi I have a website built in visual studio 2005 which executes an ssis package using LoadPackage() and Execute() functions in VB.NET. The package was built using visual studio 2005 on a 32 bit server and has an excel source and excel connection manager. We have now migrated to a new 64 bit server running visual studio 2008. The package does not execute anymore. I understand this is the problem with the unavailability of support for excel connection managers here. I have seen various posts suggesting to run the package in 32 bit mode. I tried it manually as an SQL server job and it ran successfully. But how do I run it programatically in 32 bit mode in VB.NET?

It might be the PATH environmental variable, check if the path to the 64 bit is not preceding the path to the 32 bit SSIS.Arthur My Blog

If your "host" process written in VB.Net is 64-bit, then you have two options: 1. Run your "host" process in 32 bits. If you do that, then the API functions will be run in-process, using the correct bitness. 2. Instead of using the SSIS "Execute" API function, save your package to disk and spawn a 32-bit process to run DTExec on that package. Talk to me now on