Can't seem to run SSIS packages on the 64 bit...
I am connecting to a DB2 mainframe to pull data into SQL 2005. Very simple import. SSIS package works fine on 32 bit. However, once deployed to the 64 bit machine, I get "invalid product license" on the Acquire Connection method. I've worked with IBM support. I have the correct version of the DB2 Connect client installed. The license is there and in the right place. I can connect to the mainframe from the 64 bit server using the DB2 client tools. I just can't seem to execute the package from Integration Services or run a job in SQL Server that executes the package. According to BOL, the package should automatically detect the 64 client I installed. It and the 32 bit client I developed with share the same name/id. Am I missing something? Any hints?
March 1st, 2006 2:32am

I have had multiple problems running packages that were developed on 32 bit and run fine on 32 bit on a 64 bit system. Some of the tools in the tool box, simply to not work. My work around to get these thing to run under the agent is to call them a command line type of job step. the command line should be something like c:\program files\microsoft sql server (x86)\bin\dtexec.......... This ensures that the package is exectuted with the 32 bit dtexec.
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2011 3:15pm

http://msdn.microsoft.com/en-us/library/ms141766.aspxHappy to help! Thanks. Regards and good Wishes, Deepak.
May 7th, 2011 6:44pm

To begin with, try to run the package under 32-bit environment by selecting the "Use 32-bit runtime" check box under "Execution Options" tab of the job step and running the job. If this gives a successful result, that means you don;t have the 64-bit DB2 adaptor installed on your 64-bit server. Download and install the IBM DB2 connector for SQL Server from Mcrosoft download site at this location. Choose the correct version (32 or 64) and ensure it is installed on the server where the SSIS package will run. Once done, open the SSIS package (on the same machine where you installed the connector) in BIDS, remove the existing DB2 Connection managers and create them all over again. While doing this, you should be able to see the newly installed DB2 Driver in the dropdown list to choose from. Once done with tht part, try to execuet the package manually from BIDS and check that it is able to connect to the DB2 server without any hiccups. If this is successful, that means that the DB2 connectivity is working correctly and you have the correct version of the dirver installed (since you'll be doing all this exercise on the 64 bit server itself). However, if this doesn't work, that means you need to look for the 64 bit connector from Microsoft's download site. Finally, having verified that the manual execution of the SSIS package runs fine, set it up as a SQL job and in the Job Step ensure that "Use 32-bit runtime" check box under "Execution Options" tab of the job step is unchecked. Hope this helps. Cheers!! Muqadder.
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2011 7:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics