[ODBC Microsoft Access Driver] Disk or network error - HELP!!!

[cyberbob2]

I've been researching this for three days now. For the past 2+ years I've had local ASP apps working fine with Access databases I use to test with. All of a sudden, I start getting this error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] Disk or network error. I've done the following after going to the MSKB and support, asp faqs, IIS faqs and other posts:

Set permissions in all the applicable folders and files for IUSR and IWAM (includes

http://wwwroot,

app folders, temp folders (for temp jet files), .mdb files, etc.)

Checked my MDAC version (2.7)

Set the anonymous user in IIS to IUSR with Windows Authentication

Made sure the env vars were set for the temporary jet files

Tried replacing the access databases

Tried a supposed fix in the registry with security permissions

Checked my system for any viruses or spyware that may have affected this

Seems that no matter what I do, NOTHING works and I still get this &#$@! error. Should I just reinstall IIS and see if that works?

Thanks in advance,
KP

 

[Sheco]

I suppose you already checked that you can open the .mdb in the MS Access application and that the .mdb file itself is not Read-Only?

 

[cyberbob2]

Yes, it is not read only and I have no problem opening the .mdb file.

 

[damber]

Have you tried it with a DSN-less connection string, rather than using ODBC ?

Also, you could try removing the anonymous user access and login with an admin account - this will help re-assure you that permissions are *almost* certainly not affecting it.

Other than that, try copying the exact same set-up to another computer, and see if the same error occurs - if it does, then it is likely to be the set-up, if it doesn't, it is likely to just be the computer in question (i.e. not your code/config).

Also, check if you've disabled parent paths in IIS and have the database outside of your webroot - I can't remember if this causes a problem or not for internal script access to local files, but worth checking.

As you state, you could also try un-installing and re-installing IIS.

A smile is worth a thousand kind words. So smile, it's easy!