Unable to run SSIS package on 64 bit machine with 32 bit dtexec.exe

Question

Unable to run SSIS package on 64 bit machine with 32 bit dtexec.exe

Shaira

SSCrazy

Points: 2432
More actions
August 27, 2010 at 12:47 pm

#237256

I have read and tried every example provided in the post under
SQL ‘05/SQL ’05 SSIS/Unable to run SSIS … with dtexec.exe

but have been unable to get my SSIS package to run via a batch file – I’m really hoping there’s someone out there who can help …
I am running SQL 2008 sp1. I’ve created an SSIS package and have changed the run64Bitruntime to False (have to run as 32-bit). I have a batch file that 1-creates a backup of a flat file, then 2-kicks off the SSIS package. The backup gets made but the package never kicks off.
I can run the package directly in SSIS, as a job in SSMS, and from a command line (dtsrun packagename) - but not using a batch file.
I have saved the package with EncryptSensitiveWithPassword and then imported it into File System. My latest try looks like this:
"C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec.exe" /dts "\File System\myPackageName" /SERVER myServerName /DECRYPT myPassword /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V /CONSOLELOG NCOSGXMT
My packages are at C:\Users\me\Documents\Visual Studio 2008\Projects\xxx\myPackage.dtsx … permissions issues (but with who??)? 64/32-bit issues?
Having worked on this for days now I’m at wits end – any suggestions??
TIA!!!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Todd McDermid Default port Points: 1416 More actions · Answer 1

I'm afraid most of the posts in that thread refer to protectionlevel, not bitness. And most information posted on the internet about running packages as 32-bit on 64-bit architectures is either incorrect or if correct, very misleading.

Read this, and let me know if that doesn't help: SSIS in 32- and 64-bits

Todd McDermid - SQL Server MVP, MCTS (SQL 08 BI), MCSD.Net
My Blog - Dimension Merge SCD Component for SSIS - SSIS Community Tasks and Components

caladba SSCommitted Points: 1514 More actions · Answer 2

I ran into the same issue and the following steps worked for me.

Right click on the job and open the properties.

Go and edit the job step where the package is being executed.

Go to Execution Option tab under Run as drop down.

Uncheck the Use 32 bit runtime checkbox at the bottom.

Hope this works for you too.

caladba SSCommitted Points: 1514 More actions · Answer 3

Oops, it seems like you have the opposite problem.

Right click on the job and open the properties.

Go and edit the job step where the package is being executed.

Go to Execution Option tab under Run as drop down.

updated: Make sure that the Use 32 bit runtime checkbox is checked. 🙂

Shaira SSCrazy Points: 2432 More actions · Answer 4

Thanks for the replies!

Todd ~ the link to the article you provided was great. I used the DTExecUI, which provided me almost the exact string I needed to run the job from a batch file - I just had to add the /DECRYPT mypassword to the string and the bat file fired off without a hitch. Thanks so much!!