P
Pierre
We are currently experiencing a issue that that some of
our users (some of which are laptop users that use the
offline files feature) try to open for example an Excel
file and it will be reported as being currently in use by
a named user. So far no problem. However this user does
not have the file open and if we go to check the open
files on the server the file will in fact be open by a
different user to the one reported in the excel popup
window.
Is there a way I can ensure that at least the correct user
is reported to having the file open? I'm sure this must be
somewhere int he Microsoft Knowledgebas but can I find it!
I suspect there is an element of people opening files
while online and then disconnecting from the network
without closing the files first. Then somehow the write
lock times out gets released on the server but the user
information does not.
Has anyone experienced this issue or have a resolution to
it? Our server that this occurs on is Windows 2000 Server
Service pack 4. The user machines are all Windows 2000 Pro
Service pack 4.
Many thanks,
Pierre
our users (some of which are laptop users that use the
offline files feature) try to open for example an Excel
file and it will be reported as being currently in use by
a named user. So far no problem. However this user does
not have the file open and if we go to check the open
files on the server the file will in fact be open by a
different user to the one reported in the excel popup
window.
Is there a way I can ensure that at least the correct user
is reported to having the file open? I'm sure this must be
somewhere int he Microsoft Knowledgebas but can I find it!
I suspect there is an element of people opening files
while online and then disconnecting from the network
without closing the files first. Then somehow the write
lock times out gets released on the server but the user
information does not.
Has anyone experienced this issue or have a resolution to
it? Our server that this occurs on is Windows 2000 Server
Service pack 4. The user machines are all Windows 2000 Pro
Service pack 4.
Many thanks,
Pierre