MS Access Multiuser - Corruption problem

Author

Corruption problem

Bill

2005-08-12, 3:24 am

Hi all.
I have a multiuser database distributed over a windows p2p network. This has
worked fine for 3 years. But my problem is this.......Every once in a while
the backend corrupts and needs to be repaired. This is not a problem in
itself but the lock file always stays in a state that says users are still
in the system and the lock file cannot be deleted until I reset the server
where the file resides.( I have another table in another database, which
when a boolean field is checked (yes) then the frontend(s) will close after
alerting the user that a problem exists). So the users are kicked out of the
system yet the lock file stays in the same state as when the backend
corrupted.
So my problem is my inability to delete this file so that I can compact and
repair the database.
Is this by design? Is there a way around my problem of having to reboot the
server to free the lock files state and delete it?
Please help. As I wrote code that closes everyone out, deletes the file and
compacts the backend, then allows users access again. But it will not work
because of my inability to delete the lock file unless I reboot the server
where the backend resides.

Help, help, help

Alex Dybenko

2005-08-12, 3:24 am

Hi,
if you mdb is locked - then it is opened by somebody (btw - could be
antivirus for example). you can try to discover this using this info:
http://www.mvps.org/access/general/gen0034.htm

--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

"Bill" < taylor9780@bellsouth
.net> wrote in message
news:4qUKe.3210$XM3.2577@bignews5.bellsouth.net...
> Hi all.
> I have a multiuser database distributed over a windows p2p network. This
> has
> worked fine for 3 years. But my problem is this.......Every once in a
> while
> the backend corrupts and needs to be repaired. This is not a problem in
> itself but the lock file always stays in a state that says users are still
> in the system and the lock file cannot be deleted until I reset the server
> where the file resides.( I have another table in another database, which
> when a boolean field is checked (yes) then the frontend(s) will close
> after
> alerting the user that a problem exists). So the users are kicked out of
> the
> system yet the lock file stays in the same state as when the backend
> corrupted.
> So my problem is my inability to delete this file so that I can compact
> and
> repair the database.
> Is this by design? Is there a way around my problem of having to reboot
> the
> server to free the lock files state and delete it?
> Please help. As I wrote code that closes everyone out, deletes the file
> and
> compacts the backend, then allows users access again. But it will not work
> because of my inability to delete the lock file unless I reboot the server
> where the backend resides.
>
> Help, help, help
>
>

Bill Taylor

2005-08-12, 9:30 am

Alex,
I have opened the ldb file and manually closed the front end connections to
close out all users. Sometimes the users that are shown in the lock file are
not in the database at all. So my problem is not that users have the
database open. As stated earlier...... All people are closed out, and the
lock file remains. My mdb is locked and yet nobody has it open. In fact,
nobody can have it open because it is corrupt and will not allow access.
Help, help, help
"Alex Dybenko" <alexdyb@PLEASE.cemi.NO.rssi.SPAM.ru> wrote in message
news:##wkuuwnFHA.576@TK2MSFTNGP15.phx.gbl...
> Hi,
> if you mdb is locked - then it is opened by somebody (btw - could be
> antivirus for example). you can try to discover this using this info:
> http://www.mvps.org/access/general/gen0034.htm
>
> --
> Alex Dybenko (MVP)
> http://Alex.Dybenko.com
> http://www.PointLtd.com
>
>
> "Bill" < taylor9780@bellsouth
.net> wrote in message
> news:4qUKe.3210$XM3.2577@bignews5.bellsouth.net...
still[color=darkred]

server[color=darkred
]
work[color=darkred]
server[color=darkred
]
>
>

Alex Dybenko

2005-08-13, 7:24 am

i think you can get a filemonitor at www.sysinternals.com, and then check if
file really accessed by any process.
Also you can try to find out which PC cause corruption, by taking out
one-by-one

--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

"Bill Taylor" < wtaylor51537@earthli
nk.net> wrote in message
news:u6hfWmznFHA.2180@TK2MSFTNGP15.phx.gbl...
> Alex,
> I have opened the ldb file and manually closed the front end connections
> to
> close out all users. Sometimes the users that are shown in the lock file
> are
> not in the database at all. So my problem is not that users have the
> database open. As stated earlier...... All people are closed out, and the
> lock file remains. My mdb is locked and yet nobody has it open. In fact,
> nobody can have it open because it is corrupt and will not allow access.
> Help, help, help
> "Alex Dybenko" <alexdyb@PLEASE.cemi.NO.rssi.SPAM.ru> wrote in message
> news:##wkuuwnFHA.576@TK2MSFTNGP15.phx.gbl...
> still
> server
> work
> server
>
>

Sponsored Links