none
Microsoft.ACE.OLEDB.12.0 xlsx External table is not in the expected format large file RRS feed

  • Question

  • Originally I thought this was a file size / memory limit issue with the specific windows version & ACE.OLEDB version, because I split the large file into small files, and all the data was successfully read - i.e. it wasn't some sort of corrupt data/file issue(the actual error message was vague, and about a formatting issue, not memory). *this was all through task scheduler.

    Then, a while later I had to read another large file, but tried executing the application that reads it myself, instead of through the Task Scheduler. It just worked.

    So now I think the problem is some sort of memory limit with processes started through task scheduler.

    Here is a similar post from many years ago, though a different OLEDB adapter, nearly identical problem. No solution mentioned in that thread.: https://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?forum=adodotnetdataproviders

    Any ideas? Thanks

    Friday, December 1, 2017 4:16 PM

All replies

  • Can you post code so we can actually see what you are doing? I'm assuming you are attempting to open a connection (to Excel?) but beyond that, no clue.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Friday, December 1, 2017 9:03 PM
  • Hi kwarren12345,

    As Paul said, I would suggest that you could provide a bit more information about the issue, such as related code, connection string, excel records. or a simple demo which could reproduce the issue. it would be beneficial to resolve the issue.

    In addition, based on the error message, the following similar issue for your reference.

    https://stackoverflow.com/questions/40787308/ace-oledb-external-table-is-not-in-the-expected-format-with-large-text-in-exce

    https://www.codeproject.com/Questions/537510/Externalplustableplusisplusnotplusinplustheplusexp

    Note: Please remove privacy information before share the information.

    Best regards,

    Zhanglong Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, December 4, 2017 7:11 AM
    Moderator
  • Paul, yes, it's about reading xlsx files with ace oledb connector. To clarify a little, it happens to be a C# program, but I don't see that a significant factor.

    Eventually the data is retreived with this select query: "SELECT * FROM [" + sheetName + "]";

    I already have/had the connection string properties mentioned in Zhanglong's post/links.

    I'll try to summarize it, maybe it was too wordy to follow: There seems to be a memory limit when the program is run through task scheduler. *Can anyone think of a reason why running the program through task scheduler would cause the problem, when double clicking the exe there is no error.

    And, again, the link in the original/first post is of someone having almost an identical problem with a different oledb connector, unfortunately that post, though has some discussion, has no solution (from 2009).

    link in the original/first post:  https://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?referrer=http://social.msdn.microsoft.com/Forums/en-US/215c5f1a-664d-41e5-9490-044e04b1a61e/paradox-5x-external-table-is-not-in-the-expected-format?forum=adodotnetdataproviders

    Tuesday, December 5, 2017 2:00 PM
  • The exception you posted doesn't sound like a memory error - it's a problem opening the Excel file. Does the exception occur when the application starts running or does it take a while before it occurs?

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Tuesday, December 5, 2017 4:05 PM