Temporary folder when saving on a network share not removed

Anonymous
2018-06-15T11:13:40+00:00

We experience a lot of problems in working with Macs (macOS High Sierra) on network shares (Windows server 2016 core).

When working and saving excel files on the share temporary folders will be created which are very often not removed. File locks will not be removed and opening the files is often then read only possible.

Microsoft 365 and Office | Excel | For business | MacOS

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2018-06-16T09:59:36+00:00

    Hi Andreas,

    There are several reasons that cause the file is locked, you could refer to this: "The document is locked for editing by another user" error message when you try to open a document in Word.

    1, Word previously quit improperly and, therefore, did not delete the owner file.

    2, A second instance of Word is running in the background with the document already open.

    3, The document is shared over a network, and another user has it open.

    To make this better: delete the temporary folders or files here are few ways to do that:

    1, quite the client completely when you close Office. 

    2, manually delete the temporary files and folders:

        In Terminal, paste the following: defaults write com.apple.finder AppleShowAllFiles YES

        Press return

        Hold ‘alt’ on your keyboard, then right click on the Finder icon in the dock and click Relaunch.

        In finder, go to the folder where the problem doc exists.

        Delete: .~lock.(Doc Name).ods#(or ~lock.xxx.ods# )

    Regards,

    Alex

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-06-19T08:43:18+00:00

    Hi Andreas

    haven't heard from since your first post, is there anything I can do to help?

    Regards,

    Alex

    0 comments No comments