IIS8/IIS7/IIS6 the solution of adodb.connection error ' 800a0e7a '

I just bought a server. Support for 64-bit Windows2003 so want to cool, loaded IIS6, can only install 64-bit net FrameWork

Publish two websites with VS2005 under the XP32 bit:

A, based on the SQL2000

B, Office Access based

After the server configuration completed, a station normal operation, very cool. B Station error, meaning in the method of connecting to the database, depressed for a long time.

Thinking: Today, the user prompts 64-bit IIS support for OLE problems.

Because the 64-bit operating system does not support Microsoft OLE DB Provider for Jet drive apricot explosion also does not support earlier Microsoft Access Driver (*.mdb)-mode connections. Therefore, Microsoft OLE DB Provider for Jet for Access and Excel databases is not available in the 64-bit version, that is, the following two connection strings are no longer working:

"Provider=Microsoft.Jet.OLEDB.4.0;Data source=" &server.mappath (db)

"Driver=microsoft Access Driver (*.mdb);D bq=" &server.mappath (db)

Workaround: In this case, you can only use one method to set the running environment of IIS to 32 bits:

IIS6 on the way:

1. Command line type:

cscript.exe%SystemDrive%\inetpub\adminscripts\adsutil.vbs SET W3svc/apppools/enable32bitapponwin64 1

That is, Setup IIS6 allows 32-bit programs to run on 64-bit machines

2. Re-register. NET Frameworks

%systemroot%\microsoft.net\framework\v2.0.50727\aspnet_regiis.exe-i

3. After the completion, look at the Web service extensions, should be more than a 32-bit asp.net set it to allow, disadvantage: This will enable all sites on the entire IIS to run in 32-bit compatible mode.

The practice on IIS7 is much simpler:

Application pools, advanced settings--> allows 32-bit applications

Run IIS6, run the. Net+access website to see if it solves

Follow-up: If there are problems, such as service unavailable, congratulations, you can learn new knowledge. Very annoying, look at the error log, I encountered RpcProxy.dll all ISAPI filter errors that could not be loaded and could not load the site/service. Workaround: Open iis--> View the properties of the Web site--->isapi filter--> Remove the item with the down Red Arrow--> restart Iis-->ok. This is all resolved.

These are IIS 6 settings

The following is the IIS7 setting method

Use the IIS8 under Win8 to debug an ASP program that ran the following error: adodb.connection error ' 800a0e7a ' did not find the provider. The program may not be installed correctly.

Using the IIS8 under Win8 to debug an ASP program, the following error occurred:

ADODB. Connection error ' 800a0e7a '

Provider not found. The program may not be installed correctly.

/admi_datalink.asp, Line 5

Found that the problem is 64-bit system setup, the solution is very simple:

1, open IIS, click "Application Pool" to find the operation under the "Set Application pool default Settings" (see figure);

2. Set the Enable 32-bit application in application pool defaults to True (figure);

This eliminates the 800a0e7a error.

Use the IIS8 under Win8 to debug an ASP program that ran the following error: adodb.connection error ' 800a0e7a ' did not find the provider. The program may not be installed correctly.

Using the IIS8 under Win8 to debug an ASP program, the following error occurred:

ADODB. Connection error ' 800a0e7a '

Provider not found. The program may not be installed correctly.

/admi_datalink.asp, Line 5