Discussion Locked

OLE DB Provider for ODBC Drivers error '

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After I justed the swap space on our server's C drive from 384MB to 128MB. The jet engine on the server started giving errors like those below. How can I effectively troubleshoot this?

*********************************************
[Microsoft][ODBC Text 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.

The following error occurred:

[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
*********************************************

[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.

5 replies

by raffi_

I don't know that it has anything to do with the swap file.

For the ACCESS error:
ODBC will give you errors like the 2nd one if the app has left the lock file open. Make sure the app is not being used and do a search for *.ldb (Access lock file) and delete it.

For the Text Driver error:
Are you running MS_SQL as well as Access? Or does your Access app use remote files of any kind?

regards
Raffi

by serwee98

For the ACCESS error:
There's no .ldb file. The MDB is used to store data for dynamically creating a menu using JavaScript & DHTML. Problem wasn't resolved after rebooting.

For the Text Driver error:
Yes we are using both SQL 6.5 & Access. However, the ODBC text driver is for reading a comma-separated file using ADO in an ASP. Nothing to do with SQL/Access. Anyway, the ASP has been working for many months. In any case, all our Access using local files.

by mark.thomson

See MSDN Article Q183060 for tips on how to troubleshoot this error message.

Most of the problems to do with this error message and IIS seem to revolve around NT file permissions and the anonymous user account that IIS uses.

Check that the IIS Anonymous account has read permission for the folder(s) used to store your text file(s) (and for the text files themselves) - permissions might have been changed, the account might have been changed , the folder might have been changed or the file might have been created elsewhere inheriting its file permissions from the folder it was created in thus not have the required permissions.

User accounts attempting to read .mdb files may need to create/update an .ldb file. To test this - open the.mdb (using msaccess) with an account that can create files in its current folder, do this again simultaneously and a .ldb file should be created, change the file permissions _for the .ldb file only_ to full control for your IIS anonymous account and then try using your Javascript/dhtml app

by serwee98

Thanks! I solved the problem before seeing this advice. The administrator redirected the environment variables 'TEMP' & 'TMP' from 'C:\Temp' to 'E:\Temp' without setting appropriate NTFS permissions.

This discussion is closed to new replies.