IIS - iis error - Asked By prasanna venaktesan on 11-Jun-11 06:07 AM

 

Microsoft JET Database Engine error '80004005'

Unspecified error



i am getting this error when i am calling one asp page.
Anoop S replied to prasanna venaktesan on 11-Jun-11 07:18 AM
There are several causes for this error message:
  • The account that Microsoft Internet Information Server (IIS) is using (which is usually IUSR) does not have the correct Windows NT permissions for a file-based database or for the folder that contains the file.
  • The file and the data source name are marked as Exclusive.
  • Another process or user has the Access database open.
  • The error may be caused by a delegation issue. Check the authentication method (Basic versus NTLM), if any. If the connection string uses the Universal Naming Convention (UNC), try to use Basic authentication or an absolute path such as C:\Mydata\Data.mdb. This problem can occur even if the UNC points to a resource that is local to the IIS computer.
  • This error may also occur when you access a local Microsoft Access database that is linked to a table where the table is in an Access database on a network server.
The following items correspond to the previous list of causes:
  • Check the permissions on the file and the folder. Make sure that you have the ability to create and/or destroy any temporary files. Temporary files are usually created in the same folder as the database, but the file may also be created in other folders such as the WINNT folder. For additional information about how to identify which folder does not have the correct permissions and how to configure temporary files, click the following article number to view the article in the Microsoft Knowledge Base:
    253604  (http://support.microsoft.com/kb/253604/ ) Microsoft Access 97 database connectivity fails in Active Server Pages
    If you use a network path to the database (UNC or mapped drive), check the permissions on the share, the file, and the folder.
  • Verify that the file and the data source name (DSN) are not marked as Exclusive.
  • The "other user" may be Microsoft Visual InterDev. Close any Visual InterDev projects that contain a data connection to the database.
  • Simplify. Use a System DSN that uses a local drive letter. If necessary, move the database to the local drive to test.
  • Follow the instructions in the following article to work around this problem:
    189408  (http://support.microsoft.com/kb/189408/ ) FIX: ASP fails to access network files under IIS 4.0 and IIS 5.0
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306269
Anoop S replied to prasanna venaktesan on 11-Jun-11 07:20 AM
Refer this KB article also (This problem may occur if IIS 7.0 is configured to load the current user profile for an application pool identity. This may cause compatibility issues with legacy ASP-based applications and ADO-based applications because the current user may not have sufficient permissions to write to the temporary directory.)

http://support.microsoft.com/kb/926939
Kirtan Patel replied to prasanna venaktesan on 11-Jun-11 08:07 AM
hello ,

Check the permissions on the file and the folder. Make sure that you have the ability to create and/or destroy any temporary files. Temporary files are usually created in the same folder as the database, but the file may also be created in other folders such as the WINNT folder. For additional information about how to identify which folder does not have the correct permissions and how to configure temporary files
Jitendra Faye replied to prasanna venaktesan on 11-Jun-11 10:39 AM
This usually happens in one of the following scenarios:
  • you referenced your connection incorrectly (e.g. spelled the DSN name, or one of the DSN-less string components wrong);
  • you referenced a DSN that doesn't exist;
  • the user connecting to the DSN or DSN-less connection doesn't have access to the information stored in the registry (see KB #306345);
  • you used an English or localized driver detail for your connection string when your system is not set up in that language (seeKB #174655); or,
  • you are missing the connection string entirely (this can happen if you maintain your connection string in a session variable, and your sessions aren't working; see Article #2157).
FOLLOW THIS LINK-


HOPE THIS WILL HELP YOU.