[GH-ISSUE #268] Error opening file with Excel #211

New issue

Closed

opened 2026-05-05 11:56:17 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 11:56:17 -06:00

Owner

Originally created by @duncangroenewald on GitHub (Jan 17, 2020).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/268

Originally assigned to: @jmcnamara on GitHub.

I am getting an error on one generated file when opening with Excel. See the following error log output. I can upload a copy of the generated file is required. The file seems to open fine but it's a bit annoying getting this message.

Repair Result to XXXX Extract 2020-01-17_2307480.xml

Errors were detected in file ’/Users/Shared/XXXX/Reports/Stock/XXXX Extract 2020-01-17_230748.xlsx’

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

Originally created by @duncangroenewald on GitHub (Jan 17, 2020). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/268 Originally assigned to: @jmcnamara on GitHub. I am getting an error on one generated file when opening with Excel. See the following error log output. I can upload a copy of the generated file is required. The file seems to open fine but it's a bit annoying getting this message. <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>Repair Result to XXXX Extract 2020-01-17_2307480.xml</logFileName><summary>Errors were detected in file ’/Users/Shared/XXXX/Reports/Stock/XXXX Extract 2020-01-17_230748.xlsx’</summary><repairedRecords summary="Following is a list of repairs:"><repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet1.xml part</repairedRecord></repairedRecords></recoveryLog>

gitea-mirror

2026-05-05 11:56:17 -06:00

closed this issue
added the
awaiting user feedback
label

gitea-mirror commented

2026-05-05 11:56:27 -06:00

Author

Owner

@jmcnamara commented on GitHub (Jan 17, 2020):

I can upload a copy of the generated file is required.

Yes, if you can. If it contains confidential information you can email it to me instead.

A small program that reproduces the issue would be better. Or if you can debug it then strip your program down until the error goes away.

It isn't a very common issue but things that can cause it are:

Non-UTF8 data in the strings
Overlapping merged ranges.

@jmcnamara commented on GitHub (Jan 17, 2020): > I can upload a copy of the generated file is required. Yes, if you can. If it contains confidential information you can email it to me instead. A small program that reproduces the issue would be better. Or if you can debug it then strip your program down until the error goes away. It isn't a very common issue but things that can cause it are: - Non-UTF8 data in the strings - Overlapping merged ranges.

gitea-mirror commented

2026-05-05 11:56:31 -06:00

Author

Owner

@duncangroenewald commented on GitHub (Jan 18, 2020):

Thanks, it was being caused by Swift Double values that were NaN. I would think it should handle that - i.e. convert to something Excel understands. As it is I fixed it by adding a check for Nan and don't write out the value.

@duncangroenewald commented on GitHub (Jan 18, 2020): Thanks, it was being caused by Swift Double values that were NaN. I would think it should handle that - i.e. convert to something Excel understands. As it is I fixed it by adding a check for Nan and don't write out the value.

gitea-mirror commented

2026-05-05 11:56:37 -06:00

Author

Owner

@jmcnamara commented on GitHub (Jan 18, 2020):

I would think it should handle that - i.e. convert to something Excel understands.

It is hard to detect NaN portably in C. Also Excel doesn't have a representation for NaN (outside of a formula result).

As it is I fixed it by adding a check for Nan and don't write out the value.

I think that is the best approach for now.

@jmcnamara commented on GitHub (Jan 18, 2020): > I would think it should handle that - i.e. convert to something Excel understands. It is hard to detect NaN portably in C. Also Excel doesn't have a representation for NaN (outside of a formula result). > As it is I fixed it by adding a check for Nan and don't write out the value. I think that is the best approach for now.