32-bit package on SSIS 64-bit 9.0.4207

Question

I am running SSIS on 64-bit 9.0.4207.  I have a package created in 32-bit environment, but try to run on 64-bit and get the following error.

 "The task cannot execute in 64-bit environment because the script is not pre-compiled. Please turn on the option to pre-compile the script in the task editor"

I have read this issue was supposed to be fixed in 2005 SP2?

Any helpful suggestions?

Answer 1

Hello,
Try to change Run64BitRuntime option to FALSE in project properties.

Helpful Link:
http://msdn.microsoft.com/en-us/library/ms141766.aspx

Regards.

Answer 2

I am running SSIS on 64-bit 9.0.4207.  I have a package created in 32-bit environment, but try to run on 64-bit and get the following error.

 "The task cannot execute in 64-bit environment because the script is not pre-compiled. Please turn on the option to pre-compile the script in the task editor"

I have read this issue was supposed to be fixed in 2005 SP2?

Any helpful suggestions?

Set the pre-compile property of the script task to TRUE & in scide the script add the line at the start of the script:
OPTION STRICT OFF

---

Hope this helps !! - Sudeep

Answer 3

Hello,
Try to change Run64BitRuntime option to FALSE in project properties.

Helpful Link:
http://msdn.microsoft.com/en-us/library/ms141766.aspx

Regards.

Learner_here's advice is best, IMO.

upressure's advice is easily misinterpreted.  The Run64BitRuntime option in the project properties ONLY APPLIES TO EXECUTIONS IN BIDS.  It does NOT apply to executions via DTEXEC, or SQL Agent.

It is unclear as to how the original poster is running the package in his 64-bit environment, so I thought I'd make that caveat very clear.

---

Answer 4

All,
Thanks for info.  Let me clarify.

I am not running in BIDS, but running pkgs via 32-bit inhouse written Webservice running on the 64bit server, against 64-bit SSIS.  The Webservice is making the call to the DTEXEC, capturing the outputs/logging.

Once I have made the "pre-compile property of the script task to TRUE" (plus those steps) I can run without the error.  We have 100's of packages for migration from older 32-bit 2005 SSIS to 64-bit 2005 SSIS.  I saw older posts / blogs where folk knowledgable with MS claimed this was fixed in 2005 SP2, but is not, as I am on 2005 SP3 + CU#1.

Please let me know if I need to clarify my info or provide other..... THanks.

Answer 5

Were you able to fix this issue in 100+SSIS. I'm facing same issue

Answer 6

Were you able to fix this issue in 100+SSIS. I'm facing same issue

Hi,

please try the Sudeep's suggestion::

"Set the pre-compile property of the script task to TRUE & in side the script add the line at the start of the script:
OPTION STRICT OFF"

Thanks-

---

Let us TRY this | Don’t forget to mark the post(s) that answered your question

Answer 7

go into bids and recompile the script in your 64 bit environment.  Then it should run.  I have had this happen, where compiling it on the 32 bit dev computer, then trying to run does not work.  Had to open it on the server and compile the script.  Not the best solution depending on your access to the production box, but worked for me.

Answer 8

Neea,
No, we abandonded the 64-bit SSIS, went back to 32-bit.  Primary reason was the data connectivity driver set to our legecy data sources.  Our enterprise still has a lot of MS Access databases (multiple older versions) that had packages writen using 32-bit SSIS, using the JET driver.  Having to fix those, plus the recompile of 100's of packages we decided it was best to not update to 64-bit SSIS at this time.  (Believe it or not, this was the advice from our local MS SQL representatives too).

We've had some minor challenges since then, as we still running on 64-bit OS and cluster/node/group, but about 99.9% working.