Clearing Error 3045

[DaveSlade72]

I cannot compact or repair an Access 97 database due to Error 3045 - File in use.
If I close the database, there is no ldb file left open, so the database should not be locked, and there are no other users logged into the database which resides on our server.
I can copy the database to another folder, compact it and copy it back with no problems, but the server version is still apparently locked. Where is this file lock infrormation held if it is not in an ldb file? Can I re-set this setting in any other way?

I'd apreciate any thoughts on this.

Dave Slade
Cardiff

[MMcCarthy]

I cannot compact or repair an Access 97 database due to Error 3045 - File in use.
If I close the database, there is no ldb file left open, so the database should not be locked, and there are no other users logged into the database which resides on our server.
I can copy the database to another folder, compact it and copy it back with no problems, but the server version is still apparently locked. Where is this file lock infrormation held if it is not in an ldb file? Can I re-set this setting in any other way?

I'd apreciate any thoughts on this.

Dave Slade
Cardiff

When the database is open does the ldb file appear where you expect it to be?

[DaveSlade72]

When the database is open does the ldb file appear where you expect it to be?

Yes it does.

[MMcCarthy]

Yes it does.

When you compact and repair even if the file is locked by another user the database copies itself first and then overwrites itself so it should be creating a copy of itself in the folder even if the file is locked so I don't think this is your problem.

You say you copy the file and compact and repair it no problem. Are you doing this in the same folder. What I am wondering is if the problem is more one of write privilages in the folder than the database itself.

The only other option I can think of is that there is corruption but this doesn't make sense if you can copy it and its fine.

Mary

[NeoPa]

Try speaking to your Network people.
There may be special permissions on the folder as MMcCarthy says.
I could go through all sorts of technical ways of finding the problem (which you may well not follow) but the more sensible course is to ask them to assist you with determining and then, if necessary, fixing the problem.

[DaveSlade72]

Try speaking to your Network people.
There may be special permissions on the folder as MMcCarthy says.
I could go through all sorts of technical ways of finding the problem (which you may well not follow) but the more sensible course is to ask them to assist you with determining and then, if necessary, fixing the problem.

The problem is, I am our Network people! We are a very small not-for-profit organisation and I deal with all the IT issues, including the server management etc. Hence I tend to rely alot on forums such as this to solve problems that I have no experience of. There are only four of us in the office, and none of the others have any reason to go near this database, or interact with the server directly.

The problem has only recently arisen, and I think it is related to an attempt at automating an update process. I've just successfully compacted a re-named version of the database in the same folder as the original. I had thought maybe I could simply delete it and use the renamed version instead... but of course I can't because it thinks its in use by another user!

[NeoPa]

Right then. That makes sense.
Are your MDB files stored on a separate PC or are they on your workstation?

1. Go to your server machine.
2. If not possible then do NOT skip over steps #5-6
3. Open Computer Management (Use Admin Tools or %SystemRoot%\system32\compmgmt.msc /s)
4. Go to step #7
5. Select Action / Connect to another computer.
6. Select your server PC from the list and enter
7. Select System Tools / Shared Folders / Open Files.
8. Look through this list for the information as to who has access to the file(s)
9. Force close of the file(s) if (ONLY IF) appropriate.

[DaveSlade72]

Right then. That makes sense.
Are your MDB files stored on a separate PC or are they on your workstation?

1. Go to your server machine.
2. If not possible then do NOT skip over steps #5-6
3. Open Computer Management (Use Admin Tools or %SystemRoot%\system32\compmgmt.msc /s)
4. Go to step #7
5. Select Action / Connect to another computer.
6. Select your server PC from the list and enter
7. Select System Tools / Shared Folders / Open Files.
8. Look through this list for the information as to who has access to the file(s)
9. Force close of the file(s) if (ONLY IF) appropriate.

The file is on the server, and as far as the server is concerned the file is not open. When I open the file on the workstation the mdb & ldb files appear in the open files list, but when it's closed they disappear again.

