Excel connection manager Error while running a package on a server

Hi experts, I have a problem where my package runs on my local drive but when I put it on a server where excel is not installed, it throws an error, not sure what the workaround is, the package here that I have creates an excel file with a tab and headers and later dataflow task to export data to excel. I have had packages created on the same server where I had data imported from excel files but I dont understand why we cant do it the other way....
Appreciate your help...

ERROR MESSAGE[Execute SQL Task] Error: Failed to acquire connection "Excel Connection Manager". Connection may not be configured correctly or you may not have the right permissions on this connection.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I can think of two possible causes:

1) the user running the package does not have sufficient access rights on the Excel file.

2) You are running the package in 64 bit mode on the server. The OLEDB provider to connect to Excel files is not available in 64 bit.
Check the "Running integration services packages on 64 bit computers" section in following link for more information about running packages in 32/64 bit mode:


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sqlcuriousAuthor Commented:
Hi Bartvx, its not the case 1 and regarding the option 2- I have already turned off the 62 bit option. There is something else that's happening
Are you trying to connect to Excel 2007? If so, install the Office 2007 Data Connectivity Components from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23734
 on the server.

If this is not the case, let's make sure the 64 bit issue is not the problem:

If you mean the Run64BitRuntime  option in the debugger options: Thi option only applies at design time and will have no effect when you execute the package on the server.

If you launch 'dtexec' command  in a command prompt without parameters on the server, what can you see in the version section?

If it says 64 bit, try to locate the 32 bit version of dtexec (typically in C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn. (note the X86 part) Then try to execute the package explicitly specifying the path to the 32 bit version.

ex: "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec" /f c:\mypackage.dtsx

Some more questions to make finding the solution easier:
What version of SQL are we talking about?
What are the versions of dtexec on your local PC and on the server?
What provider do you use to connect to Excel?
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Addendum: for Excel 2010 the installation of Microsoft Access Database Engine is required, you can download it here:


sqlcuriousAuthor Commented:
I am not allowed to install any office products so the solutions above wouldnt work, please provide me alternative solutions.
Hi Bartvx answers to ur questions:
What version of SQL are we talking about?  - SQL server 2008 R2
What are the versions of dtexec on your local PC and on the server? both are the same
What provider do you use to connect to Excel? - excel connection manager

As far as I know there is no way to connect without those drivers installed. :(

The only other option that I see is that you run the package on another computer (with connection to the database on the target server) where you are allowed to install the Office drivers.

Note that the links I posted are not the actual Office products, but merely the office connectivity tools which are free to download.
Anthony PerkinsCommented:
>>I am not allowed to install any office products<<
Thank goodness for that.  Suggesting you install MS Office on a Production SQL Server is dangerous at best.
sqlcuriousAuthor Commented:
k got it, I got confused, will try the above options and let you know if I come across any hiccups, thanks Bartvx!
sqlcuriousAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.