Bug 113392 - LO Created XLSX Spreadsheet opened in Excel has unreadable content
Summary: LO Created XLSX Spreadsheet opened in Excel has unreadable content
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.2.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-24 01:54 UTC by miltonh26
Modified: 2018-05-30 16:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Errant LO created XLSX file (36.10 KB, application/wps-office.xlsx)
2017-10-24 01:54 UTC, miltonh26
Details
Screenshot of Excel repair dialog (15.38 KB, image/png)
2017-10-24 02:10 UTC, miltonh26
Details

Note You need to log in before you can comment on or make changes to this bug.
Description miltonh26 2017-10-24 01:54:00 UTC
Created attachment 137245 [details]
Errant LO created XLSX file

XLSX file created in LO Linux, then opened in Excel 2010 and Excel 2013, Excel reports "Excel found unreadable content". Happens especially when the XLSX file contains a pivot table created by LO. This issue is intermittent and been in LO Calc for a long time (at least a couple years).  

How to recreate:
1. Open attached file in Excel 2010 or Excel 2013. 

Version of Excel I used is "Version: 14.0.4760.1000 (32 bit)"

Answering "Yes" to Excel's dialog to recover the file works and the errant spreadsheet can be recovered. Saving the recovered file in Excel and then reopening in LO also works and interchangeability is restored.

XLS does not have this issue.
Comment 1 miltonh26 2017-10-24 02:10:09 UTC
Created attachment 137246 [details]
Screenshot of Excel repair dialog

-- Content of XML file referenced

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
-<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<logFileName>error042200_03.xml</logFileName>
<summary>Errors were detected in file 'E:\home\milton\Documents\LO Pivot Bug 5.4.2_20171024 - load error Excel.xlsx'</summary>
-<repairedRecords summary="Following is a list of repairs:">
<repairedRecord>Repaired Records: PivotTable report from /xl/pivotCache/pivotCacheDefinition1.xml part (PivotTable cache)</repairedRecord>
</repairedRecords>

</recoveryLog>
Comment 2 miltonh26 2017-10-24 02:16:14 UTC
Saving the file in Excel after repairing it, then reopening in LO, LO recognizes the pivot table. When the file is reopened in Excel yet again the error has disappeared and interoperability of file has been restored between LO and Excel.
Comment 3 raal 2017-10-24 04:38:39 UTC
Tested with excel2010 and Version: 6.0.0.0.alpha1+
Build ID: d76c4e5c9aaf8bd27ec97679bcaeba5b18aca493
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;

steps:
open your file
change data , refresh pivot table, save
open in excel -> no warning

Please, could you test with newer version? Setting bug as needinfo, set as unconfirmed again if problem still occurs in newer version. Thank you.

http://dev-builds.libreoffice.org/daily/master/
Comment 4 QA Administrators 2018-05-02 15:47:54 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2018-05-30 16:49:13 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180530