Getting 3706 provider cannot be found. It may not be properly installed when app moved to windows 10

Question

0.00/5 (No votes)

See more:

We have an existing VB.Net 2017 app that has been running for years on Windows 7. It's using an access database.

The system was updated to Windows 10 and access to 2019. If fails on both a 32 bit and 64 bit office of access 2016 and 2019.

Error
3706 Provider cannot be found. It may not be properly installed

The app is 32 bit and must stay 32 bit.

Connection string first tried
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\ATX QBFILES\xxxxxx.mdb;
which was working on Windows 7 then tried
Provider=Microsoft.ACE.OLEDB.15.0;Data Source=C:\ATX QBFILES\xxxxxx.mdb;

I am at a loss to understand exactly what it is missing.

Any ideas?

Thanks and Happy Holidays to all.

What I have tried:

Changing the values of the connection string from 12 to 15 and 16. Different versions of Access.

Posted 14-Dec-19 9:37am

QuickBooksDev

Updated 7-Jul-23 17:52pm

Add a Solution

3 solutions

Solution 1

At a guess - and without your app and probably source that's all it can be - it's a size problem. Was the Win7 32 bit or 64? I'd suspect that the VB app was 32 bit, and you're running on 64 bit now with a 64 bit version of the ACE DB engine, or the app is "any cpu" with the 32 bit ACE engine under a 64 bit OS.

You can't "switch processor sizes" once an app has started - so a 64 bit app can't use a 32 bit engine, and vice versa.

I'd install the 64 bit ACE engine, and rebuild the VB app for 64 bit only, and see what happens.

Posted 14-Dec-19 10:15am

OriginalGriff

Comments

QuickBooksDev 14-Dec-19 16:33pm

W7 was 64bit. App is 32 bit and must stay 32 bit due to other requirements.

How do I get and install any ACE engine?

OriginalGriff 14-Dec-19 17:04pm

Uninstall 64 bit ACE, then install the 32 bit version
https://www.microsoft.com/en-us/download/details.aspx?id=54920
I understand it is possible to install them both on the same machine, but it's always given me loads of hassle:
https://datasavvy.me/2017/07/20/installing-the-microsoft-ace-oledb-12-0-provider-for-both-64-bit-and-32-bit-processing/
You'll need to reference the right version in your connection string.

QuickBooksDev 14-Dec-19 18:04pm

Installed Microsoft Access Database_x64 and get the same error on my Office 2016 64 bit machine.

Unable to install the either version of on Office 2016 32 bit machine because the 32 bit version says I have 64bit installed and the 64bit version says I have 32 bit installed.

Yuck!!!

Will try a reboot

QuickBooksDev 15-Dec-19 6:23am

Re-boot did not help.

I used different code in a 64 bit app and still failed with the same error.

Surely there must be a way to read an Access database in Windows 10.

Solution 3

I have same problem. I install my app in my laptop customer. remote.
I have success when install at his staff laptop. but, failed when install at him.

the message is: provider not found.

my suggest is:
1. windows 11.
2. office 2019.

last, maybe I have to running and compile at his laptop. if I fail with mine.

Posted 7-Jul-23 17:52pm

Member 13865334

Updated 7-Jul-23 17:53pm

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

QuickBooksDev · Accepted Answer · 2019-12-15T03:02:00

Solution 2

I gave up on using the ACE connection string and instead used

"DRIVER={Microsoft Access Driver (*.mdb)};DBQ=c:\mydatabase.mdb"

which worked with my 32bit app with a 64 bit access. It also worked on a test 64 bit app with a 32 access.

Don't understand why this has been so difficult.

Posted 15-Dec-19 3:02am

QuickBooksDev

Comments

Richard MacCutchan 15-Dec-19 11:49am

I have used the ACE connection string in a 32-bit application, in Windows 10 without problems.

QuickBooksDev 15-Dec-19 11:57am

Did you have to add anything else? It fine in W7 with Access 2013 but the same app on W10 just didn't. Same install MSI same everything but no go on W10/Access 2016.

Did you have office/access installed or were using RunTime?

jose Gonzalez Jun2022 17-Jun-22 11:26am

"DRIVER={Microsoft Access Driver (*.mdb)};DBQ=c:\mydatabase.mdb"

Muchas gracias estimado por compartir tu conocimiento, en mi caso esta linea de condigo me funcionó muy bien en mi proyecto para hacer la conexión a mi base de datos; ahora ya me puedo conectar tanto en W7 como en W11 y Access 2010 y Access 2019; el problema se me generaba en el uso del ListView, al usar los proveedores tradicionales no me podía conectar en Access 2019, ahora con este proveedor ya me puedo conectar en ambas versiones de Access 2010 - 2019.