locked
Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine - still an urgent problem in .net app RRS feed

  • Dotaz

  • I urgently need a workaround for the 32bit Office365 problem on a Windows Server 2019 64bit hosted virtual machine.

    We had to uninstall O365 64bit on the server and install 32bit version, as the access back-end database to our MS Access app was getting corrupted and the app kept on crashing/hanging and nobody could get any work done.

    However, since the downgrade, I have a visual studio .net app that processes emails (microsoft hosted exchange in the cloud), gets and saves the attachments and makes entries in a table in our Access database using oledb provider, which now does not work. Even after trying every fix, workaround found on every forum covering this long running problem! The .net app is re-compiled for 32bit. I have installed the 32bit 2010 access database engine (even though O365 32bit is installed on the server), but I still get the ACE.OLEDB error.

    What I don't understand is that I can setup a Data Source in visual studio to the backend database (and it uses oledb) and I can see the tables and fields, and even preview the datarows from any table I have setup in the Dataset (it uses myDataSet.Setup.Fill,GetData () evidently!)

    However as soon as the app runs and I try to use the oledb connection.open method, or open a test form which has the dataset, binding sources, table adaptors etc. and a datagrid to show the rows in one of the table, the exception is thrown and I cannot go any further.

    How does the Visual Studio Data Sources IDE get around this problem, but the app cannot at runtime? What is the fix for this urgent problem.

    OR....how do I use Microsoft.Exchange.Webservices dll in an MS Access app to get the job done in Access itself then???

    Thanks,

    MJ


    Mike

    úterý 17. listopadu 2020 14:28

Všechny reakce

  • office 365 forum migrated to mentioned below link 

    1. https://docs.microsoft.com/en-us/answers/index.html

    if issue resolve please mark as answer

    úterý 17. listopadu 2020 15:20
  • No, our Office 365 32bit works fine (just slower).

    It is a problem with .net oledb provider that seems to be confused!

    If I pose this question in the Office 365 forums, I will be told to redirect it here or other .net forums, like several others who have had this problem were told to!

    I need someone in Microsoft to finally state what registration key is missing or incorrect.

    I have followed every proposed solution or workaround on every forum available, to no avail.

    Also, I need to know why Visual Studio Data tools has no problem talking to the access database when setting up a data source for the application, but the application in run-time throws the exception! That is not a question for O365.

    Mike

    středa 18. listopadu 2020 6:00
  • No, our Office 365 32bit works fine (just slower).

    It is a problem with .net oledb provider that seems to be confused!

    If I pose this question in the Office 365 forums, I will be told to redirect it here or other .net forums, like several others who have had this problem were told to!

    I need someone in Microsoft to finally state what registration key is missing or incorrect.

    I have followed every proposed solution or workaround on every forum available, to no avail.

    Also, I need to know why Visual Studio Data tools has no problem talking to the access database when setting up a data source for the application, but the application in run-time throws the exception! That is not a question for O365.

    Mike

    středa 18. listopadu 2020 6:00
  • Hi MickJack,
    Based on your description, you need to download and install Microsoft Access Database Engine 2010 Redistributable.
    There are more discussion in this thread you can refer to.
    Best Regards,
    Daniel Zhang


    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.

    středa 18. listopadu 2020 9:00
  • you have 32 bit Office on the server, therefore you don't have the 64 bit access engine, if you use the Access engine from a 64 bit app without the 64 bit engine, you will get this error.

    Visual Studio is 32 bit. 

    If you want to use Access engine from a 64 bit app, uninstall all 32 bit Office components and reinstall 64 bit counterparts. But then you lose the ability to use the engine in 32 bit apps (e.g. Visual Studio). 



    Visual C++ MVP



    čtvrtek 19. listopadu 2020 4:51
  • Hi MickJack,
    Has your problem been solved? If it is resolved, we suggest that you mark it as the answer. So it can help other people who have the same problem find a solution quickly. If not solved, what problem did you encounter?
    Best Regards,
    Daniel Zhang


    "Visual c#" forum will be migrating to a new home on Microsoft Q&A ! We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A ! For more information, please refer to the sticky post.

    pátek 20. listopadu 2020 6:51