ASP pages not working with MS Access on Win 2003 svr

[Ovatvvon]

Hi all,

I have a windows 2003 server that we run SQL 2000 and 2005 on. I just put a website on there that uses MS Access, but it won't work because there is no driver for it. I thought this was part of the O.S., but I guess not.

I downloaded MDAC 2.8 and installed, but it still doesn't work, stating that the driver is not installed, or is not configured correctly. I tried using both the JET and ODBC connections, to no avail.

Does anyone know what I may be doing wrong? This is a 64bit system, so I'm not sure if that has anything to do with it. I tried downloading and installing the 64bit patches for the MDAC as well, but it still did not work. Not sure what is going on here.

Can anyone help?


-Ovatvvon :-Q

 

[onpnt]

Try this

http://forums.iis.net/t/1066385.aspx

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[Ovatvvon]

Hi Onpnt,

Thanks for the response.

I think that may work with Windows Vista, however, with windows 2003 server, I do not have the appcmd file on my system. I do not have an advanced settings area in the UI, and when I use the command line, I receive the following error:

C:\>C:\WINDOWS\system32\inetsrv\appcmd set AppPool 32-
Bit-App-Pool -enable32BitAppOnWin64:true
'C:\WINDOWS\system32\inetsrv\appcmd' is not recognized as an internal or external command,
operable program or batch file.

C:\>




-Ovatvvon :-Q

 

[esaragosti]

Hey there,
I had similar errors. MS Server 2003 has higher security than 2003, so they added the "feature" That you need to share the dlls for the odbc to your local user. It took me a week to figure it out, since the logic to this decision escapes me.

Try reading this:

http://support.microsoft.com/kb/238971

Hopefully it'll be of help. Unfortunately I don't remember the details, I just remember that for the sake of security, you have to give the machine permission to use the ODBC.

Eric

 

[Ovatvvon]

Hi Esaragosti,

I looked at that, and thought it was going to work, but alas, it didn't. I still receive the same error on the ASP page:

ADODB.Connection error '800a0e7a'

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


Perhaps this was for a different version, but there was no "security" tab, like it said in the MS article. I did still find the permissions though, and altered them to allow everyone to have full control - to no avail.

This is confusing to me. I'm sure it is probably some simple setting somewhere that takes 2 seconds to change, but the question is what is the required change to make it work.



-Ovatvvon :-Q