asked on

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.

ASKER CERTIFIED SOLUTION

BartVx

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sqlcurious

ASKER

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
Thanks,

SOLUTION

BartVx

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

BartVx

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

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=13255

sqlcurious

ASKER

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

BartVx

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 Perkins

>>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.

sqlcurious

ASKER

k got it, I got confused, will try the above options and let you know if I come across any hiccups, thanks Bartvx!

sqlcurious

ASKER

Thanks!