Windows XP Pro x64 and Jet 4.0

I am trying to work with my database driven .asp files and once I add a call to my asp files I get the following message:

ADODB.Connectionerror '800a0e7a'

Provider cannot be found. It may not be properly installed.

/cedar-springs/admin/includes/inc.dbopen.asp, line 25

It seems that in Windows XP Pro x64 the Microsoft Jet 4.0 provider can not be registered. I have installed the lastest version of .net frame that i can find and this still does not work. Any help would be greatly appreciated.

the code in the inc.dbopen.asp file is below:

Dim conn

Set Conn = Server.CreateObject("ADODB.Connection")
Conn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source="
Conn.ConnectionString = Conn.ConnectionString & "C:\Inetpub\wwwroot\cgi-bin\db\cedar-springs\cedar-springs.mdb;"
conn.Open

[1152 byte] By [DonaldSechrest] at [2008-1-27]
# 1

anyone else found a way around this, i just installed win64 xp pro and am setting things up...i just ran across this same thing and what use to work on winxp pro 32bit no longer works in my iis....

anyone help?

DeuceLoosely at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...
# 2

anyone can hlep?

the same !

hjt at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...
# 3

The jet database engine has not been ported to 64bit. Therefore you will have to get IIS/ASP running in 32 bit mode and use the 32 bit jet driver. This article shows how to get IIS/ASP sessions running in 32 bit http://support.microsoft.com/?id=891314 .

Jet is deprecated. The above is offered only as a work around to keep you running for now. Based on the current resources on Jet you should expect no additional updates on Jet engine and providers. You should be actively moving your application the SQLServer 2005 Express. http://www.microsoft.com/sql/editions/express/default.mspx

BradRhodes-MSFT at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...
# 4
You can force the SQL

Server Agent to execute the 32-bit version of DTExec by setting up the

job as a CmdExec task instead of an SSIS package call, as detailed

here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

MatWakefield at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...
# 5

Hi ,

I have few doubts. Could you plz clarify them. Still i have not even seen Vista OS, so sorry for basic qns.

1) Whether Microsoft Jet 4.0 is available only for 32 Bit Vista ? if so, is it backward comapatible ( does that support Win 2K,2k2,2k3,XP versions also )?

2) Data connectivity components which are available for Office 2k7 supports backward compatibility ( supporting from Win 2k to latest one) ?

3) Currently i have a stabilised application which had OLEDB Support for Win 2k, 2K2,XP. Now i would like my application to support Vista (which contains office 2007) also .

regards,

Mahesh

mallamahesh at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...
# 6

okay, i get it. its not there anymore. i tried using the C:\WINDOWS\SysWOW64\odbcad32.exe for a DSN connection and got this error:

ADODB.Command error '800a0ea9'

Provider is not specified and there is no designated default provider.

/Default.asp, line 16

Im pretty much pissed off! can anyone help me from this?
snuke at 2007-9-8 > top of Msdn Tech,SQL Server,SQL Server Data Access...

SQL Server

Site Classified