Problems with Access

[Christopher Brandsdal]

I get this error:

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

/inc/DBconnect.asp, line 6
-------------------------------------------------------

I have just set up a new server, Win 2003 Std x64 bit

It seems like the driver for connecting to the database does not work on x64
bit!?!

Is there any workarounds on this, or do I have to get myself a new Win
edition?

Best regards,

Christopher Brandsdal

 

[Dave Anderson]

I get this error:

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

/inc/DBconnect.asp, line 6
-------------------------------------------------------

There's your error: line 6.

 

[Christopher Brandsdal]

The code is in use on about 100 websites I have made, so the code is fine i
guess. It just seems that the provider is not supported in x64? I have
googled the problem, and it seems to be common among 64 bits...
This is the code it reacts on:

1: <%
2: ' Connection to the database / Datenbankverbindung
3: Dim ConnectString, conn
4: ConnectString = Application("AdoConnection")
5: Set conn = Server.CreateObject("ADODB.Connection")
6: conn.open ConnectString
7: %>

 

[Bob Barrows [MVP]]

I get this error:

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

/inc/DBconnect.asp, line 6
-------------------------------------------------------

I have just set up a new server, Win 2003 Std x64 bit

It seems like the driver for connecting to the database does not work
on x64 bit!?!

Is there any workarounds on this, or do I have to get myself a new Win
edition?

Does this help?
http://www.aspfaq.com/show.asp?id=2340

 

[Christopher Brandsdal]

I read an article about the same thing:
-----------------------------------------------------------
I'm using Windows XP Professional 64 bit with Access 2000.

Databases I've used for quite sometime, now error in the line strConn =
"DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("/db/sample.mdb")

I've tried using strConn = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data
Source=" & Server.MapPath("/db/sample.mdb") but this results in an
'800a0e7a' error.

The first error is "Provider is not specified and there is no designated
default provider", the second is "Provider cannot be found. It may not be
properly installed."

I've tried downloading and installing MDAC 2.8 but it errors on this
platform??
------------------------------------------------------------------------

MDAC cannot be installed on x64. when I try to download it says that it's
only for 32 bit.
I guess I just have to get me a 32 bits win2k3...

 

[Bob Barrows [MVP]]

I read an article about the same thing:
-----------------------------------------------------------
I'm using Windows XP Professional 64 bit with Access 2000.

Databases I've used for quite sometime, now error in the line strConn
= "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("/db/sample.mdb")

I've tried using strConn = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data
Source=" & Server.MapPath("/db/sample.mdb") but this results in an
'800a0e7a' error.

The first error is "Provider is not specified and there is no
designated default provider", the second is "Provider cannot be
found. It may not be properly installed."

I've tried downloading and installing MDAC 2.8 but it errors on this
platform??
------------------------------------------------------------------------

MDAC cannot be installed on x64. when I try to download it says that
it's only for 32 bit.
I guess I just have to get me a 32 bits win2k3...

Did you try downloading and installing the Jet components? Those are
separate from the MDAC installation.

 

[Bob Barrows [MVP]]

I read an article about the same thing:
-----------------------------------------------------------
I'm using Windows XP Professional 64 bit with Access 2000.

Databases I've used for quite sometime, now error in the line strConn
= "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &
Server.MapPath("/db/sample.mdb")

I've tried using strConn = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data
Source=" & Server.MapPath("/db/sample.mdb") but this results in an
'800a0e7a' error.

The first error is "Provider is not specified and there is no
designated default provider", the second is "Provider cannot be
found. It may not be properly installed."

I've tried downloading and installing MDAC 2.8 but it errors on this
platform??
------------------------------------------------------------------------

Hmm, I've just been doing some googling myself and now see what you are
talking about: no x64 driver or provider for Jet.

Small consoloation, but according to this,
http://redmondmag.com/reports/article.asp?EditorialsID=128, " ... JET is
getting x64 support ... "

 

[Christopher Brandsdal]

Lol, i guess I don't have the time to sit around and wait!

But thanks a bunch for helping me, Bob!

 

[Bob Barrows [MVP]]

I get this error:

Christopher! Are you still around? Check this out:
http://www.microsoft.com/downloads/...98-de73-47dc-911b-50f4f0627ff4&DisplayLang=en

 

[Christopher Brandsdal]

After alot of help from Bob Barrows, there is finally a solution! :-D

Here is a short summary:

If you run Windows 2003 64 bit verion and still want to run Jet engine,
Acces and FrontPage, you have to do the following steps:

1. Make shore you have SP1 installed on the server

2: Check to ensure that you have all the DLL's required in ypur system
folders
Here is a list of DLL files needed:
http://support.microsoft.com/?kbid=829558

"there's only a 32-bit Jet driver in WS2003 x64, so only a 32-bit
application will be able to access Jet.
In order for IIS to use 32-bit drivers, you must flip it from 64-bit to
32-bit."

3: Convert IIS to run in 32 bit mode:
http://support.microsoft.com/default.aspx?scid=kb;en-us;894435

Make sure that the status of ASP.NET version 2.0.40XXX is set to Allowed in
the Web service extension list in Internet Information Services Manager.

4. To run FrontPage server extensions, download and run:
http://www.microsoft.com/downloads/...f9-3c78-44bb-8a72-6f8ed2aa0e8e&DisplayLang=en

Once again; thanks alot Bob! I have learned a great deal about 32/64 bit
software now ;-)

 

[Bob Barrows [MVP]]

3: Convert IIS to run in 32 bit mode:
http://support.microsoft.com/default.aspx?scid=kb;en-us;894435

This solution came from an MVP naned Steve Foster ,,, credit where credit is
due

 

[Egbert Nierop \(MVP for IIS\)]

After alot of help from Bob Barrows, there is finally a solution! :-D

Here is a short summary:

If you run Windows 2003 64 bit verion and still want to run Jet engine,
Acces and FrontPage, you have to do the following steps:

1. Make shore you have SP1 installed on the server

2: Check to ensure that you have all the DLL's required in ypur system
folders
Here is a list of DLL files needed:
http://support.microsoft.com/?kbid=829558

"there's only a 32-bit Jet driver in WS2003 x64, so only a 32-bit
application will be able to access Jet.
In order for IIS to use 32-bit drivers, you must flip it from 64-bit to
32-bit."

3: Convert IIS to run in 32 bit mode:
http://support.microsoft.com/default.aspx?scid=kb;en-us;894435

Make sure that the status of ASP.NET version 2.0.40XXX is set to Allowed
in the Web service extension list in Internet Information Services
Manager.

4. To run FrontPage server extensions, download and run:
http://www.microsoft.com/downloads/...f9-3c78-44bb-8a72-6f8ed2aa0e8e&DisplayLang=en

Once again; thanks alot Bob! I have learned a great deal about 32/64 bit
software now ;-)

b.t.w. it's better to avoid the ODBC compatibility driver. Your connection
string also loads through ODBC and you can load ole db for access (jet) more
directly by using this string...

Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Data\mymdb.mdb;Mode=ReadWrite|Share Deny None;

 

[Narendra Jain]

It is also possible to run IIS in 32 bit mode. So it can use all the
database drivers

http://support.microsoft.com/defaul...OnWin64 1 I used this and it is working fine.