cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only


w

I support Excel 2010 users on Windows 7 who share data via xls files and VBA.  They sometimes get the message:

xxx.xls cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only

Once this happens, the session must be closed as Excel 2010 will not open any file in the whole directory.  Even if they try using the GUI, they get the same error opening an xls that they could open earlier.  Furthermore, they get a protected view error when they try to open a xlsm file.  If they start a new Excel session, they can open all files again until it happens again which can be days later.

In the event log, I see

<Data>100101</Data>

<Data>14.0.7015.1000</Data>

<Data>xqgg</Data>

I cannot reproduce this error and would appreciate ideas on its cause.

June 8th, 2015 4:00pm

Hi,

Based on your description, could you tell me if this issue only appeared in a particular file? For example: a *.xls file?  And if this issue appeared in all users computers?

First I suggest you check if you enable Offline files in Windows 7, try to disable Offline files.

Then check registry entries:

HKey_Classes_Root\Excel.Sheet.12\shell\edit\ddeexec

It should be:

[open("%1",,,,,,,,,,,,,,,,,0)]

and

HKey_Classes_Root\Excel.Sheet.12\shell\edit\command

It should be

"C:\Program Files\Microsoft Office\Office14\Excel.exe" /dde

Please read this blog and check if these methods work for you.

http://negyuhsit.blogspot.com/2013/10/microsoft-excel-compatibility-cannot-be.html

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Hope its helpful.

Regards,

George Zhao
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 3:06am

The PCs with Offline files disabled seem to work better, but we still have a problem that only appears once in a while.

One detail is that after Excel throws the

"file cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only

message, the Excel session will give the same message for older xls file it opened earlier and even for txt files.

While we can't recover from this error in production, I have been able to "correct" Excel by deleting and copying files in the same folder using the command line.  I do not know the exact sequence because it not easy to reproduce.

I have turned on the Protected View logging but I see little in the log file.  I see;

Trust Center Decision: Enable Content

but I do not see when something is not trusted.

Also, I am searching the Event Log for other traces of this problem.  Do you have any suggestions?



June 17th, 2015 9:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics