Microsoft Excel cannot access the file

  • 1
  • Problem
  • Updated 9 months ago
  • (Edited)
We have seen this a couple times.  I have ignored it but I now need to know what is causing it. 
  • This Excel document was being used by one person
  • The person uses Sync to open the file
  • This error occurred during an attempt to save this morning
  • There are no revisions in the web app since yesterday at 3:42pm
  • The file name has been removed from the image below
  • This has happened as well to Word Docs
What is causing this?

Photo of Rich Tincher

Rich Tincher

  • 17 Posts
  • 1 Reply Like

Posted 9 months ago

  • 1
Photo of Leo

Leo, Official Rep

  • 404 Posts
  • 37 Reply Likes
Hi Rich,

Given the length of the message, I'm suspecting filepath limit.  Excel has had a significantly shorter filepath limit (218) to allow for some Excel functionality, and I don't think this has changed.  Word can trigger it too, but it's at the standard length, so it should be rarer.
https://support.microsoft.com/en-us/help/325573/you-receive-error-messages-when-you-try-to-open-an-o...
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_other-mso_o365b/excel-218-char...

-Leo
Photo of Rakesh Kumar

Rakesh Kumar, Employee

  • 21 Posts
  • 4 Reply Likes
@Rich from the path mentioned in the error dialog, it seems you are using DriveMapper tool and not Sync. Is that right?
if so, we have a ticket for the error you are experiencing and is currently being investigated. 
Photo of Rich Tincher

Rich Tincher

  • 17 Posts
  • 1 Reply Like
Leo,  The file path   "ShareFile\Shared Folders\....xlsx" is 166 characters long.  After initial issue of saving, we saved the document with a different filename.  We then opened the ORIGINAL document, edited and saved with no issue.  I do not think it is filename length on this one.

Rakesh,  The original report from the employee is that it was opened in Sync.  However, I agree, the path indicates it was pulled from the DriveMapper S Drive.  Thanks for that info and correction.
Photo of Leo

Leo, Official Rep

  • 404 Posts
  • 37 Reply Likes
Thanks for the additional information Rich.  The error message you posted is the same window that comes up for the long filepath issue, which is why that was my first thought.  With the clarification, I agree that it is likely the Drive Mapper issue Rakesh brought up.