Microsoft Excel needs to recover XLSX before opening

Hi,

Excel pops up a message whether I want to repair the file, because it has found some issues with it. After recovery it says:

Repaired Records: Cell information from /xl/worksheets/sheet1.xml part

Recovery log:

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<logFileName>error212120_01.xml</logFileName>
<summary>Errors were detected in file 'C:\0\test.xlsx'</summary>
<repairedRecords summary="Following is a list of repairs:">
<repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet1.xml part</repairedRecord>
</repairedRecords>
</recoveryLog>

Please advise.

Thanks, Andor

[jayflo]

For me, it looks like the worksheet names are the issue: http://stackoverflow.com/questions/11706393/excel-found-unreadable-content-in-xslx

I need to use shorter names.

[rob2d]

Just to update in case it helps anyone else, I finally found the source of my problem. I had some data generated in cells which exceeded the length allowed (32,767 characters). There’s other constraints on things like row height/cell length/etc which when violated work in non Microsoft products (e.g. Google Docs) but bring up a Microsoft recovery message. You can find that info here: https://support.office.com/en-us/article/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3

I think it would be a great idea to detect these issues in excelJS and pass a warning. This way, we won’t need to troubleshoot blindly and drive ourselves crazy (and usually an excel UI would apply these constraints to the inputs themselves).

Any thoughts on it? I am considering putting in a PR as library this seems to be the best hope at isomorphic excel solutions currently.