April 2, 2015 at 10:32 am
I built a SSIS(writing out to a flat file ) in 32 bit machine and it woks fine . But however when I deploy to the produciton server(64 bit) the SSIS writes out garbage data .
After some research I found out that the problem with the 32 bit OS and 64 bit OS problem.
What is my next step. Am I out of luck that now I will have to redesing the SSIS in 64 bit?
April 2, 2015 at 10:52 am
Try going (in VS) to Project -> <Your Proj Name> Properties -> Configuration Properties ->Debugger -> Debug Options -> Turn off 64 bit runtime (set to false) and see if that does it.
I think there is a way to do that on the deployment too but I can't remember.
April 2, 2015 at 11:54 am
lebraix (4/2/2015)
Try going (in VS) to Project -> <Your Proj Name> Properties -> Configuration Properties ->Debugger -> Debug Options -> Turn off 64 bit runtime (set to false) and see if that does it.I think there is a way to do that on the deployment too but I can't remember.
I tried but no it didn't do the trick. Thanks
April 2, 2015 at 12:20 pm
Your package must use some 32-bit component or driver. Try identify it and find a workaround.
If no workaround can be found, force it to run as 32-bit. You should set the Run64BitRuntime package property to False.
If the package is being run by a SQL Agent job, the step properties Execute tab has a "Use 32-bit Runtime" checkbox.
If the package is being run by a DTEXEC command, specify "C:\Program Files (x86)\Microsoft SQL Server\(version)\DTS\Binn\DTEXEC.EXE ..." to run as 32-bit.
If all else fails, run the package on a 32-bit server.
April 2, 2015 at 12:39 pm
Scott Coleman (4/2/2015)
Your package must use some 32-bit component or driver. Try identify it and find a workaround.If no workaround can be found, force it to run as 32-bit. You should set the Run64BitRuntime package property to False.
tried but no success
If the package is being run by a SQL Agent job, the step properties Execute tab has a "Use 32-bit Runtime" checkbox.
If the package is being run by a DTEXEC command, specify "C:\Program Files (x86)\Microsoft SQL Server\(version)\DTS\Binn\DTEXEC.EXE ..." to run as 32-bit.
Will these affect other DTS packages running on the same server using 64 bit?
If all else fails, run the package on a 32-bit server.
April 3, 2015 at 9:02 am
Running a package using the 32-bit version of DTEXEC won't affect any other packages started normally with the 64-bit version.
Unless your package has a "Run Child Package" step that starts another package in 32-bit mode. And even then, I'm not sure which version of DTEXEC the child package would be running under.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply