Why do I get "Could not find file '(unknown)'" errors using the Access ODBC driver with the ODBC-ODBC Bridge?

This problem usually occurs when the Microsoft Access MDB file specified in the ODBC data source can't be found. Another cause is file permissions.

In ODBC Data Source Administrator, open the Microsoft Access System DSN you're using with the Easysoft ODBC-ODBC Bridge. The MDB filename should be shown (select the MDB path if you can't read all of it). Does the file exist? Is it on a mapped drive that's no longer mapped?

If the file exists, check:

  • The permissions on the file. The file needs to be readable and writable by the user your ODBC-ODBC Bridge client logs on as. This user is the LogonUser attribute value in your ODBC-ODBC Bridge data source.
  • If the MDB file is on a mapped drive, check that the LogonUser value is the same user who mapped the network drive. For example, if user XXX is interactively logged into a Windows server and maps drive H from a network share, no user other than XXX will have access to the mapped drive.
  • Does the MDB file link to a table in another MDB file that's on a network drive? If so, refer to the previous point.
  • Make sure the System environment variable TEMP is set to a directory that LogonUser has access to.

    To do this, select the Advanced tab in Control Panel > System Properties. If necessary, edit Environment Variables > Temp. Use the OK button to save your changes and exit the dialog boxes.

  • Make sure LogonUser has permission to create temporary files in the same directory as the MDB file.
  • Does another process or user have the MDB file open?

You may also get error "80004005 in Active Server Pages and Microsoft Data Access Components." If this is the case, check all of the above, plus:

  • Does the account that Microsoft Internet Information Server (IIS) is using have the correct Windows permissions for a file-based database or for the directory that contains the file. IIS usually runs under the IUSR account.
  • Is the MDB file marked as Exclusive?
  • The error may be caused by a delegation issue. Check the IIS authentication method.