2/18/14

Share

Microsoft SQL Server Integration Services: Switch package from 64bit to 32bit
0

More

Next Blog

Create Blog

Sign In

Microsoft SQL Server Integration Services

Sunday, 9 September 2012 Search This Blog
Search

Switch package from 64bit to 32bit

Case
My Data Flow Task with an Excel connection doesn't run. It throws the following error: Error: 0xC020801C at Data Flow Task, Excel Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC00F9304. There may be error messages posted before this with more information on why the AcquireConnection method call failed. Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "Excel Source" (1) failed validation and returned error code 0xC020801C. Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS 2008 error example (gives poor hints) Error: 0xC0209303 at GetDataFromExcel, Connection manager "Excel Connection Manager": The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". Error: 0xC020801C at Data Flow Task, Excel Source [8]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: Excel Source failed validation and returned error code 0xC020801C. Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS 2012 error example (gives better hints)

Home Author Contact me SSIS Addons DQS

Blog Archive 2014 (4) 2013 (28) 2012 (38) December (5) November (2) October (6) September (4) Call SSIS 2012 Package within .Net application - P... Who is running the package?

Solution
If you have a 64bit machine, with connections that only support 32bit (like Excel, Access and old ODBC connections) you will get an error like above. The solution is to run your package in 32bit mode. This can be done within Visual Studio for debugging or within SQL Server Management Studio for scheduled packages. This solution will also allow you to debug a Script Task, because that also doesn't work in 64bit mode. BIDS / Visual Studio Running in 32bit mode is a Project Property. Setting it will affect all packages within the project. Right Click the SSIS project and select Properties in the context menu. Go to the Debugging pane and select false under Run64bitRuntime.

How to configure a Foreach Loop Container: ADO Enu... Switch package from 64bit to 32bit August (4) July (3) June (2) May (1) April (4) March (2) February (2) January (3) 2011 (53) 2010 (17)

SSIS 2008

Hire me via

microsoft-ssis.blogspot.in/2012/09/swtich-package-from-64bit-to-32bit.html

1/5

2/18/14

Microsoft SQL Server Integration Services: Switch package from 64bit to 32bit

Labels
ADO AGGREGATE ASSEMBLY

SQL Server Management Studio Edit your job and then edit the right jobstep. Go to the Execution Options pane and check "Use 32 bit runtime". This property will only effect the package (+child packages) called in this jobstep.
SSIS 2012

ASYNCHRONOUS BATCH FILE BDD BEST PRACTICES BIML BUFFER C# CAST CHECKSUM
CODING CONVENTIONS COLLATE

CONFIGURATIONS
CONNECTION MANAGER
CONTINUOUSLY CONVERT CREDENTIAL CRM CUSTOM DATA CONVERSION DATA TAP DEBUG

DECRYPT DENALI CTP1 DENALI CTP3 DEVELOPMENT DOWNLOAD DTUTIL ENCRYPT

ENUMERATOR
ENVIRONMENTS
EVENTLOG EVENTS

ERROR EXCEL

EXECUTE SQL TASK EXPORT COLUMN EXPRESSIONS FILE SYSTEM TASK FOR LOOP FOREACH LOOP FTP GUID HEADER IMAGES IMEX IMPORT COLUMN INDEXES ISNUMERIC JOB JOIN LAST MODIFIED LOOKUP MAIL MERGE PARALLELISM PARAMETERS PERFORMANCE PIVOT PROPERCASE PROXY REFLECTION REGEX RIJNDAEL SCHEDULE

SCRIPT SCRIPT
CONTAINER

COMPONENT TASK SEQUENCE

SERVICES SLOWLY CHANGING DIMENSION SORT SOURCE SQL SQL SERVER AGENT SQLRALLY SQLSAT SSDT

32 bit problems Besides running 64 bit problems there are also 32 bit problems. For example, Fuzzy Lookup will not run in 32 bit. It opens SQLDUMPER.EXE in a command line / dos box but with out errors. The solution for that is to run in 64 bit mode. So running an Excel source and a Fuzzy Lookup within the same package could be a bit of a challenge.
SSMS - Use 32 bit runtime

