|
 |
access thread: RE: Access File Locking
Message #1 by "Beverley Usher" <bUsher@h...> on Tue, 20 Mar 2001 08:00:18 +0000
|
|
Access 97 files on one of my servers are locking themselves down. All of
the files have been working well in a multi-user environment (and the
same files on three other servers are fine), but on one server, a file
will suddenly insist that it is in use and cannot be used by anyone
else. This is true even early in the morning when no one is at the site.
Even as supervisor/owner of the files, I cannot delete them or change
their name, or delete the directory they are in. The only work-around I
have found so far is to rename the entire directory, create a new one
and put new copies of the files there. The directory I had to recreate
this morning is 700 MB so I really do not want to have to do this much
longer.
Has anyone had a similar problem? Does anyone have any ideas of how to
solve this or of better work-arounds?
Any and all help appreciated.
Beverly
Message #2 by "Jeff Harrington" <jsh@s...> on Wed, 21 Mar 2001 14:12:18
|
|
Beverly,
If an .ldb file exists for the .mdb file (the database), then the database
believes it still has a connection to someone. The first step I take when
I believe everyone is out is to try and delete the .ldb and compress the
database. If that does not work, then open the .ldb with notepad. You will
see all the computer names of systems that opened the database previously.
The computer names will show when someone opens the database, but do not
get removed when a person exits the database. This will give you a group
of computers to go check out. It very well could be that someone is not
out of the database (the most common problem). If that's the case, just
close them out of the database and you are all set. If no one has any
instances of the database open, look for ghosts (An instance of Access
open in the system tray, but showing no database). End task on Access
twice to get rid of it. If this still does not fix the problem, my next
move is to reboot the systems on the .ldb list. Sometimes asking the users
if they had errors or other problems the last time they had the database
open will give you an idea of which to try first. The most common problems
are those users who have errors, corrupt the database just a little, exit
Access, but never turn off their PC at night. Reboot that PC and you will
almost always fix the problem. In 2 1/2 years of administering Access
databases, I have yet to find a case where I had to recreate the folders,
etc. I hope this helps.
Best of luck,
Jeff H
> Access 97 files on one of my servers are locking themselves down. All of
> the files have been working well in a multi-user environment (and the
> same files on three other servers are fine), but on one server, a file
> will suddenly insist that it is in use and cannot be used by anyone
> else. This is true even early in the morning when no one is at the site.
> Even as supervisor/owner of the files, I cannot delete them or change
> their name, or delete the directory they are in. The only work-around I
> have found so far is to rename the entire directory, create a new one
> and put new copies of the files there. The directory I had to recreate
> this morning is 700 MB so I really do not want to have to do this much
> longer.
>
> Has anyone had a similar problem? Does anyone have any ideas of how to
> solve this or of better work-arounds?
>
> Any and all help appreciated.
>
> Beverly
Message #3 by "Beverley Usher" <bUsher@h...> on Wed, 21 Mar 2001 15:03:58 +0000
|
|
Thanks for the suggestions. I will keep this on file. Unfortunately, my
problem at the moment is that the server where the locked files are is
well off-site and there is no one there who is at all technical, so I
can't really do much. But I think the problem is probably with the
server - we're having other problems with it. And, get this, there is NO
.ldb file for the file that has locked! Anyway, I'm sure I'll have
occasion to use your suggestions on site some time in the not too
distant future.
Beverly
>>> jsh@s... 21/03/2001 2:12:18 PM >>>
Beverly,
If an .ldb file exists for the .mdb file (the database), then the
database
believes it still has a connection to someone. The first step I take
when
I believe everyone is out is to try and delete the .ldb and compress
the
database. If that does not work, then open the .ldb with notepad. You
will
see all the computer names of systems that opened the database
previously.
The computer names will show when someone opens the database, but do
not
get removed when a person exits the database. This will give you a
group
of computers to go check out. It very well could be that someone is not
out of the database (the most common problem). If that's the case, just
close them out of the database and you are all set. If no one has any
instances of the database open, look for ghosts (An instance of Access
open in the system tray, but showing no database). End task on Access
twice to get rid of it. If this still does not fix the problem, my next
move is to reboot the systems on the .ldb list. Sometimes asking the
users
if they had errors or other problems the last time they had the
database
open will give you an idea of which to try first. The most common
problems
are those users who have errors, corrupt the database just a little,
exit
Access, but never turn off their PC at night. Reboot that PC and you
will
almost always fix the problem. In 2 1/2 years of administering Access
databases, I have yet to find a case where I had to recreate the
folders,
etc. I hope this helps.
Best of luck,
Jeff H
> Access 97 files on one of my servers are locking themselves down. All
of
> the files have been working well in a multi-user environment (and
the
> same files on three other servers are fine), but on one server, a
file
> will suddenly insist that it is in use and cannot be used by anyone
> else. This is true even early in the morning when no one is at the
site.
> Even as supervisor/owner of the files, I cannot delete them or
change
> their name, or delete the directory they are in. The only work-around
I
> have found so far is to rename the entire directory, create a new
one
> and put new copies of the files there. The directory I had to
recreate
> this morning is 700 MB so I really do not want to have to do this
much
> longer.
>
> Has anyone had a similar problem? Does anyone have any ideas of how
to
> solve this or of better work-arounds?
>
> Any and all help appreciated.
>
> Beverly
Message #4 by "Pardee, Roy E" <roy.e.pardee@l...> on Wed, 21 Mar 2001 08:24:33 -0800
|
|
In case you haven't already, have a look at:
http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
The fact that your .mdb is located 'well off site' makes me wonder about the
reliability of your network connections--I believe Access is fairly
intolerant of even small interruptions in net connections. I seem to
remember some newsgroup posts relating stories of using the jet UserRoster
to track down a single machine with a bum NIC.
HTH,
-Roy
-----Original Message-----
From: Beverley Usher [mailto:bUsher@h...]
Sent: Wednesday, March 21, 2001 7:04 AM
To: Access
Subject: [access] RE: Access File Locking
Thanks for the suggestions. I will keep this on file. Unfortunately, my
problem at the moment is that the server where the locked files are is
well off-site and there is no one there who is at all technical, so I
can't really do much. But I think the problem is probably with the
server - we're having other problems with it. And, get this, there is NO
.ldb file for the file that has locked! Anyway, I'm sure I'll have
occasion to use your suggestions on site some time in the not too
distant future.
Beverly
>>> jsh@s... 21/03/2001 2:12:18 PM >>>
Beverly,
If an .ldb file exists for the .mdb file (the database), then the
database
believes it still has a connection to someone. The first step I take
when
I believe everyone is out is to try and delete the .ldb and compress
the
database. If that does not work, then open the .ldb with notepad. You
will
see all the computer names of systems that opened the database
previously.
The computer names will show when someone opens the database, but do
not
get removed when a person exits the database. This will give you a
group
of computers to go check out. It very well could be that someone is not
out of the database (the most common problem). If that's the case, just
close them out of the database and you are all set. If no one has any
instances of the database open, look for ghosts (An instance of Access
open in the system tray, but showing no database). End task on Access
twice to get rid of it. If this still does not fix the problem, my next
move is to reboot the systems on the .ldb list. Sometimes asking the
users
if they had errors or other problems the last time they had the
database
open will give you an idea of which to try first. The most common
problems
are those users who have errors, corrupt the database just a little,
exit
Access, but never turn off their PC at night. Reboot that PC and you
will
almost always fix the problem. In 2 1/2 years of administering Access
databases, I have yet to find a case where I had to recreate the
folders,
etc. I hope this helps.
Best of luck,
Jeff H
> Access 97 files on one of my servers are locking themselves down. All
of
> the files have been working well in a multi-user environment (and
the
> same files on three other servers are fine), but on one server, a
file
> will suddenly insist that it is in use and cannot be used by anyone
> else. This is true even early in the morning when no one is at the
site.
> Even as supervisor/owner of the files, I cannot delete them or
change
> their name, or delete the directory they are in. The only work-around
I
> have found so far is to rename the entire directory, create a new
one
> and put new copies of the files there. The directory I had to
recreate
> this morning is 700 MB so I really do not want to have to do this
much
> longer.
>
> Has anyone had a similar problem? Does anyone have any ideas of how
to
> solve this or of better work-arounds?
>
> Any and all help appreciated.
>
> Beverly
Message #5 by "Brian Paniccia" <bpanicci@n...> on Wed, 21 Mar 2001 11:40:30 -0500
|
|
Hi,
I once ran into a situation with an Access db on a network with similar
symptoms. I finally discovered a condition on the network
where the Lock Release File Reset Bit was not being reset in the file
system. There was a driver conflict within Access or Windows via the
Network file system and I remember having to write a routine in Access (this
was 97 on a Novell network) that did explicit locking and would call an
external batch file to issue a server command remotely to reset the file
lock status until a new driver came out for Windows file support on Novell.
I'm giving this scenario to you as best as I can from memory. The specifics
may be inaccurate I.E. Novell, Driver specific, but this was the general
cause/effect. It sounds like your situation may be similar and I hope this
helps. I would check
the Brand, Version , Build and driver facts from the Network file system.
The rights on the location of the Access files, The versions of all drivers
Network Interface card on up to the file system and check (with IT) the
patches and revisions available.
----- Original Message -----
From: "Beverley Usher" <bUsher@h...>
To: "Access" <access@p...>
Sent: Wednesday, March 21, 2001 10:03 AM
Subject: [access] RE: Access File Locking
> Thanks for the suggestions. I will keep this on file. Unfortunately, my
> problem at the moment is that the server where the locked files are is
> well off-site and there is no one there who is at all technical, so I
> can't really do much. But I think the problem is probably with the
> server - we're having other problems with it. And, get this, there is NO
> .ldb file for the file that has locked! Anyway, I'm sure I'll have
> occasion to use your suggestions on site some time in the not too
> distant future.
>
> Beverly
>
> >>> jsh@s... 21/03/2001 2:12:18 PM >>>
> Beverly,
>
> If an .ldb file exists for the .mdb file (the database), then the
> database
> believes it still has a connection to someone. The first step I take
> when
> I believe everyone is out is to try and delete the .ldb and compress
> the
> database. If that does not work, then open the .ldb with notepad. You
> will
> see all the computer names of systems that opened the database
> previously.
> The computer names will show when someone opens the database, but do
> not
> get removed when a person exits the database. This will give you a
> group
> of computers to go check out. It very well could be that someone is not
>
> out of the database (the most common problem). If that's the case, just
>
> close them out of the database and you are all set. If no one has any
> instances of the database open, look for ghosts (An instance of Access
>
> open in the system tray, but showing no database). End task on Access
> twice to get rid of it. If this still does not fix the problem, my next
>
> move is to reboot the systems on the .ldb list. Sometimes asking the
> users
> if they had errors or other problems the last time they had the
> database
> open will give you an idea of which to try first. The most common
> problems
> are those users who have errors, corrupt the database just a little,
> exit
> Access, but never turn off their PC at night. Reboot that PC and you
> will
> almost always fix the problem. In 2 1/2 years of administering Access
> databases, I have yet to find a case where I had to recreate the
> folders,
> etc. I hope this helps.
>
> Best of luck,
>
> Jeff H
>
>
> > Access 97 files on one of my servers are locking themselves down. All
> of
> > the files have been working well in a multi-user environment (and
> the
> > same files on three other servers are fine), but on one server, a
> file
> > will suddenly insist that it is in use and cannot be used by anyone
> > else. This is true even early in the morning when no one is at the
> site.
> > Even as supervisor/owner of the files, I cannot delete them or
> change
> > their name, or delete the directory they are in. The only work-around
> I
> > have found so far is to rename the entire directory, create a new
> one
> > and put new copies of the files there. The directory I had to
> recreate
> > this morning is 700 MB so I really do not want to have to do this
> much
> > longer.
> >
> > Has anyone had a similar problem? Does anyone have any ideas of how
> to
> > solve this or of better work-arounds?
> >
> > Any and all help appreciated.
> >
> > Beverly
Message #6 by "Beverley Usher" <bUsher@h...> on Thu, 22 Mar 2001 08:11:04 +0000
|
|
Thanks. I'll go over this with our Novell experts.
B.
>>> bpanicci@n... 21/03/2001 4:40:30 PM >>>
Hi,
I once ran into a situation with an Access db on a network with
similar
symptoms. I finally discovered a condition on the network
where the Lock Release File Reset Bit was not being reset in the file
system. There was a driver conflict within Access or Windows via the
Network file system and I remember having to write a routine in Access
(this
was 97 on a Novell network) that did explicit locking and would call
an
external batch file to issue a server command remotely to reset the
file
lock status until a new driver came out for Windows file support on
Novell.
I'm giving this scenario to you as best as I can from memory. The
specifics
may be inaccurate I.E. Novell, Driver specific, but this was the
general
cause/effect. It sounds like your situation may be similar and I hope
this
helps. I would check
the Brand, Version , Build and driver facts from the Network file
system.
The rights on the location of the Access files, The versions of all
drivers
Network Interface card on up to the file system and check (with IT)
the
patches and revisions available.
----- Original Message -----
From: "Beverley Usher" <bUsher@h...>
To: "Access" <access@p...>
Sent: Wednesday, March 21, 2001 10:03 AM
Subject: [access] RE: Access File Locking
> Thanks for the suggestions. I will keep this on file. Unfortunately,
my
> problem at the moment is that the server where the locked files are
is
> well off-site and there is no one there who is at all technical, so
I
> can't really do much. But I think the problem is probably with the
> server - we're having other problems with it. And, get this, there is
NO
> .ldb file for the file that has locked! Anyway, I'm sure I'll have
> occasion to use your suggestions on site some time in the not too
> distant future.
>
> Beverly
>
> >>> jsh@s... 21/03/2001 2:12:18 PM >>>
> Beverly,
>
> If an .ldb file exists for the .mdb file (the database), then the
> database
> believes it still has a connection to someone. The first step I take
> when
> I believe everyone is out is to try and delete the .ldb and compress
> the
> database. If that does not work, then open the .ldb with notepad.
You
> will
> see all the computer names of systems that opened the database
> previously.
> The computer names will show when someone opens the database, but do
> not
> get removed when a person exits the database. This will give you a
> group
> of computers to go check out. It very well could be that someone is
not
>
> out of the database (the most common problem). If that's the case,
just
>
> close them out of the database and you are all set. If no one has
any
> instances of the database open, look for ghosts (An instance of
Access
>
> open in the system tray, but showing no database). End task on
Access
> twice to get rid of it. If this still does not fix the problem, my
next
>
> move is to reboot the systems on the .ldb list. Sometimes asking the
> users
> if they had errors or other problems the last time they had the
> database
> open will give you an idea of which to try first. The most common
> problems
> are those users who have errors, corrupt the database just a little,
> exit
> Access, but never turn off their PC at night. Reboot that PC and you
> will
> almost always fix the problem. In 2 1/2 years of administering
Access
> databases, I have yet to find a case where I had to recreate the
> folders,
> etc. I hope this helps.
>
> Best of luck,
>
> Jeff H
>
>
> > Access 97 files on one of my servers are locking themselves down.
All
> of
> > the files have been working well in a multi-user environment (and
> the
> > same files on three other servers are fine), but on one server, a
> file
> > will suddenly insist that it is in use and cannot be used by
anyone
> > else. This is true even early in the morning when no one is at the
> site.
> > Even as supervisor/owner of the files, I cannot delete them or
> change
> > their name, or delete the directory they are in. The only
work-around
> I
> > have found so far is to rename the entire directory, create a new
> one
> > and put new copies of the files there. The directory I had to
> recreate
> > this morning is 700 MB so I really do not want to have to do this
> much
> > longer.
> >
> > Has anyone had a similar problem? Does anyone have any ideas of
how
> to
> > solve this or of better work-arounds?
> >
> > Any and all help appreciated.
> >
> > Beverly
Message #7 by "Beverley Usher" <bUsher@h...> on Thu, 22 Mar 2001 08:08:19 +0000
|
|
That would explain a lot as that site is having lots of problems with
network connections.
Thanks!
>>> roy.e.pardee@l... 21/03/2001 4:24:33 PM >>>
In case you haven't already, have a look at:
http://support.microsoft.com/support/kb/articles/Q209/1/37.ASP
The fact that your .mdb is located 'well off site' makes me wonder
about the
reliability of your network connections--I believe Access is fairly
intolerant of even small interruptions in net connections. I seem to
remember some newsgroup posts relating stories of using the jet
UserRoster
to track down a single machine with a bum NIC.
HTH,
-Roy
-----Original Message-----
From: Beverley Usher [mailto:bUsher@h...]
Sent: Wednesday, March 21, 2001 7:04 AM
To: Access
Subject: [access] RE: Access File Locking
Thanks for the suggestions. I will keep this on file. Unfortunately,
my
problem at the moment is that the server where the locked files are is
well off-site and there is no one there who is at all technical, so I
can't really do much. But I think the problem is probably with the
server - we're having other problems with it. And, get this, there is
NO
.ldb file for the file that has locked! Anyway, I'm sure I'll have
occasion to use your suggestions on site some time in the not too
distant future.
Beverly
>>> jsh@s... 21/03/2001 2:12:18 PM >>>
Beverly,
If an .ldb file exists for the .mdb file (the database), then the
database
believes it still has a connection to someone. The first step I take
when
I believe everyone is out is to try and delete the .ldb and compress
the
database. If that does not work, then open the .ldb with notepad. You
will
see all the computer names of systems that opened the database
previously.
The computer names will show when someone opens the database, but do
not
get removed when a person exits the database. This will give you a
group
of computers to go check out. It very well could be that someone is
not
out of the database (the most common problem). If that's the case,
just
close them out of the database and you are all set. If no one has any
instances of the database open, look for ghosts (An instance of Access
open in the system tray, but showing no database). End task on Access
twice to get rid of it. If this still does not fix the problem, my
next
move is to reboot the systems on the .ldb list. Sometimes asking the
users
if they had errors or other problems the last time they had the
database
open will give you an idea of which to try first. The most common
problems
are those users who have errors, corrupt the database just a little,
exit
Access, but never turn off their PC at night. Reboot that PC and you
will
almost always fix the problem. In 2 1/2 years of administering Access
databases, I have yet to find a case where I had to recreate the
folders,
etc. I hope this helps.
Best of luck,
Jeff H
> Access 97 files on one of my servers are locking themselves down.
All
of
> the files have been working well in a multi-user environment (and
the
> same files on three other servers are fine), but on one server, a
file
> will suddenly insist that it is in use and cannot be used by anyone
> else. This is true even early in the morning when no one is at the
site.
> Even as supervisor/owner of the files, I cannot delete them or
change
> their name, or delete the directory they are in. The only
work-around
I
> have found so far is to rename the entire directory, create a new
one
> and put new copies of the files there. The directory I had to
recreate
> this morning is 700 MB so I really do not want to have to do this
much
> longer.
>
> Has anyone had a similar problem? Does anyone have any ideas of how
to
> solve this or of better work-arounds?
>
> Any and all help appreciated.
>
> Beverly
|
|
|
View Cart
