Cannot access files on Time Machine after Mavericks update

PAMurillo
PAMurillo used Ask the Experts™
on
Hi Everyone,
I have a small Mac network with 3 Macs.  The all connect to an AirPort Time Capsule on which I have setup a single shared folder and granted Read/Write permission to all 3 users.  I updated the  newest Mac to 10.9.5.  Although, it can still access the folder it cannot open the Office documents (see attachments) error 2error 1.  Strangely, it has no problems opening the PDF files in the same folder.

I have tried to:
-Save a test document to the folder without success
-Renaming the files (many of them are named #1 donors list 2014, #2 donors list 2014, etc).
-Checking for MS Office 2011 updates (none)

Any assistance would be appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Try using file names without any punctuation, just letters and numbers, and see if that makes a difference. In particular, make sure there are no colons, slashes or backslashes in the filename.

Author

Commented:
I tried that  but no luck.  Both renaming existing files and creating new ones (wasn't permitted to save new files to the folder)
Do you have antivirus software on the Mac in question? If so, try disabling it.
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Hi Strung,
No AV software installed.

Here's the answer:
Apparently it is just one file that is inaccessible that is saved in a shared folder in Time Machine.  Its a word file appx 21GB (multiple hi-res pictures were inserted in it).  When trying to open it on any of the Macs on the network, the same error is generated.

Now I can't delete it, but we can just let it be.
The maximum file size for a Word document in Windows is 512MB. I haven't been able to find the maximum file size for the Mac version, but it may well be the same.

If you had mentioned at the start that it was only one file that was causing the problem, you would have got entirely different responses to your question.

Author

Commented:
Hi strug,
Thanks for your input. Today, I had 2 of the 3 employees on-site.  I was then able to trace the process leading up to the issue based on their timeline based on asking them both what they were doing on the shared folder.  Originally, I thought the issue was caused by the Mavericks upgrade but it was merely coincidental.

Author

Commented:
It was the correct answer

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial