Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » Data Warehousing » Integration Services » Error trying to run an SSIS Package
Add to briefcase
12 posts, Page 1 of 2
12»»

Error trying to run an SSIS Package Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
manuelroman98
Posted Tuesday, December 04, 2012 7:47 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 3:26 PM
Points: 21, Visits: 131
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
Post #1392498
Elliott Whitlow
Posted Tuesday, December 04, 2012 8:37 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854, Visits: 4,873
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
Post #1392548
kl25
Posted Tuesday, December 04, 2012 9:16 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 8:40 AM
Points: 241, Visits: 1,097
You may want to check out the article from today about Using SSIS to export data from a 64 bit server to Excel 2007 .

I've tended to use the 32-bit runtime but will be exploring the solution provided in article.
Post #1392567
manuelroman98
Posted Tuesday, December 04, 2012 9:29 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 3:26 PM
Points: 21, Visits: 131
And what do i do to install the 64 bit Jet drivers???

Regards,
Manuel Roman
Post #1392576
manuelroman98
Posted Tuesday, December 04, 2012 9:33 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 3:26 PM
Points: 21, Visits: 131
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
Post #1392579
Elliott Whitlow
Posted Tuesday, December 04, 2012 9:36 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854, Visits: 4,873
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
Post #1392580
Elliott Whitlow
Posted Tuesday, December 04, 2012 9:38 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854, Visits: 4,873
The drivers are here: http://www.microsoft.com/en-us/download/details.aspx?id=13255

CEWII
Post #1392581
manuelroman98
Posted Tuesday, December 04, 2012 9:40 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 3:26 PM
Points: 21, Visits: 131
Thank you very much....
I'll give it a try.

Manuel
Post #1392583
P Jones
Posted Wednesday, December 05, 2012 1:37 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 7:35 AM
Points: 515, Visits: 1,016
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.
Post #1392830
manuelroman98
Posted Tuesday, December 11, 2012 7:41 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 3:26 PM
Points: 21, Visits: 131
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
Post #1395127
« Prev Topic | Next Topic »

Add to briefcase
12 posts, Page 1 of 2
12»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.