PRB: Framework 1.1 installation breaks ASP3.0 websites that use MS Access

  • Thread starter Thread starter Sam Vanhoutte
  • Start date Start date
S

Sam Vanhoutte

Hello,

I installed the Microsoft .NET framework 1.1 on our Windows 2000 std server.
That server hosts five ASP3.0 websites and four ASP.NET websites. The
ASP.NET websites are using SQL Server and everything works fine with these
websites. But the ASP3.0 websites are using MS Access with a DSN name for
their database access.

My problem is that all the ASP3.0 pages with database access stopped working
after the installation. These sites use the IUSR_Machine account for the
anonymous user. I tried several things that I found on the newsgroups, but
with no result...

- I installed MDAC2.7 SP1
- I started regedt32 and gave Everyone read access to the DSN key
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
- I gave everyone full access on the mdb file, but that didn't work (i
removed the full access, afterwards, off course)

- The last option was to specify the administrator account for the anonymous
user. That worked off course. Everything is fixed now, but this option is
just a temporary option for security reasons.

Does someone know what the problem can be with my data access?

Thanks in advance!

kind regards,
Sam Vanhoutte
 
Try giving the IUSR account access to write to the folder with the Access
database, if you have not tried that yet. A common problem with Access is
the directory does not have write priveleges, which stops the user account
from creating the lock file (.ldb), which is necessary to access Access.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
Cowboy (Gregory A. Beamer) said:
Try giving the IUSR account access to write to the folder with the Access
database, if you have not tried that yet. A common problem with Access is
the directory does not have write priveleges, which stops the user account
from creating the lock file (.ldb), which is necessary to access Access.
Click to expand...

The IUSR Account has full access to the directory of the MS Access database,
so that is not the problem.

thank you for the answer
 
Back
Top