How to run a 32 bit ASP-Access application in Windows Server 2008 64 bit

[Matsam]

Hello,

I have developed an application in ASP and MS-Access 2010 as back end. It works fine in the localhost in Windows 7. But when I installed it in IIS7 in a Windows Server 2008 64 bit server, only the first html page is displaying. It gives the following error message on calling the ASP page.

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

I have used the following connection string:

Connectstr = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\inetpub\wwwroot\transaction\dep.accdb;Persist Security Info=False;"
 
cn.open connectstr

Is this an issue of 32bit - 64bit? Another .Net application is working in the same server. Other simple ASP files also works fine in it.

Can anyone help me in solving this issue? What should be done to run a 32 bit application in it? Will it affect the other .Net application which is already running?

Thanks in advance

Matsam

[zmbd]

First this is out the realm of my expertise; thus, all can offer is some basics. I’m sure that you’ve probably already tried these things; however, sometimes going back and checking that the plug is actually in the socket and that the cat hasn’t knocked it lose is the best place to start.
:-)

So, let's start with the basics:
(please actually go to the following link too as there is more information there:

Why do I get 80040200 / 80040514 / 800A0E7A errors?

{/...\}
Access

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. A major source of this problem is that Microsoft stopped shipping the JET files with MDAC, starting at 2.6 (see KB #271908), so many machines set up starting at that baseline or later do not have the necessary JET runtime files.

See Article #2342 for information on getting the most recent version of the JET provider.

Other problems with Access include fat-fingering the connection string, or mixing up Access and JET parameters, e.g:

Driver={Micrsoft Axess Diver (*.mdb)};DBQ=c:\file.mdb 
(several misspelled words) 
 
Driver={Microsoft Access Driver (*.mdb)};Data Source=c:\file.mdb 
(DBQ is the parameter for database location with the Access driver) 
 
Provider=Microsoft.Jet.OLEDB.4.0;DBQ=c:\file.mdb 
(Data Source is the parameter for database location with the JET provider) 

See Article #2126 for sample Access connection strings to help model your own.
{...}

This seems a little old as the connection strings for the newer versions of Access use the ACE engine so the connection string should be something like (note: I am using this to connect to a text file; however the general concept should be the same, just change the extended properties):

zstrcn = "Provider=Microsoft.ACE.OLEDB.12.0;" & _
        "Data Source=" & zstrdatadirectory & _
        "; Extended Properties=""text;HDR=Yes;FMT=Delimited(,)"";"