The Excel Connection Manager is not supported in the 64-bit version of SSIS

As most new PCs are shipping with a 64-bit OS this is becoming a more common error.  I always forget how to resolve this and have to look it up so I thought if I wrote about it in a blog it would help me remember.  So you build your data flow in SSIS, get everything converted and mapped.  Time to test it in Visual Studio and then the dreaded error –

[Excel Source [1]] Error: 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.

[Connection manager “Excel Connection Manager”] Error: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

This issue is easier to resolve than it might appear.  To fix it go into the project’s properties and select Debugging. 


You should see Run64BitRuntime set to True.











To fix the problem just set it to false.  Problem solved.


This entry was posted in SQL Server Integration Services and tagged , , , , . Bookmark the permalink.

54 Responses to The Excel Connection Manager is not supported in the 64-bit version of SSIS

  1. Cromag says:

    Sweet! Can finally test in BIDS!

  2. Ted says:

    You will also have to change it when you deploy it to SQL Server and run it via a job.

    • Tom says:

      Ted (or anyone else still paying attention to this thread), when you say, “You will also have to change it when you deploy it to SQL Server and run it via a job,” what are the steps to change it? Where is it changed when deploying it? Hopefully, this isn’t too stupid a question. I am very new to SSIS. I had the same exact problem described in this post when debugging in BIDS. The solution was as described here. However, the problem persists when I deploy the package and run it via a job.

    • KayBee says:

      Hi, where do I change it when I deploy to SQL Server

  3. Scott says:

    THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  4. amitsuthar8 says:

    Thank you very much!!!!
    I really worried 4-5 hours for this error and finally got solution from you.
    Thanks again!!

  5. Ram says:

    Thanks a ton ! worked like a charm.

  6. Sunil says:

    Thanks a lot! This really helped 🙂

  7. Mark says:

    Thanks for this information. Much appreciated

  8. RK says:

    Thanks a bunch! 🙂

  9. Madhu Reddy says:

    I really happy with trouble shoot fix, because I was strugled halfday about this.
    Madhu Sudhan

  10. Kato says:

    fine, and how can I solve this without a configuration manager?

  11. Appreciate the help! I’m learning to check that switch almost anytime a strange error is thrown.

  12. Pingback: SSIS 64-bit loading data from Excel Error solution 解决64位SSIS下Excel数据加载错误 | Li Guoliang

  13. says:

    than you

  14. Eric says:

    Gracias por la ayuda

  15. Clark says:

    Thanks so much for this. Can’t tell you how much time I wasted trying to figure this out. Thank you!

  16. syed says:

    Excellent it worked like it didnt have any issue earlier 😀

  17. David says:

    A thousand time “thank you”!!!!!!

    Such a simple and obvious fix to an issues that has been driving me mad for hours!

  18. Shahid Iqbal says:

    Thanks, for sharing…

  19. Steven Allen says:

    Yes, but that doesn’t work if you have 64-bit Excel installed on your development workstation. You can’t install or use the 32-bit drivers, which SQL Server Data Tools (BIDS for earlier verisons) requires. Apparently, you can’t develop a package in SQL Server 2012 that uses a 64-bit Excel provider that is 2 years older than the SSIS development environment. When will Microsoft FINALLY give a 64-bit version of Visual Studio? This 32-bit/64-bit crap is over 7 years old and really wearying!

  20. Jehan says:

    Thanks a lot.

  21. pavan says:

    what will be solution if we face this problem while running a job agent?

  22. RS says:

    Thank you for sharing this, I wish all things were this easy to fix

  23. $@mb@ says:

    Thank You Soooo Much!!!!!!!!!!!!!!!!!!!!!

  24. Joao says:

    Tank you so much, very usefull.

  25. Dom says:


  26. Christina says:

    It worked! Thank you so much for your blog!

  27. majid says:

    Thanks Great man

  28. It’s really a cool and useful piece of information. I am satisfied that you shared this useful information with us. Please stay us up to date like this. Thanks for sharing.

  29. Sai says:

    It is working for me in ssis but not when schedules as a job in ssms. I check the option run as 32-bit. But still failing and same error. Please help

  30. Sudhakar says:

    how to run without changing the 64bitruntime property

  31. Marco says:

    Hi everyone, it’s my first pay a quick visit at this web site, and article is in fact fruitful designed for me, keep up posting such articles or reviews.

  32. sadsda says:

    thank you it worked 🙂

  33. tetolww says:

    Wow…Thank you, thank you.

  34. Paramesh says:

    Thank you, it’s working 🙂

  35. learner59 says:

    Thanks…forgotton yet again…But Google led me to you again!

  36. Anonymus says:

    Thanks a Lot You save my Day!!!

  37. Kiya says:

    It is Working, Thanks a Lot.

  38. Azam says:

    This is a very nice post but yet people have issues while running the package through SQL server Job when 64 bit version of Excel is installed. I have also faced the similar situation and after experimenting with options I have found if we run the job step specifically through 32 bit runtime engine then this issue will be resolved. I am not sure it will resolve your issue or not but it had worked for me.

    Open the job –> Navigate to Steps –> Go to your job step properties by double clicking it –> Move to Execution options Tab –> Check the box use 32 bit runtime.

  39. Gangadhar says:

    Thank you sir,
    It’s Working.. 🙂

  40. manmis says:

    Thanks. It worked and helped.

  41. Linda says:

    Thank you soooooooooo much for you post. I picture really helped me find the solution.

  42. Sandi says:

    Thank you sooooo much!

  43. dave_r says:

    Muchas Gracias !!!!
    Rifado carnal !!!

  44. Bhanuja says:

    Thanks a Lot…

  45. codedecks says:

    Thank you!!!

  46. Thank you! It’s really hard to believe that in 2015 we are still dealing with issues such as 64-bit incompatibility.

  47. Karthik says:

    Thanks for the information.

  48. Brian Matanda says:

    This is excellent… Thanks

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s