Microsoft Jet Datbase Engine error after moving DB

[aabraham]

Hi

I have a internally built Access based front end application that hooks into a SQL Server backend. The client works fine from Windows 2003 32 bit system. I tried to get the client to run from a 64 bit Windows 2008 R2 Server. I can login to the DB but get the following error:

Microsoft Office Access
The Microsoft Jet database engine cannot open the file xxxxxx. It is already opened exclusively by another user, or you need permission to view its data.

Detailed information:
1. The database front end is based on Microsoft Access 2003 (App wont work with newer versions of Access). MS Access 2003 is currently running on a Windows 2003 32 bit Citrix server and it works fine
2. The database back-end is running on Windows 2008 SQL Server
3. The MDB file resides on a central network location
4. The only thing required in the past to get the Application to work is to create a ODBC SQL connection and install MS Access 2003 on Citrix Server
5. User access is fine as the Application works on the old 32 bit Citrix system


6. IIS is not installed nor is it needed
7. Not a locking issue as I have up to 20 users accessing the DB from the old Citrix system at any one time. Application only fails on Windows 2008 64 bit system

The new OS system is Windows 2008 R2 64 bit but the version of MS Access 2003 installed in 32 bit. Has anyone seen a similar issues?

Thanks

[ItsMe]

What version of Access created the BE file?

[aabraham]

Access 2003

[ItsMe]

So you have a single MDB file that was created with Access 2003 that resides on a file server? This file has as many as 20 concurrent connections to it a given time by various PC's on the network? This single file uses ODBC connections to SQL server? You have a second MDB file that acts as a front end that resides on Server 2008 R2 and this file is not opening when accessed from PC's on the network?

You will need the correct drivers on the 2008 R2 server to make the ODBC connection to SQL server. However, the fact that the MDB file is not opening causes me to believe that there are some settings that should be checked. When defining the DSN there are advanced options for the System Database to open the DB in exclusive mode.

Additionally, there are settings within the DB to open exclusively.

User permissions can also cause this to happen if you set them up

An mdb file that crashes may leave behind an ldb file. This ldb file can sometimes cause this symptom. Make sure nobody else has the mdb file open and move or delete the ldb.