OES 2018 sp3 Cifs, user B tries to open Excel sheet, but app report that file will be opened read only since it's currently open by user C, but it's user A that got the file open

Hi,

A customer with 2 server network (no cluster) with one DSFW server for auth and one oes server with cifs services for file sharing.

They report issues with file sharing conflicts, user B tries to open file, but Excel reports that it can only be open read only since it's already opened by  user C. In reality it's users A that has opened the file and users C isn't logged in since he has left the company and account is disabled.

But where does Excel get the information? I supposing from OES Cifs, but if I check opened files there is no files opened by user C.

User A got the specific file open, so that is fine.

I will migrate to oes 23.4 or 24.1 as soon as possible, but what I'm reading in forums doesn't make me to pumped to do without proper time to role back if needed.

Any suggestions?

/Lennart

  • Verified Answer

    +1

    Hi Lennart,

    We see this often in our environment. when Excel opens a file, a temp file (~somewhat) is createted and deleted, when the file is closed. If Excel crashes, or the connection is broken, the tmp file is orphaned and never be deleted automaticly anymore. If the file is opened by the user A and user B tries to open the file, Excel reads the owner of the tmp file (user C) and reports that this user has the file open. Simply delete the tmp file while the sheet is not opened and the next time the tmp file is created with the correct file owner.

    Arndt

  • 0 in reply to 

    Hello Arndt,

    That worked out fine, thanks for your help

    /Lennart

  • 0   in reply to 

    ah yes,  where one needs to occasionally run a "del *.tmp /s" and/or "del ~*.* /s" from the drive in question to catch all of those orphaned files.  To the point I have a cleanup.bat in my search path.

    REM  cleanup.bat   
    REM  to clean up those temp files that still get littered by applications 
    REM    when they don't properly cleanup after themselves
    REM  Created by Andy Konecny some time last century and still used regularly
    del *.tmp /s
    del *.temp /s
    del ~*.* /s
    del *.bak /s
    del thumbs.db /s

    It doesn't touch the files that are in actual use, and though it misses the hidden ones, it brings the issue down to a dull roar.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    you can use 

    find /media/nss/ -type f -name '~$*.*' -delete

    on the server console, if you wan't you can script it and run periodicly via cron