question

Raj More avatar image
Raj More asked

SSIS will not run in 64 bit mode

I am using Visual Studio 2012 with SQL Server 2012 Data Tools installed. For some unexplained reason, my workstation will only run my SSIS code in 32 bit mode. I created a dummy data flow reading from a RAW file, and writing to another RAW file. Here are my settings: ![alt text][1] It runs `DTSDebugHost.exe *32` - the 32-bit version, although I have both installed on my machine. ![alt text][2] Can you help me figure out what I need to do why it is not running the 64 bit version of DTSDebugHost.exe? [1]: /storage/temp/2125-settings.jpg [2]: /storage/temp/2126-dtsdebughost.jpg
ssissql-server-2012visual-studio-2012
settings.jpg (102.7 KiB)
dtsdebughost.jpg (54.9 KiB)
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Pavel Pawlowski avatar image Pavel Pawlowski commented ·
I know that for SQL 2008R2 this worked properly, Now checked with SSDT 2013 and SQL Server 2014 and the same problem occurs. Also found several other people complaining about this. For normal work this is not a problem, but in case you need to debug a package which needs eg. larger amount of data in the lookups or more complex data flow tasks with larger amount of buffers it can be an issue. I will try to check this on Monday at work on some of our larger projects.
0 Likes 0 ·
Raj More avatar image Raj More commented ·
It turns out that VS2012 is looking for registry entries pertaining to VS2012 under WOW6432-DEVDIV-VS-11.0. Microsoft Support FTW.
0 Likes 0 ·

1 Answer

·
KenJ avatar image
KenJ answered
You may have already gone through *64 bit Considerations for Integration Services* ( https://technet.microsoft.com/en-us/library/ms141766%28v=sql.105%29.aspx). If the following is true for the IDE as well as the command prompt... > By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt Then you may be able to correct this by changing the order of the paths in the PATH environment variable: > To ensure that you run the 64-bit version of the utility at the command prompt, you can take one of the following actions: > > Permanently change the order of the paths in the PATH environment variable by placing the 64-bit path (C:\Program Files\Microsoft SQL Server\100\DTS\Binn) before the 32-bit path (C:\ Program Files(x86)\Microsoft SQL Server\100\DTS\Binn) in the variable.
3 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Raj More avatar image Raj More commented ·
I accepted this answer in haste. This did not resolve my issue. It had absolutely nothing to do with the path, or if 64 bit was installed, but with registry entries pertaining to VS2012.
1 Like 1 ·
Pavel Pawlowski avatar image Pavel Pawlowski commented ·
@KenJ this is not related to the command line execution. This is related to debugging packages in SQL Server Data Tools. The PATH has nothing to do with this. This is related to the Run64BitRuntime in the project settings, but SSDT is not reflecting this somehow.
0 Likes 0 ·
KenJ avatar image KenJ commented ·
Fair enough. I posted it as a comment rather than answer since it was just an idea.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.