Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 3706

Error 3706 and 429: The Microsoft ACE OLEDB Provider Is Not Registered

10 min read Updated October 5, 2026 Outlook & Office Applications

Fix it now

The provider your connection string names is not usable by the process asking for it. Microsoft publishes 3706 as “Provider cannot be found. It may not be correctly installed.” Two things cause that: the wrong architecture, and an Office Click-to-Run installation that keeps the provider inside its own virtual environment.

Run these in a Command Prompt: the first shows 64-bit registration, the second 32-bit

reg query HKLM\SOFTWARE\Classes\Microsoft.ACE.OLEDB.16.0
reg query HKLM\SOFTWARE\Classes\WOW6432Node\Microsoft.ACE.OLEDB.16.0
  1. Establish the bitness of the process that fails, not of Windows. A .NET application built for x86, a 32-bit Office, and an IIS application pool with 32-bit applications enabled all need the 32-bit provider.
  2. Install the Access Database Engine in the architecture that process needs. On a machine with no Office at all, the current download is the Microsoft 365 Access Runtime.
  3. If Office is installed and is a Click-to-Run build, check its version before installing anything. Microsoft took the ACE components out of the Click-to-Run virtual environment from Microsoft 365 Apps for enterprise Version 2009, so on an older build the answer is to update rather than to add a redistributable.
  4. If the connection string names Microsoft.Jet.OLEDB.4.0, change it. Jet 4.0 exists only in 32-bit and was never released for 64-bit processes.
  5. Retest from the host and the account that failed, not from a development tool of a different bitness, and restart the service or application pool first so it picks up the new registration.

Read the registered provider names out of the registry rather than guessing the version. A connection string naming Microsoft.ACE.OLEDB.12.0 on a machine where only 16.0 is registered fails in exactly the same way as a machine with no provider at all.

If the connection opens and returns a row, you are done. The next section explains why architecture decides everything here, and what the Click-to-Run case looks like.

Why it happens

An OLE DB provider is an in-process COM server: a library the calling process loads into its own address space. A 64-bit process can only load 64-bit libraries and a 32-bit process only 32-bit ones, so a provider registered for one architecture is invisible to the other. Windows keeps two separate registration areas for exactly this reason, and a provider present in one of them satisfies nothing running in the other.

That trips people up because the failing process is rarely the one they are looking at. A report designer running as a 32-bit application previews a package happily and then fails when a 64-bit runtime executes it. A web application succeeds or fails depending on whether its application pool has 32-bit applications enabled. A database engine loads the provider into its own 64-bit process regardless of what is installed for the interactive user. Establish which process is asking before you install anything.

The second cause is the one most articles miss. Microsoft documents that Click-to-Run installations of Office run in an isolated virtual environment, and that applications outside Office may not know where to look inside it – so an external application asking for Microsoft.ACE.OLEDB.12.0 or Microsoft.ACE.OLEDB.16.0 gets “Provider cannot be found” on a machine where Access is plainly installed and working. From Microsoft 365 Apps for enterprise Version 2009 the ACE components were taken out of that bubble. On an older Click-to-Run build, updating Office is the fix and installing a redistributable is not.

The provider is installed for the wrong architecture

You have this one if The code works in one host and fails in another on the same machine, or works interactively and fails when a service or scheduler runs it.

  1. Determine the bitness of the failing process. In .NET, read the platform target rather than assuming Any CPU behaves as 64-bit.
  2. Install the Access Database Engine matching that bitness.
  3. For a web application, check whether the application pool has 32-bit applications enabled and match the provider to that setting.
  4. Retest from the host that failed, after restarting it.

Office is Click-to-Run and older than Version 2009

You have this one if Access is installed and works, and an external application still gets a provider-not-found error. ODBC drivers supplied by Access may also be missing from the driver list.

  1. Read the Office build and channel from File > Account.
  2. Update to Microsoft 365 Apps for enterprise Version 2009 or later, which is where Microsoft took ACE out of the virtual environment.
  3. On Office 2016 or 2019 Pro Plus Click-to-Run volume builds, Microsoft’s options are to move to Office LTSC 2021 or to install the Access 2013 Runtime.
  4. On a machine with no Office at all, install the Microsoft 365 Access Runtime.

No Click-to-Run instance of Office can create machine or system data source names for these drivers, either from inside an Office application or from the ODBC administrator. If that is what you were trying to do, this is why.

No provider is installed at all

You have this one if Both registry queries return nothing, and the machine has never had Access or a redistributable on it.

  1. Install the Access Database Engine in the architecture the process needs.
  2. Confirm registration afterwards with the registry queries above.
  3. Restart the calling application, service or application pool so it picks up the new registration.

The connection string names a provider that is not here

You have this one if 3706 on a machine that clearly has a provider installed, with a version in the string that does not match it.

  1. Read the registered provider names from the registry rather than guessing.
  2. Update the connection string to the version actually present.
  3. Replace Microsoft.Jet.OLEDB.4.0 with the current ACE provider; there is no 64-bit Jet and there never was.
  4. Where the same code runs on several machines, read the provider version from configuration instead of hard-coding it.

