Where you able to find workaround on your issue ?
Kindly update the same here for future reference.
1 of 1 people found this helpful
I had three choices:
1. Change the code to a 64 bit execution
2. Create a 32 bit SQL machine and run the code there
3. Wrap the SSIS into a SQL Agent job and activate inside SQL Agent job the 32 bit execution.
I chose 1.
This is caused by the way Control-M for DB is running SSIS packages , it call dtexec utility. Control-M read the registry of the machine and in the registry is the path for the SQL server installation. If the SQL server is 64 bit it will search for dtexec in the 64 bit path. If you change the registry for 32 bit path all your SSIS will be executed on 32 bit , so basically you have the option 2..
Thanks this is helpful as we are having a similar issue. Some packages depend on the Microsoft access database engine which isn't installed as 64bit. Were going to try installing it before we try the alternatives you suggested.