Today morning i was working with a SSIS package and came across this error while running the package through a SQL Agent Job on a 64 Bit WIn SRV 08 running SQL 08 SP1.

A little more about my dev environment:

My Dev machine is running a 64 bit Win 7 RC with 08 BIDS

My Production machine is running SQL 08 SP1 on Win 08 all 64 Bit.

What I am doing?

Creating a SSIS package to get some data stored in a Excel File (Office 2003 Format) on a remote share to my production warehouse.

What's the Error?

Simply put…

Executed as user: domain/Username. Microsoft (R) SQL Server Execute Package Utility  Version 10.0.2531.0 for 64-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  10:00:00 AM  Error: 2009-05-02 10:00:02.36     Code: 0xC00F9304     Source: PackageName Connection manager "Excel Connection Manager"     Description: 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.  End Error  Error: 2009-05-02 10:00:02.36     Code: 0xC020801C     Source: Remote to Staging 1 Excel Source [521]     Description: 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.  End Error  Error: 2009-05-02 10:00:02.38     Code: 0xC0047017     Source: Remote to Staging 1 SSIS.Pipeline     Description: component "Excel Source" (521) failed validation and returned error code 0xC020801C.  End Error  Error: 2009-05-02 10:00:02.38     Code: 0xC004700C     Source: Remote to Staging 1 SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2009-05-02 10:00:02.38     Code: 0xC0024107     Source: Remote to Staging 1      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  10:00:00 AM  Finished: 10:00:02 AM  Elapsed:  1.857 seconds.  The package execution failed.  The step failed.

Why the error?

Excel Connection Manager is not supported on 64 bit runtime

How I resolved?

1. Open up the Agent Job >> Go to Steps :

2. Double click and Open the Step >> Go to Execution Options and Select Use 32 bit Runtime


You’re good to go.


Comments (33)

  1. Sam says:

    Thanks a lot . such a simple solution neatly told…. worked perfectly… 🙂

  2. Michal says:

    Thank you for this ticket.

    I solved the problem in executing single SSIS, bud i hav not seen the checkbox in Jobs.

    Thank you for that 🙂

  3. Chad Collier says:

    Doesn't work. Get the error:

    Microsoft (R) SQL Server Execute Package Utility  Version 9.00.4035.00 for 64-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Option "/X86" is not valid.  The command line parameters are invalid.  The step failed.

  4. Chad,

    i believe you are using Command line parameter and the command line is not escaped correctly since the command processor strips quotes. You can use "Use 32 bit runtime" in Execution options of the Job or use a escape charector with your command line parameter. something like this…

    /FILE "\servernameSSISPackagesPackageDetails.dtsx"  /X86  /CHECKPOINTING OFF /REPORTING E

  5. kiran says:

    thanks Man . it working 100%

  6. wbargiel says:

    Thanks a lot, it works perfectly !

  7. Jose says:

    Thanks !!!!!!!!!

  8. Terry says:

    Thanks a lot; However if you are working in BIDS and this happems; Open the Project Properties; then under the Debugging properties set the "Run64BitRuntime" property to false

  9. SHAKES says:

    Great Stuff! Thanks heaps for your posting and was put in very plain English!

  10. Selva says:

    .. Or… From your BI Editor, select the project >> Properties. Under Debugging, Set False for Run64BitRunTime.

  11. user says:

    Thanks¡¡¡ it works¡¡¡ 🙂

  12. Ryan says:

    Thanks Terry for the tip on how to get it to work in BIDS!  And great original post!

  13. XyrenNet says:

    Thanks a LOT friend, the solution is perfect..!!!!

  14. sbmanager says:

    Thanks for this.  Saved me from pulling the rest of my hair out.

  15. mkapicibasi says:

    Thanks a lot. It's perfect.

  16. ARUL XAVIER says:

    saved my life thanks!!!!!!!!!!!!!!

  17. shgp says:

    Thank, so much, perfect solution¡¡¡¡, best regard

  18. Fehmi says:

    Thnx. Perfect:)

  19. Mehran says:

    Thank you for taking the time to post this solution.

  20. Nitasha Chopra says:

    Thanks, I had been trying to find out the solution from so many days ….

  21. Grant says:

    Thanks – worked a treat – much appreciated.

  22. piyush jain says:

    thanks a ton . it worked like charm

  23. openritwanz says:

    what a great solution ! thanks bro ..

  24. Roshin Narikkot says:

    Wow thanks!!! Great Solution neatly told.

  25. Naveli says:

    Thanks it really helped 🙂

  26. Jein says:

    Great. Terry/ Selva's tip really helped me to fix the issue in BIDS. Much appreciated friends.

  27. Dilip Chauhan says:

    @Terry 12 Jan 2012 7:02 AM  – Thanks you save my day.!!! Thank you!!

  28. SSIS Dev says:

    Wow..Great!!  Thnks for sharing

  29. Andy Az says:


  30. wil says:

    Thanks man, this stupid setting resolve my epic issue 😛

Skip to main content