Full reference

Which installations need something extra

What is installed Extra components needed What Microsoft says to do
Microsoft 365 Apps for enterprise, or Office 2016/2019/2021 consumer, Version 2009 or later No
Office LTSC 2021 volume licence No
Office 2016 or 2019 Pro Plus Click-to-Run volume licence Yes Upgrade to Office LTSC 2021, or install the Access 2013 Runtime
Office 2010, 2013 or 2016 MSI No
No Office installation Yes Microsoft 365 Access Runtime

Reading the codes you were given

Code Published meaning
3706 Provider cannot be found. It may not be correctly installed
429 Component can’t create object or return reference to this object
3044 No vendor-published meaning; in practice the path in the connection string is not usable by the account the process runs under
3170 No vendor-published meaning; in practice the provider loaded and the driver for the file type in the extended properties did not

3170 is worth separating from the rest, because it means you got further than you think. The provider was found and loaded; what failed was the installable driver for the specific file type named in the connection string’s extended properties – a spreadsheet or a text format. Check the extended properties clause first, because a malformed value produces this even when everything is installed correctly.

Both architectures on one machine

Installing a redistributable of one architecture alongside an Office of the other is not a supported configuration. It can interfere with Office repair and update operations, and a later Office update can undo the arrangement without telling anybody. Where it seems unavoidable, look first at whether the calling application can be built for the architecture Office already uses – that is the outcome that stays fixed. If you go ahead anyway, do it on a server dedicated to one job, never on a user’s workstation, and write down why the machine is set up that way for whoever repairs Office next.

Checks that settle it quickly

  • Run both registry queries. If neither returns a key, nothing is registered and the argument about bitness is premature.
  • Read File > Account in any Office application for the build and channel; the Click-to-Run cause turns on that number.
  • Check the platform target of the failing application rather than the machine’s architecture.
  • For an IIS application, read the Enable 32-Bit Applications setting on the application pool, not the site.
  • Test the connection string from a small script running in the same architecture as the failing process, which removes the application from the question entirely.

When a licence is the actual fix

For most of these there is nothing to buy. The Access Database Engine is a free download from Microsoft, and where Office is a Click-to-Run build older than Version 2009 the fix is an update you are already entitled to rather than a purchase. Check both of those before anyone raises a requisition. A licence question only arises where somebody needs Access itself – to open, design and maintain the databases rather than to read them from code – and Access is included in some Microsoft 365 plans and not others, so the answer depends on what you already hold. Arco can check whether the subscriptions you have include Access, and supply Microsoft 365 Apps licences matched to the bitness your applications actually need rather than to whatever installs by default.

Every code this article covers

Code What it points at Source
3706 Provider cannot be found. It may not be correctly installed Microsoft Learn
429 Component can’t create object or return reference to this object Microsoft Learn
3044 The path given in the connection string is not usable by the account the process runs under not published by the vendor
3170 The provider loaded, and the installable driver for the file type named in the extended properties did not not published by the vendor

Confirm the fix worked

  1. Run the registry query for the provider you expect and confirm it returns a key in the area matching your architecture.
  2. Execute the failing code path from the same host and under the same account that failed originally.
  3. Open a connection, read one row and close it, to prove the provider works rather than merely registers.
  4. Restart the service or application pool and repeat, to confirm the fix survives a recycle.
  5. If the machine has Office, read File > Account and record the build, so the next person knows whether the Click-to-Run cause applied.

Questions people ask about this

Do I have to buy Access to read an Access file from my application?

No. The Access Database Engine is free from Microsoft and provides what your code needs. You need a licensed copy of Access only when somebody has to open and work in the database interactively.

Why does it work on my development machine and fail on the server?

Almost always architecture, or a missing engine. Development tools frequently run as 32-bit while the deployed process runs as 64-bit, so the provider that satisfied the designer is invisible to the runtime. Check the platform target of the built application rather than the machine.

Access is installed and working. How can the provider be missing?

If Office is a Click-to-Run build older than Microsoft 365 Apps for enterprise Version 2009, the ACE components sit inside Office’s virtual environment and applications outside Office cannot see them. Updating Office is the documented fix for that case.

Can I still use the old Jet provider?

Only from a 32-bit process and only for the older file format. There is no 64-bit Jet and there never was, so anything current should use the ACE provider.

Is installing both architectures really that risky?

It is unsupported rather than guaranteed to break. The practical risks are that Office repair behaves unexpectedly and that a later update undoes the arrangement quietly. On a dedicated server it is sometimes accepted; on a user’s workstation it rarely repays the trouble.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office Cannot Print: Spooler Errors 0x000006ba and 0x00000bc4 With No Printers Found License Error Outlook 0x80070020: The OST File Is In Use and Locked by Another Process Free Fix Outlook 0x800CCC0A Message Download Incomplete: Clear the Stuck Oversized Email Free Fix Outlook 0x800CCC80 and 0x800CCC1A: SSL and Authentication Method Mismatch on Send
โ† Back to Knowledge Base