ADODB.Connection error '800a0e7a'

Paul Lynch wrote:
 > On Fri, 26 Mar 2004 17:16:52 -0800, J L
 > <anonymous RemoveThis @discussions.microsoft.com> wrote:
 >
 >
  >>hello,
  >>I have a problem on a Windows 2000 Server sp4 where any asp page that
  >>tries to connect to a database (SQL or Access) get's the following eror:
  >>
  >>-----
  >>ADODB.Recordset error '800a0e7a'
  >>
  >>Provider cannot be found. It may not be properly installed.
  >>
  >>/TEST.asp, line 8
  >>-----
  >>
  >>Example lines-
  >>Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
  >>
  >>Site 2: set br = server.CreateObject("ADODB.Connection")
   >> br.open application("BR_DATA_CONNECTION")
  >>
  >>Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
   >> rsViews.ActiveConnection = shop_conection_STRING
  >>
  >>And so on, and so forth. Previously, the server has MDAC v2.7
  >>installed, but after experiencing this today, I've upgraded to MDAC v2.8
  >>and hotfix Q832483, but that hasn't fixed the problem.
  >>
  >>Any ideas? All are appreciated.
 >
 >
 > Try this :
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://www.aspfaq.com/show.asp?id=2340</font" target="_blank">http://www.aspfaq.com/show.asp?id=2340</font</a>>
 >
 >
 > Regards,
 >
 > Paul Lynch
 > MCSE

Paul,

I've seen that page a couple of times today

As for its resolutions (page quotes preceded by '#')

# First things first: check your connection string. This error can
# often happen if you have a typo in your provider or driver details.

All the affected pages worked 100% prior to this morning.

# Make sure you have the most recent version of MDAC installed

Like I mentioned, this was the first thing I did - upgrade from 2.7 to 2.8

# This is often caused by attempting to connect to an Access
# database using OLE-DB (e.g. Provider=Microsoft.Jet.OLEDB.4.0
# without having JET components installed

All pages uses a JET provider still work. (JET 4.0 sp8)

Thanks.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

Response.Write() the values of the connection strings.

Response.Write(MM_dbconnection_STRING)
Response.End

Response.Write(application("BR_DATA_CONNECTION"))
Response.End

etc

Cheers
Ken


"J L" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
: hello,
: I have a problem on a Windows 2000 Server sp4 where any asp page that
: tries to connect to a database (SQL or Access) get's the following eror:
:
: -----
: ADODB.Recordset error '800a0e7a'
:
: Provider cannot be found. It may not be properly installed.
:
: /TEST.asp, line 8
: -----
:
: Example lines-
: Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
:
: Site 2: set br = server.CreateObject("ADODB.Connection")
: br.open application("BR_DATA_CONNECTION")
:
: Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
: rsViews.ActiveConnection = shop_conection_STRING
:
: And so on, and so forth. Previously, the server has MDAC v2.7
: installed, but after experiencing this today, I've upgraded to MDAC v2.8
: and hotfix Q832483, but that hasn't fixed the problem.
:
: Any ideas? All are appreciated.
:
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

Ken Schaefer wrote:

 > Response.Write() the values of the connection strings.
 >
 > Response.Write(MM_dbconnection_STRING)
 > Response.End
 >
 > Response.Write(application("BR_DATA_CONNECTION"))
 > Response.End
 >
 > etc
 >
 > Cheers
 > Ken
 >
 >
 > "J L" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in message
 > news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
 > : hello,
 > : I have a problem on a Windows 2000 Server sp4 where any asp page that
 > : tries to connect to a database (SQL or Access) get's the following eror:
 > :
 > : -----
 > : ADODB.Recordset error '800a0e7a'
 > :
 > : Provider cannot be found. It may not be properly installed.
 > :
 > : /TEST.asp, line 8
 > : -----
 > :
 > : Example lines-
 > : Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
 > :
 > : Site 2: set br = server.CreateObject("ADODB.Connection")
 > : br.open application("BR_DATA_CONNECTION")
 > :
 > : Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
 > : rsViews.ActiveConnection = shop_conection_STRING
 > :
 > : And so on, and so forth. Previously, the server has MDAC v2.7
 > : installed, but after experiencing this today, I've upgraded to MDAC v2.8
 > : and hotfix Q832483, but that hasn't fixed the problem.
 > :
 > : Any ideas? All are appreciated.
 > :
 >
 >

