I have an Intranet published with IIS 5 on a WK2 server. My problem is that the site is ASP and I can't get the ASP pages to view. The error I get is:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
/accounts/default.asp, line 30
line 30 refers to the DSN connection. I have checked on the web server that there is a DSN connection to the .mdb file that the site runs from.
I have also checked that the account used for anonymous authication has the same password as that on the web server. I have checked the NTFS permissions for the folder that contains the .mdb file and I can't seem to find a reason why the ASP aspects wont work.
Bearing in mind that at the moment I only want users to be aboe to view the site internally. Is there a more steamlined way of setting permissions to avoid possible conflicts between NTFS and IIS permissions. Could I have no NTFS and leave the security up to IIS?
If anybody has any pearls of wisdom. I would be most grateful. :-(
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
/accounts/default.asp, line 30
line 30 refers to the DSN connection. I have checked on the web server that there is a DSN connection to the .mdb file that the site runs from.
I have also checked that the account used for anonymous authication has the same password as that on the web server. I have checked the NTFS permissions for the folder that contains the .mdb file and I can't seem to find a reason why the ASP aspects wont work.
Bearing in mind that at the moment I only want users to be aboe to view the site internally. Is there a more steamlined way of setting permissions to avoid possible conflicts between NTFS and IIS permissions. Could I have no NTFS and leave the security up to IIS?
If anybody has any pearls of wisdom. I would be most grateful. :-(
