Sharing Violations

Anonymous
2019-10-18T22:33:01+00:00

Since installing Catalina 10.15 and Office 365 16.30 (updates installed the same day (something I will not due again)) when I attempt to save a workbook that I have used for a couple of years, I receive the alert: 'Your changes could not be saved  to xxx.xlsx due to a sharing violation.  I then receive the alert The file format end extension of 646820000.mactf don't match. 

I contacted the Answer Desk who say it is an Apple Product and Apple support said it is a Microsoft problem.

Any thoughts or suggestions will be appreciated.

Microsoft 365 and Office | Excel | For home | Windows

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

92 answers

Sort by: Oldest
  1. Anonymous
    2020-02-28T17:33:23+00:00

    16.34 is still not working for me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-03-04T20:43:15+00:00

    We've just started seeing this issue as well.

    Some specifics on trying to duplicate:

    Excel 16.34 for OSX

    OSX 10.14.6

    Storage:

    Dell Fluid FS (its basically a nas file system running linux) the one thing that might be related is OSX was ignoring some file/folder inheritance when the share level permissions were set to full control.  The work around this Authenticated Users are set to "Write" rather then "Full Control"  This is specific to the share level permissions, not NTFS permissions.  This setting kept OSX from directly adding user permissions to files.  It may have nothing to do with this, but its what comes to mind.

    I'm working to try and test if the share level permissions are related.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-03-04T21:50:53+00:00

    This is a known bug that Microsoft is working on.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-03-05T12:51:54+00:00

    This is a known bug that Microsoft is working on.

    I didn't follow the entire thread, but it looked like MS was having some trouble duplicating the issue so I was just adding what info we had to contribute.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-03-16T01:15:50+00:00

    Installed the latest update, 16.35, a few days ago and have NOT seen the error since. Thank you for finally fixing this!

    -Ray

    Was this answer helpful?

    0 comments No comments