Hello. Thanks Ken,

Here's one that stopped working:
MM_conTest_STRING = "dsn=test"

And another:
Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
DBQ=C:\wwwroot\ob\fus\cated.mdb"

And another:
application("SITE_DB_CONNECTION") =
"Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User
ID=***;Initial Catalog=***;ServerName=***;Database=***"


Here's one that still works:
MM_conManagement_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=G:\wwwroot\site1\ob\fus\cated.mdb"'"dsn=***;"

I hope that helps. Keep in mind that the top three all worked this
morning, and that like the last one, all JET connections still seem to
work. Crazy mdac.

Any other ideas? I'll try anything to circumvent an OS reinstall

Thank you in advance.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

J L wrote:

 > Ken Schaefer wrote:
 >
  >> Response.Write() the values of the connection strings.
  >>
  >> Response.Write(MM_dbconnection_STRING)
  >> Response.End
  >>
  >> Response.Write(application("BR_DATA_CONNECTION"))
  >> Response.End
  >>
  >> etc
  >>
  >> Cheers
  >> Ken
  >>
  >>
  >> "J L" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
  >> news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
  >> : hello,
  >> : I have a problem on a Windows 2000 Server sp4 where any asp page that
  >> : tries to connect to a database (SQL or Access) get's the following
  >> eror:
  >> :
  >> : -----
  >> : ADODB.Recordset error '800a0e7a'
  >> :
  >> : Provider cannot be found. It may not be properly installed.
  >> :
  >> : /TEST.asp, line 8
  >> : -----
  >> :
  >> : Example lines-
  >> : Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
  >> :
  >> : Site 2: set br = server.CreateObject("ADODB.Connection")
  >> : br.open application("BR_DATA_CONNECTION")
  >> :
  >> : Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
  >> : rsViews.ActiveConnection = shop_conection_STRING
  >> :
  >> : And so on, and so forth. Previously, the server has MDAC v2.7
  >> : installed, but after experiencing this today, I've upgraded to MDAC
  >> v2.8
  >> : and hotfix Q832483, but that hasn't fixed the problem.
  >> :
  >> : Any ideas? All are appreciated.
  >> :
  >>
  >>
 >
 > Hello. Thanks Ken,
 >
 > Here's one that stopped working:
 > MM_conTest_STRING = "dsn=test"
 >
 > And another:
 > Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
 > DBQ=C:\wwwroot\ob\fus\cated.mdb"
 >
 > And another:
 > application("SITE_DB_CONNECTION") =
 > "Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User
 > ID=***;Initial Catalog=***;ServerName=***;Database=***"
 >
 >
 > Here's one that still works:
 > MM_conManagement_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
 > Source=G:\wwwroot\site1\ob\fus\cated.mdb"'"dsn=***;"
 >
 > I hope that helps. Keep in mind that the top three all worked this
 > morning, and that like the last one, all JET connections still seem to
 > work. Crazy mdac.
 >
 > Any other ideas? I'll try anything to circumvent an OS reinstall
 >
 > Thank you in advance.
 >


If it will help, I've also unreged and re-reged all the 2.8 DLL's like
mentioned in the 2003-06-20 microsoft.public.data.ado post titled
"Repair a corrupted MDAC 2.71 installation - the Solution"

Found:
<a style='text-decoration: underline;' href="http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+installation+-+the+Solution%22&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=eBVyN%23yNDHA.1612%40TK2MSFTNGP11.phx.gbl&rnum=1" target="_blank">http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+insta...tion+-+</a>

Thanks.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

Hi, if you suspect your MDAC installation to be damaged, please download the
ComCheck tool from:
www.microsoft.com/data
and verify your MDAC components. Report back if there are any reported.

Cheers
Ken


