G
Geo
Greetings.
We have a puzzling problem with randomly generating .ldb files on a
network share that users have read/write access to and locking the
databases. The puzzling part is that users, who would not even know
where the database is located, will show up as having an open session
to the ldb file in computer managment (MMC computer mgmt, shared
folders, open files). I can see the ldb is open by %username%.... but
not the mdb. At times it has even shown that I had the ldb session
open when I know that I didn't connect to the mdb. I have to end the
session from the MMC to delete the ldb and restore access to the DB's.
We had the share in a SAN enviroment that was having other issues so
the folder structure was moved to a standalone server (a member server
that only has print functions) to try to isolate the problem from the
SAN. However, the problem persists, the ldb's keep coming back. Has
anyone seen this and how do we fix it?
Thanks.
We have a puzzling problem with randomly generating .ldb files on a
network share that users have read/write access to and locking the
databases. The puzzling part is that users, who would not even know
where the database is located, will show up as having an open session
to the ldb file in computer managment (MMC computer mgmt, shared
folders, open files). I can see the ldb is open by %username%.... but
not the mdb. At times it has even shown that I had the ldb session
open when I know that I didn't connect to the mdb. I have to end the
session from the MMC to delete the ldb and restore access to the DB's.
We had the share in a SAN enviroment that was having other issues so
the folder structure was moved to a standalone server (a member server
that only has print functions) to try to isolate the problem from the
SAN. However, the problem persists, the ldb's keep coming back. Has
anyone seen this and how do we fix it?
Thanks.