Error trying to run an SSIS Package

Question

Error trying to run an SSIS Package

manuelroman98

Mr or Mrs. 500

Points: 593
More actions
December 4, 2012 at 7:47 am

#149664

Hi Forum
I getting the following error:
SSIS Error Code DTA_E_OLEDB_EXCEL_NOT_SUPPORTED: The
Excel Connection Manager is not supported in the 64-bit vesion of
SSIS, as no OLE DB povider is avalable.
I've done everything that i can think of on the SQL server side and nothing works.
I am trying the SSIS windows launcher app that i found and i am still getting the same reuslts.
Any clue on what i am doing wrong or i might be missing?
Regards,
Manuel Roman

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102296 More actions · Answer 1

The error message tells the tale.

You are running it with the 64-bit run-time, unless you have the 64-bit jet drivers installed it will NEVER work this way. your choices are to install the 64-bit jet drivers or use the 32-bit run-time.

CEWII

kl25 Hall of Fame Points: 3752 More actions · Answer 2

You may want to check out the article from today about Using SSIS to export data from a 64 bit server to Excel 2007 [/url].

I've tended to use the 32-bit runtime but will be exploring the solution provided in article.

manuelroman98 Mr or Mrs. 500 Points: 593 More actions · Answer 3

And what do i do to install the 64 bit Jet drivers???

Regards,

Manuel Roman

manuelroman98 Mr or Mrs. 500 Points: 593 More actions · Answer 4

OK, i am trying to use the SSIS Windows Launcher application but i guess it is not using the 32 bit DTExec.

Even though we have both drivers installed on the server it is not picking up the default driver for whaterver reason.

I just don't want the user to manually run the imports (SSIS packages).

Regards,

Manuel Roman

Elliott Whitlow SSC Guru Points: 102296 More actions · Answer 5

I'm reading that article now, the first thing I would say is the section where we set the debug setting Run64BitRuntime is ONLY applicable to BIDS, when the package is run by the runtime in the server this setting is ignored.

MY experience has been you want to install the x64 bits on 64-bit servers or you basically need to use the 32-bit runtime, this has worked without fail for me..

CEWII

Elliott Whitlow SSC Guru Points: 102296 More actions · Answer 6

The drivers are here: http://www.microsoft.com/en-us/download/details.aspx?id=13255

CEWII

manuelroman98 Mr or Mrs. 500 Points: 593 More actions · Answer 7

manuelroman98

Mr or Mrs. 500

Points: 593

December 4, 2012 at 9:40 am

#1565401

Thank you very much....

I'll give it a try.

Manuel

P Jones SSChampion Points: 12353 More actions · Answer 8

If you are running the SSIS packages from SQL Agent, just tick the 32 bit runtime box on the Execution Options tab

I had this problem with an Access DB import and it fixed it because there weren't any 64 bit JET drivers.

manuelroman98 Mr or Mrs. 500 Points: 593 More actions · Answer 9

Hi,

I've installed the drivers and i am still getting the same message...

I am using the SSIS Windws Launcher application that i got from CodePoject... i just tweeked it a little bit and compiled it to run it on my server...

It is supposed to run the default 32 bit DTExec and it is running the 64 bit instead.

If i run it using the Execute Package Utility works fine, but i don't want the user t run it this way.

Regards,

Manuel Roman

Elliott Whitlow SSC Guru Points: 102296 More actions · Answer 10

How is that project compiled? Is it set for 64/32 or both, if its not explicitly set I think it will use 64 on a 64 bit OS and 32 on a 32 bit OS, you might have to force it to one for your purposes.

CEWII

manuelroman98 Mr or Mrs. 500 Points: 593 More actions · Answer 11

Hi Elliott,

You have a point... let me try that.

Thanks

Manuel