Post reply

Trouble import excel file to SSIS 2012

  • January 14, 2014 at 12:50 pm

    #288328

    I'm trying to import an Excel97-2003 file to SSIS 2012

    I get the following error when I execute the package.

    In addition I can only preview the SQL command result when the excel sheet is open.

    In advanced editor I've managed to map the columns succesfully.

    I've tried using IMEX=1; HBR=YES with no success. I'll be greatful for any help.

    Errors

    [Excel Source [2]] Error: No column information was returned by the SQL command.

    [SSIS.Pipeline] Error: Excel Source failed the pre-execute phase and returned error code 0x80004005.

  • January 29, 2014 at 12:12 am

    #1684150

    HI,

    If you are using 64bit OS, better do the following step

    Right click on Project and select properties. select debugging and make Run64bitRuntime False.

    also try to check Delayvalidation ( u can find this under solution Explorer we have properties) as True.

    Save this changes and try to use excel sheet. Hope this will work.

    Best Regards,

    VijayVanamala

  • January 29, 2014 at 12:16 am

    #1684153

    vijay.sap1255 (1/29/2014)

    HI,

    If you are using 64bit OS, better do the following step

    Right click on Project and select properties. select debugging and make Run64bitRuntime False.

    also try to check Delayvalidation ( u can find this under solution Explorer we have properties) as True.

    Save this changes and try to use excel sheet. Hope this will work.

    DelayValidation has only an effect when you use expressions on the connection manager.

    @Al.guidi: does the SQL command return the column names?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 29, 2014 at 7:44 am

    #1684327

    The sql command does return the column names only when I have the document open on my desktop, eitherwise I get an error message when I try setting up the excel source when the document is closed.

    If the document is not opened before I do that, I get a corrupt document error message if I try to open it after configuring the excel source.

  • January 29, 2014 at 7:48 am

    #1684328

    can you try explicitly saving the document as excel 2003-2007?

    i've had a similar situation where a csv or html file was saved with an xls extension, so it was not a valid excel document, and only by opening nad saving the doc did it become something i could open correctly.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • February 11, 2014 at 9:21 am

    #1687969

    @SSChampion

    Converting to xlsx solved the issue. Thank you very much.

Viewing 6 posts - 1 through 5 (of 5 total)

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