none
Microsoft.ACE.OLEDB.16.0 Not registered error RRS feed

  • Question

  • Machine setup: 

    Visual Studio 2016

    SQL Server 2016 Developer

    Office 2016

    I keep getting Microsoft.ACE.OLEDB.16.0 Not registered on this machine error. Not sure how to fix it.

    • Moved by 宝宝徐 Tuesday, November 22, 2016 6:19 AM
    Sunday, November 20, 2016 3:11 PM

Answers

  • Hello,

    When do you get the error message? Within an application or when you run a query against SQL Server or ... ?

    In common the error indicates a) ACE data Provider is not installed at all or b) ACE ist installed but in a different 32 / 64 bit achitecture then the used application.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, November 22, 2016 6:43 AM
    Moderator
  • Hi f_a_98,

    Could you please share more detailed information to us for analysis? In which scenario did you meet this error message? An application running the query, migrating data, importing data? We also want to know the Bit number of Office 2016 and SQL Server 2016, 32-bit or 64-bit?

    Based on my experience, the above error message can occur in many scenarios:

    1. The file Csi.dll is broken or not existing, this file should be in the folder ‘C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16’, please copy this file from another machine that runs Access 2016 to replace the broken file or repair Access 2016. To repair Access 2016, you can right-click Office 2016 in the Programs and Features and select change, after that select online repair.

    2. If you use Visual Studio to connect Access database using a connection string like the following code:

    string connString = "Provider=Microsoft.ACE.OLEDB.16.0;Data Source=****.xls;Extended Properties=****";


    We need to change the Solution Platform from "Any CPU" to "x86" or "x64" based on the Bit number of office installation, please use the following steps:

    a. Right click on the Solution File in Solution Explorer of Visual Studio and click on the Configuration Manager.
    b. Click on the Active Platform Drop down, if x86 is already there then select that, else click on New.
    c. Select x86 or x64 from the new platform dropdown and click OK.

    Best Regards,
    Teige


    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.



    Tuesday, November 22, 2016 8:57 AM
    Moderator

All replies

  • Hi f_a_98,

    Thank you for posting in MSDN forum.

    This forum is discussing about Visual Studio Setup and installation.

    As your issue is related to SQL Server,I help you move this case to SQL Server Getting started with SQL Server  forum for dedicated support.

    Thank you for your understanding.

    Best Regards,


    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.

    Tuesday, November 22, 2016 6:19 AM
  • Hello,

    When do you get the error message? Within an application or when you run a query against SQL Server or ... ?

    In common the error indicates a) ACE data Provider is not installed at all or b) ACE ist installed but in a different 32 / 64 bit achitecture then the used application.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, November 22, 2016 6:43 AM
    Moderator
  • Hi f_a_98,

    Could you please share more detailed information to us for analysis? In which scenario did you meet this error message? An application running the query, migrating data, importing data? We also want to know the Bit number of Office 2016 and SQL Server 2016, 32-bit or 64-bit?

    Based on my experience, the above error message can occur in many scenarios:

    1. The file Csi.dll is broken or not existing, this file should be in the folder ‘C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16’, please copy this file from another machine that runs Access 2016 to replace the broken file or repair Access 2016. To repair Access 2016, you can right-click Office 2016 in the Programs and Features and select change, after that select online repair.

    2. If you use Visual Studio to connect Access database using a connection string like the following code:

    string connString = "Provider=Microsoft.ACE.OLEDB.16.0;Data Source=****.xls;Extended Properties=****";


    We need to change the Solution Platform from "Any CPU" to "x86" or "x64" based on the Bit number of office installation, please use the following steps:

    a. Right click on the Solution File in Solution Explorer of Visual Studio and click on the Configuration Manager.
    b. Click on the Active Platform Drop down, if x86 is already there then select that, else click on New.
    c. Select x86 or x64 from the new platform dropdown and click OK.

    Best Regards,
    Teige


    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.



    Tuesday, November 22, 2016 8:57 AM
    Moderator