"J L" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:%23PcZBZ8EEHA.1456@TK2MSFTNGP09.phx.gbl...
: J L wrote:
:
: > Ken Schaefer wrote:
: >
: >> Response.Write() the values of the connection strings.
: >>
: >> Response.Write(MM_dbconnection_STRING)
: >> Response.End
: >>
: >> Response.Write(application("BR_DATA_CONNECTION"))
: >> Response.End
: >>
: >> etc
: >>
: >> Cheers
: >> Ken
: >>
: >>
: >> "J L" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
: >> news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
: >> : hello,
: >> : I have a problem on a Windows 2000 Server sp4 where any asp page that
: >> : tries to connect to a database (SQL or Access) get's the following
: >> eror:
: >> :
: >> : -----
: >> : ADODB.Recordset error '800a0e7a'
: >> :
: >> : Provider cannot be found. It may not be properly installed.
: >> :
: >> : /TEST.asp, line 8
: >> : -----
: >> :
: >> : Example lines-
: >> : Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
: >> :
: >> : Site 2: set br = server.CreateObject("ADODB.Connection")
: >> : br.open application("BR_DATA_CONNECTION")
: >> :
: >> : Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
: >> : rsViews.ActiveConnection = shop_conection_STRING
: >> :
: >> : And so on, and so forth. Previously, the server has MDAC v2.7
: >> : installed, but after experiencing this today, I've upgraded to MDAC
: >> v2.8
: >> : and hotfix Q832483, but that hasn't fixed the problem.
: >> :
: >> : Any ideas? All are appreciated.
: >> :
: >>
: >>
: >
: > Hello. Thanks Ken,
: >
: > Here's one that stopped working:
: > MM_conTest_STRING = "dsn=test"
: >
: > And another:
: > Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
: > DBQ=C:\wwwroot\ob\fus\cated.mdb"
: >
: > And another:
: > application("SITE_DB_CONNECTION") =
: > "Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User
: > ID=***;Initial Catalog=***;ServerName=***;Database=***"
: >
: >
: > Here's one that still works:
: > MM_conManagement_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
: > Source=G:\wwwroot\site1\ob\fus\cated.mdb"'"dsn=***;"
: >
: > I hope that helps. Keep in mind that the top three all worked this
: > morning, and that like the last one, all JET connections still seem to
: > work. Crazy mdac.
: >
: > Any other ideas? I'll try anything to circumvent an OS reinstall
: >
: > Thank you in advance.
: >
:
:
: If it will help, I've also unreged and re-reged all the 2.8 DLL's like
: mentioned in the 2003-06-20 microsoft.public.data.ado post titled
: "Repair a corrupted MDAC 2.71 installation - the Solution"
:
: Found:
:
http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+insta...tion+-+
:
: Thanks.
:
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

Ken Schaefer wrote:

 > Hi, if you suspect your MDAC installation to be damaged, please download the
 > ComCheck tool from:
<font color=purple> > <a style='text-decoration: underline;' href="http://www.microsoft.com/data</font" target="_blank">www.microsoft.com/data</font</a>>
 > and verify your MDAC components. Report back if there are any reported.
 >
 > Cheers
 > Ken
 >
 >
 > "J L" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
 > news:%23PcZBZ8EEHA.1456@TK2MSFTNGP09.phx.gbl...
 > : J L wrote:
 > :
 > : > Ken Schaefer wrote:
 > : >
 > : >> Response.Write() the values of the connection strings.
 > : >>
 > : >> Response.Write(MM_dbconnection_STRING)
 > : >> Response.End
 > : >>
 > : >> Response.Write(application("BR_DATA_CONNECTION"))
 > : >> Response.End
 > : >>
 > : >> etc
 > : >>
 > : >> Cheers
 > : >> Ken
 > : >>
 > : >>
 > : >> "J L" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
 > : >> news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
 > : >> : hello,
 > : >> : I have a problem on a Windows 2000 Server sp4 where any asp page that
 > : >> : tries to connect to a database (SQL or Access) get's the following
 > : >> eror:
 > : >> :
 > : >> : -----
 > : >> : ADODB.Recordset error '800a0e7a'
 > : >> :
 > : >> : Provider cannot be found. It may not be properly installed.
 > : >> :
 > : >> : /TEST.asp, line 8
 > : >> : -----
 > : >> :
 > : >> : Example lines-
 > : >> : Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
 > : >> :
 > : >> : Site 2: set br = server.CreateObject("ADODB.Connection")
 > : >> : br.open application("BR_DATA_CONNECTION")
 > : >> :
 > : >> : Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
 > : >> : rsViews.ActiveConnection = shop_conection_STRING
 > : >> :
 > : >> : And so on, and so forth. Previously, the server has MDAC v2.7
 > : >> : installed, but after experiencing this today, I've upgraded to MDAC
 > : >> v2.8
 > : >> : and hotfix Q832483, but that hasn't fixed the problem.
 > : >> :
 > : >> : Any ideas? All are appreciated.
 > : >> :
 > : >>
 > : >>
 > : >
 > : > Hello. Thanks Ken,
 > : >
 > : > Here's one that stopped working:
 > : > MM_conTest_STRING = "dsn=test"
 > : >
 > : > And another:
 > : > Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
 > : > DBQ=C:\wwwroot\ob\fus\cated.mdb"
 > : >
 > : > And another:
 > : > application("SITE_DB_CONNECTION") =
 > : > "Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User
 > : > ID=***;Initial Catalog=***;ServerName=***;Database=***"
 > : >
 > : >
 > : > Here's one that still works:
 > : > MM_conManagement_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
 > : > Source=G:\wwwroot\site1\ob\fus\cated.mdb"'"dsn=***;"
 > : >
 > : > I hope that helps. Keep in mind that the top three all worked this
 > : > morning, and that like the last one, all JET connections still seem to
 > : > work. Crazy mdac.
 > : >
 > : > Any other ideas? I'll try anything to circumvent an OS reinstall
 > : >
 > : > Thank you in advance.
 > : >
 > :
 > :
 > : If it will help, I've also unreged and re-reged all the 2.8 DLL's like
 > : mentioned in the 2003-06-20 microsoft.public.data.ado post titled
 > : "Repair a corrupted MDAC 2.71 installation - the Solution"
 > :
 > : Found:
 > :
