CFF KB - Carrz-Fox-Fire Promotions Knowledge Base

CFF KB is all about 1 thing: The Sharing of Knowledge and the Power we gain from it.
>>Development (Web and Desktop) >> Database >> Microsoft Access

ADODB.Connection error '800a0e7a' Provider cannot be found. It may not be properly installed.

Article ID: 143 - Date Created Monday, July 18, 2011 - This Article Has been Viewed 8401 times.
Article was last updated on: Friday, May 05, 2017 - Written By:

ADODB.Connection error '800a0e7a' Provider cannot be found. It may not be properly installed.

CFF Knowledge Base - Share on MySpace CFF Knowledge Base - Share With Facebook CFF Knowledge Base - Share on Twitter CFF Knowledge Base - Share on Reddit CFF Knowledge Base - Share on Digg It CFF Knowledge Base - Share on Stumble Upon It CFF Knowledge Base - Share on Delicious
Share With Friends (Updated 6-8-2010)
If you are trying to use the accdb access database in your web application, you may run into this error when making your connection call to open the database in your script.

Details
Using the ACCDB access database, you will have to download and install the driver on your server if you do not have microsoft office 2007 or microsoft office 2010 installed on the server that the script is being run on.
The following error will happen if you do not have the driver installed.

 
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
/ACN.asp, line 15


Recreate Issue
To recreate this issue.
Scenario #1:
Do not have any drivers installed for the Access Database, this will cause this error to happen.

Scenario #2:
The [application pool], is not set for 32 Bit.


Resolve Issue
To correct this issue:

Scenario #1:
Either install Microsoft Office 2007 or Microsoft Office 2010.
It they are not available, you will have to download and install the following driver.
Microsoft Access Database Engine 2010 Redistributable«

Scenario #2:
Open [IIS] (Internet Information Services)
[Step #1]
Click on [Application Pools]
Either create a [New Application Pool] by right click on choosing such
(or)
[Right Click] on one of the available Application Pool
If this is for [ASP Classic], make sure that you choose the one that has Classic under [Managed Pipeline].
[Next]
[Right Click] on the chosen Application Pool name, and choose [Advanced Settings]
Under [General]
Enable 32-Bit Applications [True]
Click [OK]

[Step #2]
Expand [Server Name]
Expand [Sites]
[Right Click] on the [Default Web Site] (or) The website you are working with.
Hover the cursor over: [Manage site]
Then choose [Advanced Settings]
(This can also be gotten to by the following)
Click on the [Default Web Site]
On the far right panel
Under [Browse Web Site]
Click [Advanced Settings]
When the Advanced Settings Dialog opens.
Under [General]
[Application Pool] Choose the Application Pool name from the dropdown list, that you assigned 32-Bit to, in [Step #1].
Click [OK]
Then reload your page.

Scenario #3:
Perform this after everything else has been done from above.

To configure 32-bit mode for the server

Open a command prompt and run the following:

 
%windir%\system32\inetsrv\appcmd set config -section:applicationPools -applicationPoolDefaults.enable32BitAppOnWin64:true


Scenario #4
Download the Microsoft Access Database Engine 2010 Redistributable« package.
Choose the 32-Bit version.
To install this 32-Bit file to your 64-Bit server, you will need to perform the following.

use /passive parameter with 64bit version.
(This information was provided by: Ivana Kolin from Solidworks.com« )
You can also watch the following Video, of which demonstrates this method as well. from here

 
Click Start, then click Run.
In the Run dialog box, type cmd, and then click OK.
In the command prompt window, change the directory to the drive that contains downloaded AccessDatabaseEngine.exe
To change the Directory, simply type in the Drive letter and colon, and press Enter
Example - D:
To change folder locations, to where you have AccessDatabaseEngine located at.
D:\> cd data
D:\data> cd myFile
D:\data\myFile >
Now, type in
At the command prompt, type: AccessDatabaseEngine.exe /passive


Updated, changed the name of the accessdatabaseengine file name from _64 to .exe
This is using the 32bit version, of which, fixing this issue, in most cases.