Errors in the back-end database access module. The provider Microsoft.ACE.OLEDB.12.0 is not registered

obeida bitar 21 Reputation points
2020-11-09T12:33:33.507+00:00

I am working on a data mining (sql server analysis services) project on visual studio 2019, I have an office 2016 64bit, I tried to install Microsoft Access Database Engine 2010 Redistributable 64bit but I couldn't find it in the provider list, so I uninstall it and install the 32bit version of Microsoft Access Database Engine 2010 after that I could find The Microsoft.ACE.OLEDB.12.0 provider but when I try to process my project I have this error
38406-43008.png

SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,276 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Lukas Yu -MSFT 5,821 Reputation points
    2020-11-10T06:19:13.507+00:00

    Hi,

    As suggested in your last post, the 32bit maybe the reason for this error.

    I still suggest you to try 64bit version. For SSAS 2019, I would suggest you to try the newest : Microsoft Access Database Engine 2016 Redistributable

    If the provider still not show in the list, you may follow the official resolution for this : Can't use the Access ODBC driver or OLEDB provider outside Office Click-to-Run applications

    Regards,
    Lukas


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet ----Hot issues October


  2. Darren Gosbell 1,471 Reputation points
    2020-11-15T23:32:51.05+00:00

    If you are running both SSDT and the server on your local machine you actually need both versions of the provider installed. SSDT needs the 32 bit version and the server needs the 64 bit version.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.