SSIS 2005

SSIS

SSIS 2008 2012 SSMS

VB.NET

SYNCHRONOUS TASK TEMPLATE TFS TIME DIMENSION TRAILER TRANSACTIONS TSQL UPSERT VARIABLES VALIDATION WAIT WMI EVENT WATCHER TASK XML XSD ZIP

Last 30 days

33,791
Twitter
Follow @ssisjoost

Followers

C:\Program Files (x86)\Microsoft SQL Server 100\Shared\\SQLDUMPER.EXE

microsoft-ssis.blogspot.in/2012/09/swtich-package-from-64bit-to-32bit.html

2/5

2/18/14

Microsoft SQL Server Integration Services: Switch package from 64bit to 32bit
Join this site
w ith Google Friend Connect

Note : For 32bit execution via dtexec.exe you need to pick the right folder: 32bit => C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe 64bit => C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe Note 2: if you use 32bit then the process can use less memory! You might also like:

Members (55) More

Already a member? Sign in

Connecting to Excel (XLSX) in SSIS

Long Validation of SSIS Packages in Visual Studio

BUG: Could not decrypt file

Popular Posts
Linkwithin

Redirect duplicate rows

Geplaatst door Joost Labels: SSIS 2008, SSIS 2012, SSMS
Recommend this on Google

How to use variables in a Script Task Referencing a custom assembly inside a Script Task How to configure a Foreach Loop Container: File Enumerator Sending mail within SSIS - Part 2: Script Task

13 comments:
sunil r 8 October 2012 05:29 I am new to BI. From the solution here I see that we change the properties at the project level in BIDS. This changes properties of all the packages in that project. Is there any way where we can change the properties of the packages in BIDS only to run in 32 bit mode? Reply Replies Joost 8 October 2012 07:31

No it's always on project level within BIDS. If you want it for one specific package, then you can create a separate project within your solution for 32 packages. Reply

Anonymous 30 November 2012 00:12 This worked like a charm! Thanks! Reply

Anonymous 14 December 2012 02:20 Just what I needed. Pulling my hair out until I spotted this. Reply

Anonymous 26 March 2013 16:50 Thank you! Reply

Anonymous 29 April 2013 06:04 Thank you so much for taking the time to document this. By far the best information I could find and fixed the problem immediately. Reply

Anonymous 22 May 2013 04:52

microsoft-ssis.blogspot.in/2012/09/swtich-package-from-64bit-to-32bit.html

3/5

2/18/14
Thank you very much. Reply

Microsoft SQL Server Integration Services: Switch package from 64bit to 32bit

Anonymous 27 May 2013 15:19 Thank you.. This helped.. Reply

Troy Covington 2 July 2013 18:34 Visual Studio 2010 works fine when running on 32 bit, but SQL Server 2012 does not work fine on 32 bit with excel destination. What are your thoughts? Reply Replies Joost 8 July 2013 07:56

What's the Excel version? Which errors do you get? Perhaps post you question here: SSIS MSDN forum Reply

Anonymous 31 August 2013 19:58 thanks!! Reply

Blake Adams 6 November 2013 18:28 This saved the day- THANK YOU! Reply

Anitha Shankar 12 November 2013 19:55 Thanks . Helped me a lot!!! Reply

Enter your comment...

Comment as:

Google Account

Publish

Preview

Please use the SSIS MSDN forum for general SSIS questions that are not about this post. I'm a regular reader of that forum and will gladly answer those questions over there. All comments are moderated manually to prevent spam.

Links naar dit bericht

Create a Link

microsoft-ssis.blogspot.in/2012/09/swtich-package-from-64bit-to-32bit.html

4/5

2/18/14

Microsoft SQL Server Integration Services: Switch package from 64bit to 32bit

Newer Post

Home
Subscribe to: Post Comments (Atom)

Older Post

Awesome Inc. template. Powered by Blogger.

microsoft-ssis.blogspot.in/2012/09/swtich-package-from-64bit-to-32bit.html

5/5