I recently builta SQL Server x64 server, whereI changed the default install path of SSIS. My reason for doing so was to move the SSIS engine off of the system volume, onto a different set of spindles, to reduce potential contention between the OS, the SQL Engine and the SSIS Engine. It is also documented in BOL as an option for the components. The 64-bit runtime installed fine on the new volume, however, the 32-bit runtime was not installed at all. I checked Program Files (x86) and the directories I chose during the initial install, but only the 64-but runtime exists on the server. Since 64-bit drivers are limited (to put it mildly), I would say about half of the packages I run through jobs require execution of the 32-bit runtime to work. BOL doesn't seem to indicate that the 32-bit will not install if the default is changed, but the following note indicates that I would not even be able to uninstall/reinstall the components back to the system drives: A single installation path is shared between SQL Server Integration Services, Notification Services, and Client Components. Changing the installation path for one component also changes it for other components. Subsequent installations install components to the same location as the original installation. Iam wondering if there is a command-line install option to ensure the 32-bit runtime is installed, or if there is a way to install the 32-bit SSIS runtime manually. And if not, can the registry be edited to force a re-install back to the default path? Any ideas?

With some help from Microsoft (thanks, Rob), I was able to determine the issue here, and wanted to share the solution in case someone else runs into it. When installing SSIS in a 64-bit evironment, to ensure a 32-bit installation is also required, you must install SSIS and BIDS. Installing SSIS and not BIDS will only install the 64-bit engine. In my particular scenario, I saw no good reason to install SSMS, BIDS, or any other client-type component on my production server. It seems more of a security risk to me to install components that are not required. So, I chose to install only the SQL Engine and SSIS, and nothing else. I also chose a different volume for the SSIS engine. When I discovered that 32-bit was not installed (and I needed it for several SSIS packages), I had assumed that it was the selection of a different path that was the reason for the missing 32-bit \90\DTS\ directory. In fact, it was not selecting a BIDS install resulted in the 64-bit-only installation. The following article: http://msdn2.microsoft.com/en-us/library/ms141766.aspx does mention this: When you install SQL Server 2005 and select both Integration Services and Business Intelligence Development Studio, all available 32-bit and 64-bit design-time and run-time Integration Services features are installed. When you install Integration Services, you also install 32-bit run-time support for SQL Server 2000 Data Transformation Services (DTS) packages. I guess I would have appreciated a note on what happens when you don't select both, but that is the answer. Hope this helps someone else!

Thanks for the follow-up, esnajder!

I've been bouncing around a few threads like this, if someone else comes across this, I worked around my problem by running this cmd. You can schedule cmds from server agent "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec.exe" /F "C:\some folder\yourDtsxFileHere.dtsx"- Michael