ACE.OLE.DB issue importing to SQL Server 2019

Question

After I installed Office 2016 I lost the ability to successfully import Excel files using Import/Export wizard in SQL Server 2019. Able to import Flat files.

Microsoft ODBC Driver 17 for SQL Server and Microsoft ODBC Driver 19 for SQL Server are installed.

Microsoft Access database engine 2010 32bit installed. I deleted and then reinstalled Microsoft Access databased engine 2016 from the cmd line: with /quiet

There is an ACE.OLEDB.12.0 and and ACE.OLEDB.16.0 on my machine. I've selected different versions of Excel. That does not resolved the issue.

Can you assist with this issue?

Answer 1

Hi @Michel Weaver (Getting to Green LLC),

Please refer to this similar thread:

 https://learn.microsoft.com/en-us/answers/questions/737285/how-to-fix-microsoft-ace-oledb-12-0-provider-is-no

If this thread does not give you help, you can register the ACE.OLEDB.12.0 provider manually. Open the Command Prompt as an administrator and run the following command:

regsvr32 "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEOLEDB.DLL"

Ensure that you replace the file path with the correct path to the ACEOLEDB.DLL file on your machine.

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 2

Is there a way to resolve the main issue that I seem to be having with OLEDB? It is very helpful for us to have this option. I tried importing through Visual Studio and received the following error. I ran what you sent before as an admin so not sure why these are not registered?

Imported the file as .csv but am having issue with a datetype data type. In the SQL Server Import and Export Wizard Advanced view a column RequestDate is added as date [DT_DATE]. The destination type is datetype. Below is the error. Thanks for the help!

Answer 3

Hi @Michel Weaver (Getting to Green LLC)

From the error message, please try to run the package via 64bit model.

In the Project Properties of an Integration Services package, you need to select 64-bit execution by setting the value of the Run64BitRuntime property to true on the Debugging page as shown below.

Regards，

Zoe Hui

---

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

Answer 4

Run64BitRuntime was set to True.