> Script fragment below is run in the following enviroment: > WinXP Home ed. + MSAccess 2000 + ActivePerl (both PerlIS.dll or > Perl.exe) > Script executed from the command prompt works OK, connecting > to the database and displaying its contents. Same script, > when run as CGI, displays initial message and hangs, > presumably when trying to connect to the database (diagnostic > messages following DBI->connect do not get displayed). Script > does not display any error messages, just hangs indefinitely.
[snip] > Other CGI scripts (not using DBI) work fine. Proper operation > when invoked from the command prompt lets me think that ODBC > source is properly configured (system DSN). The database > seems to be located in the world-readable directory, however > the only possible source of the problem coming to my mind are > the access rights of the IUSR_WINXP (being the privilege > level bound with IIS). Most of the info available on the net > covers Apache/*nix environment, where I do manage myself. Has > anyone WinXP experience to share (I am not a WinXP expert)? > This is (at least somewhat) covered in the DBI FAQ and DBD::ODBC's POD documenation. If you come across something different than what's there, let me know. I'll happily add to it. DBI FAQ (www.xmlproj.com/cgi/fom.cgi) To summarize, you are probably on the right track with checking on IUSR_WINXP. However, there are a variety of factors. Using a system DSN is good. Check NTFS permissions on the database file(s) and directories leading up to and including the directory for the file (ensure that the directory is writable, too, since Access will create the .ldb for locks). IUSR_WINXP will only have local system access, but that's probably what you are doing anyway, since you say XP Home (which should eliminate the network issues addressed in the above referenced information, but if for some reason you are counting on a network share, then you'll have issues with Home edition and the services in general). I'd also check to see if you have any security on the database itself and is the .mda (?) accessible to IUSR_WINXP. Something to try: allow IUSR_WINXP to logon and login as IUSR_WINXP and run your scripts. See what it says. If ISUR_WINXP can't login interactively, then create a local user (dummy) and try that... Just some thoughts. Regards, Jeff