<font color=purple> > <a style='text-decoration: underline;' href="http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+installation+-+the+Solution%22&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=eBVyN%23yNDHA.1612%40TK2MSFTNGP11.phx.gbl&rnum=1</font" target="_blank">http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+insta...tion+-+</a>>
 > :
 > : Thanks.
 > :
 >
 >

Ken,

Everything looks good and it recognizes MDAC 2.8 RTM
There are two mismatches at the moment (bear in mind I've been changing
these all day):
ODBCBCP.DLL - expected v2000.85.1022.0 - installed is v2000.85.1025.0
msxml3.dll - expected v8.40.9419.0 - installed is 8.30.9926.0

J L<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

J L wrote:

 > Ken Schaefer wrote:
 >
  >> Hi, if you suspect your MDAC installation to be damaged, please
  >> download the
  >> ComCheck tool from:
<font color=green>  >> <a style='text-decoration: underline;' href="http://www.microsoft.com/data</font" target="_blank">www.microsoft.com/data</font</a>>
  >> and verify your MDAC components. Report back if there are any reported.
  >>
  >> Cheers
  >> Ken
  >>
  >>
  >> "J L" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
  >> news:%23PcZBZ8EEHA.1456@TK2MSFTNGP09.phx.gbl...
  >> : J L wrote:
  >> :
  >> : > Ken Schaefer wrote:
  >> : >
  >> : >> Response.Write() the values of the connection strings.
  >> : >>
  >> : >> Response.Write(MM_dbconnection_STRING)
  >> : >> Response.End
  >> : >>
  >> : >> Response.Write(application("BR_DATA_CONNECTION"))
  >> : >> Response.End
  >> : >>
  >> : >> etc
  >> : >>
  >> : >> Cheers
  >> : >> Ken
  >> : >>
  >> : >>
  >> : >> "J L" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
  >> : >> news:OqN6wk5EEHA.4008@TK2MSFTNGP10.phx.gbl...
  >> : >> : hello,
  >> : >> : I have a problem on a Windows 2000 Server sp4 where any asp
  >> page that
  >> : >> : tries to connect to a database (SQL or Access) get's the following
  >> : >> eror:
  >> : >> :
  >> : >> : -----
  >> : >> : ADODB.Recordset error '800a0e7a'
  >> : >> :
  >> : >> : Provider cannot be found. It may not be properly installed.
  >> : >> :
  >> : >> : /TEST.asp, line 8
  >> : >> : -----
  >> : >> :
  >> : >> : Example lines-
  >> : >> : Site 1: Rs.ActiveConnection = MM_dbconnection_STRING
  >> : >> :
  >> : >> : Site 2: set br = server.CreateObject("ADODB.Connection")
  >> : >> : br.open application("BR_DATA_CONNECTION")
  >> : >> :
  >> : >> : Site 3: set rsViews = Server.CreateObject("ADODB.Recordset")
  >> : >> : rsViews.ActiveConnection = shop_conection_STRING
  >> : >> :
  >> : >> : And so on, and so forth. Previously, the server has MDAC v2.7
  >> : >> : installed, but after experiencing this today, I've upgraded to
  >> MDAC
  >> : >> v2.8
  >> : >> : and hotfix Q832483, but that hasn't fixed the problem.
  >> : >> :
  >> : >> : Any ideas? All are appreciated.
  >> : >> :
  >> : >>
  >> : >>
  >> : >
  >> : > Hello. Thanks Ken,
  >> : >
  >> : > Here's one that stopped working:
  >> : > MM_conTest_STRING = "dsn=test"
  >> : >
  >> : > And another:
  >> : > Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
  >> : > DBQ=C:\wwwroot\ob\fus\cated.mdb"
  >> : >
  >> : > And another:
  >> : > application("SITE_DB_CONNECTION") =
  >> : > "Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User
  >> : > ID=***;Initial Catalog=***;ServerName=***;Database=***"
  >> : >
  >> : >
  >> : > Here's one that still works:
  >> : > MM_conManagement_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
  >> : > Source=G:\wwwroot\site1\ob\fus\cated.mdb"'"dsn=***;"
  >> : >
  >> : > I hope that helps. Keep in mind that the top three all worked this
  >> : > morning, and that like the last one, all JET connections still
  >> seem to
  >> : > work. Crazy mdac.
  >> : >
  >> : > Any other ideas? I'll try anything to circumvent an OS reinstall
  >> : >
  >> : > Thank you in advance.
  >> : >
  >> :
  >> :
  >> : If it will help, I've also unreged and re-reged all the 2.8 DLL's like
  >> : mentioned in the 2003-06-20 microsoft.public.data.ado post titled
  >> : "Repair a corrupted MDAC 2.71 installation - the Solution"
  >> :
  >> : Found:
  >> :
  >> <a style='text-decoration: underline;' href="http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+installation+-+the+Solution%22&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=eBVyN%23yNDHA.1612%40TK2MSFTNGP11.phx.gbl&rnum=1" target="_blank">http://groups.google.ca/groups?q=%22Repair+a+corrupted+MDAC+2.71+insta...tion+-+</a>
  >>
  >> :
  >> : Thanks.
  >> :
  >>
  >>
 >
 > Ken,
 >
 > Everything looks good and it recognizes MDAC 2.8 RTM
 > There are two mismatches at the moment (bear in mind I've been changing
 > these all day):
 > ODBCBCP.DLL - expected v2000.85.1022.0 - installed is v2000.85.1025.0
 > msxml3.dll - expected v8.40.9419.0 - installed is 8.30.9926.0
 >
 > J L
 >
 >

