Issues Saving Files; Excel 2013 RRS feed

  • Question

  • Users are unable to save files using Excel 2013 (both .xls and .xlsx) to network share space. the return is "Someone else is working on 'J:\network space name\filename' right now. Please try again later". There are no other users currently using the file in question and Folder and file ACL allows for full control. Users are able to save to their persistent D:\ volume (we are using VMware) but unable to breach the network space. I have full administrative rights and am experiencing the same results, this includes a newly created file, files for which I have total ownership and files for which i have full control over. This condition is only true for Excel 2013, Office and other Suite applications are functioning well within tolerance.

    This condition originally manifested when we first rolled out the MSFT Office 2013 image but subsided when we modified Trend Micro so that it would not scan edited files. After that it would only manifest occasionally and to single or a couple of users but has now returned to being global. Any ideas as to how to remedy this would be greatly appreciated.

    Thursday, March 19, 2015 7:57 PM


All replies

  • Please read this blog post. It describes possible solutions.
    • Edited by Gil RavivMVP Friday, March 20, 2015 6:37 AM
    • Proposed as answer by Gil RavivMVP Friday, March 20, 2015 6:37 AM
    • Marked as answer by George123345 Friday, April 3, 2015 1:46 AM
    Friday, March 20, 2015 6:36 AM
  • The blog post speaks to an error message that is not what my users are seeing. There is no reference to files being 'locked', rather it suggests that another user may be viewing the same file precluding a save action. Initially we believed it was related to an issue caused by .TMP files but as it turned out a refresh of AV baseline policy relieved the condition. So it may have been a cache issue and how the AV was handling the temporary file but details behind causality could not be determined beyond refreshing the base policy.

    Thank you for your suggestion though, I appreciate the consideration.

    Friday, April 3, 2015 2:21 AM