Microsoft jet database cannot open file "..." It is already open exclusively by another user or you need permission to view its data

Question

I have a WinForms application that I got support over, and it was created using Visual Studio 2005 with VB.Net. The application uses the Access database. It works great when it is installed as a standalone application, but the installation CD for the application also allows you to install the network, and in this I run into problems.

To verify the network installation, I created a folder on my server (Windows Server 2003 Service Pack 2) and copied the Access database to this folder. I created a share for this folder and gave everyone full access to this folder. Then on the workstation I installed the application and gave the database path as follows:

\\ MyServer \ MyShare \ mydb.mdb

(Installation steps are performed in accordance with the instructions on the installation CD)

The workstation on which I installed it is Windows 7 Ultimate. When I launch the application, I get the error message indicated in the header when the application tries to read the database file. I confirmed that I can write to a shared folder on the server, so I don't think this is a permission issue. In addition, the database file is not used at all, so it is definitely not open exclusively. Does anyone know what could be causing this and what can I try to make it work?

UPDATE:

I tested the installation of a workstation on a computer with a fresh installation of Windows XP SP3 and was able to access the database file without any problems. It seems that this error that I am getting is somehow specific to Windows 7. Maybe there is a known problem with Oledb drivers in Windows 7? My version of Windows 7, by the way, is 32 bits.

Answer 1

There can be so many, so it’s hard to give an exact answer. However, I had a similar problem, and I wrote a post that I don't want to duplicate here:

http://walkinghumble.wordpress.com/2009/02/20/cannot-connect-to-an-access-mdb-file-located-on-the-network-through-oledb/

Perhaps this will help if the underlying problem is the same (although in my case it was an ASP.NET application). If it will not, at least advance the process monitor, if you still do not know it.

Answer 2

Jet 4.0 will not be able to open the access file without a link to the COM version of "Microsoft ADO Ext 2.8 for DDL and Security" in the project link settings. To check the status of links, do: Project → References → COM.

Other important references for this work are:

"Microsoft ADO Data Control 6.0 (OLEDB)" COM Link

"Microsoft Access Object Library 14.0" COM Link

Answer 3

Access sometimes reports this error if you have an unsolicited MS Access process on your own machine. Check the process list of the task manager (not the application).

Answer 4

Try to run these things ...

• Are these computers in a domain? If this is a Win 7 field joined to a domain?
• Did you set permissions when logging in to the server - or did you set permissions from a share on another machine? Set permissions on the server itself.
• In the Win 7 window, make sure that you can open the share on the 2003 server and change the name of the access file (just like a test, change it back).
• Do you have Access installed in the win 7 window? If so, see if you can access the resource and use access to open .mdb.