Time for some well-deserved sleep.

Gave the IUSR Read-Execute permissions on D:\Program Files\Common
Files\System\Ole DB\

Why this was never mentioned anywhere, I don't know. I wish I could say
that this was the problem in the first place. But between upgrading
MDAC, upgrading JET, re-applying a SQL service pack, AND changing these
permissions, it would be hard to reproduce, let alone help someone else
fix this problem.

Thanks.

-Josh<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a' 

"J L" <anonymous.TakeThisOut@discussions.microsoft.com> wrote in message
news:%23PcZBZ8EEHA.1456@TK2MSFTNGP09.phx.gbl...
 > J L wrote:
 >
  > > Ken Schaefer wrote:
  > > MM_conTest_STRING = "dsn=test"
  > >
  > > And another:
  > > Application("db") = "Driver={Microsoft Access Driver (*.mdb)};
  > > DBQ=C:\wwwroot\ob\fus\cated.mdb"


First don't use ODBC dsn! (in general). Nothing very bad about it, but it
requires to use an extra driver layer that you don't need.
use this
Provider=Microsoft.JET.OLEDB.4.0;data source=yourdb.mdb;user
id=admin;password=;"

<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;278604" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;278604</a>

second,

JET for IIS is really a bad idea and is a no-no when you talk about
reliability and scalability...<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: ADODB.Connection error '800a0e7a'