looks like it changed. i tried yestarday cmd with --verbose option its telling us the user who locked it cool ...thanks all
isi_for_array isi smb openfiles list --verbose
Contact support and ask about "patch-101597". Issue is solved in 18.104.22.168 but for any below you can use this patch.
This patch addresses the issue where one user closes an Excel file and a
different user will not be able to open the file because the file is still
opened by the first user. This problem persists after the Microsoft KB 942146
has been appiled to the client. http://support.microsoft.com/kb/942146
(Windows XP KB 812937 http://support.microsoft.com/kb/942146)
* Race condition where a file close and an oplock break response was causing
the software to sometimes miss closing a file. This seems to happen
mostly with Excel file closes.
(MD5 = 9db346b3eab63f66cb8640c79db6d9c5)
thank you for the very useful info and thats what i am looking for . i heard 22.214.171.124 is coming this week end or next week is that true ?? if so i go for it rather doing 2 upgrades.
I have combined a few of the previously mentioned into one that works well for me.
isi_for_array isi smb openfiles list --verbose | grep -A3 "%filename%"
I am constantly unlocking locked files due to an error we are unable to narrow down. I prefer the following:
isi_for_array "isi smb openfiles list --verbose" |grep -B3 -A3 (Username)
If Users are behind a firewall, check the keepalive / keepidle times of the tcp settings on client / firewall and cluster. Sometimes a firewall closes the tcp-session without correctly informing client and server.