[NeoPa]

Can you try to make a copy of your MDB file into the same folder with a different name and let me know what happens.

[DaveSlade72]

Can you try to make a copy of your MDB file into the same folder with a different name and let me know what happens.

I can create a copy in the same folder, and I have no problem doing anything with that copy. This is what makes the situation all the more irritating, since I could simply replace the one that doesn't work with one that does... but I can't delete or rename the one that thinks it's locked!

[DaveSlade72]

I can create a copy in the same folder, and I have no problem doing anything with that copy. This is what makes the situation all the more irritating, since I could simply replace the one that doesn't work with one that does... but I can't delete or rename the one that thinks it's locked!

I've just looked at the processes currently running on the Server, and there is an NMSAccess.exe process running whilst as far as I can see there are no open databases. Can I simply stop this process do you think?

[NeoPa]

(How to remove NMSAccess error) should tell you more about it.

[DaveSlade72]

(How to remove NMSAccess error) should tell you more about it.

Thanks - looks like it's got nothing to do with Access, so probably not related to my file - locking problem.

[NeoPa]

I'm afraid I can't think why this is happening Dave.
Everything you say seems logical. You've already tried any other ideas I've had :(
Sorry.

[MMcCarthy]

Thanks - looks like it's got nothing to do with Access, so probably not related to my file - locking problem.

Dave can you copy out a backup of the file and compact and repair it. Then delete the existing file and replace with the backup. Does this make any difference?

[DaveSlade72]

Dave can you copy out a backup of the file and compact and repair it. Then delete the existing file and replace with the backup. Does this make any difference?

I've just taken my happily working duplicate of the database from the folder that the locked version is in, copied it to a different folder, renamed it and over-written the locked database. The new version of the database is now locked.

I cannot create a backup using the windows backup facility bacause it's apparently in use by another process!


Backup Status
Operation: Backup
Active backup destination: File
Media name: "Backup.bkf created 17/01/2007 at 13:34"

Backup of "S: \\Sewbrecserver\SEWBReC"
Backup set #1 on media #1
Backup description: "Set created 17/01/2007 at 13:34"
Media name: "Backup.bkf created 17/01/2007 at 13:34"

Backup Type: Normal

Backup started on 17/01/2007 at 13:35.
Warning: Unable to open "S:\M. MapMate files\SEWBReC(MM).mdb" - skipped.
Reason: The process cannot access the file because it is being used by another process.


Backup completed on 17/01/2007 at 13:35.
Directories: 2
Files: 0
Bytes: 296
Time: 1 second

[NeoPa]

I think Backup in this case simply means a file copy.
This is similar to ideas referred to in post #6.

[DaveSlade72]

I think Backup in this case simply means a file copy.
This is similar to ideas referred to in post #6.

Sorry, I mis-understood. Still, it was worth a try!

Assuming that the database really does have an active process running somewhere (either on the workstation or the server), is there any way of finding out what that process might be so that I can simply stop it?
Obvioulsy, I could simply restart the server, but I don't want to disrupt the other two members of staff as we've got a lot on at the moment.

[NeoPa]

My response in post #8 was designed to do just that. Unfortunately, the results you got surprise me and I'm unable to interpret them into anything that makes sense. That would be the tool for that task though :confused:

[DaveSlade72]

My response in post #8 was designed to do just that. Unfortunately, the results you got surprise me and I'm unable to interpret them into anything that makes sense. That would be the tool for that task though :confused:

Well thanks very much for trying. When I get the chance to re-boot the server I'll let you know if the problem goes away!

[DaveSlade72]

Well thanks very much for trying. When I get the chance to re-boot the server I'll let you know if the problem goes away!

Re-booted the server this morning before the others got into the office, and the problem has gone away. All very mysterious!

[NeoPa]

A problem gone is a problem ... well ... gone I suppose :)