locked
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine. error to process excel file RRS feed

Answers

  • User1292358045 posted

    Thanks, you inspirited me to check driver versions.

    the 64bit odbc driver is 14.0.0, the 32 bit odbc driver is 12.0.0, I changed connection string to Provider=Microsoft.ACE.OLEDB.12.0 (although project is compiled to any CPU, and target app pool is runned on 64-bit) it works

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, April 3, 2015 12:25 PM

All replies

  • User1428246847 posted

    I can't help you but installing the full office suite will not help; I get this type of errors on systems that have the full office suite installed.

    I don't know if you found this one during your research: https://social.msdn.microsoft.com/Forums/en-US/b5a79958-5bce-4229-a69f-75589b6240a8/faq-item-solution-fails-on-64-bit-system-with-error-microsoftjetoledb40-provider-is-not?forum=adodotnetdataproviders

    Thursday, December 18, 2014 5:47 PM
  • User1292358045 posted

    Thanks, I would give it a try later. However, if compile to 32-bits application could work, I wonder why on develop machine (also a 64-bit OS) the application works with <any cpu> compilation options

    Thursday, December 18, 2014 6:03 PM
  • User1292358045 posted

    Still, if I just compile to x86 code, same error message, if I checked enable 32-bit applications, application pool crashes.

    I checked the event viewer to see why application pool crashed, it seems the url rewrite module (inetsrv/rewrite.dll) fail to load, however, 32-bit version of url-rewrite cannot be installed since this is a 64-bit OS, I am stuck again.

    Friday, December 19, 2014 12:05 PM
  • User1644755831 posted

    Hi Cheng Bao,

    1. Check if ODBC Data Provides exists for the Excel Files.

    1. Go To Control Panel > Administrative Tools > ODBC Data Sources

    One of the reason could be that you haven't added excel data sources Under USER DSN.

    Hope this helps.

    With Regards,

    Krunal Parekh

    Friday, March 6, 2015 4:34 AM
  • User753101303 posted

    Hi,

    Not sure as you are talking about the "same error message" but note that this is not enough. You have to update your code to use the driver you installed rather than Jet.

    Also make sure to download the appropriate version (ie the 64 bit version if you are in 64 bit mode).

    Friday, March 6, 2015 7:10 AM
  • User1292358045 posted

    I do have Microsoft Excel drivers installed in ODBC.

    I can't add an DSN entry because it is not a static data source, I need process dynamic, uploaded excel files, which name/path I don't know in design time.

    Thursday, April 2, 2015 6:04 PM
  • User753101303 posted

    Hi,

    Could you confirm that you are in x64 bit mode, that you installed the corresponding x64 exe and that you changed the connection string to use Microsoft.ACE.OLEDB.12.0 ?

    What is the current error message ?It shouldn't mention any more 'Microsoft.Jet.OLEDB.4.0' if you followed the correct steps but I was confused as you talked about "having the same error message".

    Friday, April 3, 2015 4:28 AM
  • User1292358045 posted

    Thanks, you inspirited me to check driver versions.

    the 64bit odbc driver is 14.0.0, the 32 bit odbc driver is 12.0.0, I changed connection string to Provider=Microsoft.ACE.OLEDB.12.0 (although project is compiled to any CPU, and target app pool is runned on 64-bit) it works

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, April 3, 2015 12:25 PM