As reported on Ask.LO: ----- asked 2012-06-09 02:54:33 +0200 updated 2012-06-09 02:58:18 +0200 Whenever I save LibreOffice documents as .doc, .xls, .docx, .xlsx (these are the only ones I've tried), Microsoft Office 2007/2010 can't open them. They are seen as corrupted document files and I'm asked by MS Office to use its open-and-repair function, which fails nonetheless. In fact, MS Office is able to repair and open .odt and .ods documents, unlike its aforementioned seemingly native formats. If I may, what's the point of being able to "Save as..." if the respective formats can't be read by their native suites (i.e., MS Word, MS Excel etc.)? I'm currently using the latest LibreOffice (v 3.5.3.2) in Ubuntu 12.04 LTS. I've tried this on multiple Ubuntu (11.10/12.04) and Windows (7) computers. Thanks for the help, in advance. ----- Hoping that someone has this particular version of LO *and* a Windows7 machine for testing :-)
Here's the URL for the question: http://ask.libreoffice.org/question/3198/libreoffice-created-doc-xls-docx-xlsx-wont-open/
Hi Qubit. This is annoying indeed. Might it be possible to attach such a corrupt file to see what has been going wrong? Ideally as simple as possible. Without a test file, it might be impossible to guess what's going wrong here.
(In reply to comment #2) > Might it be possible to attach such a > corrupt file to see what has been going wrong? @Sebastian -- Sorry, I don't have an example file that we can use to troubleshoot this problem. I created this bug in response to a question on the Ask.LO site and never got an attached file from the OP. It's been a couple months since the last update from OP, so unless you want to try pinging the user again, I think it's probably fine to mark as No Repro and close it out.
Created attachment 66679 [details] corrupted Excel (new format xlsx) created from original ODS with libreoffice 3.6 latest release FRENCH excel a rencontré un contenu illisible dans ...voulez-vous récupere le contenu de ce dossier.... APRES Correction enregistremnt supprimes : plage nommée dans la partie /xl/workbook.xml(classeur) <?xml version="1.0" encoding="UTF-8" standalone="true"?> -<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error055600_01.xml</logFileName><summary>Des erreurs ont été détectées dans le fichier « \\cbinfo\paul\Les emmerdes de cricri\Bug LibreOffice 3.6 WIN7-FR.xlsx »</summary>-<removedRecords summary="Liste des enregistrements supprimés ci-dessous :"><removedRecord>Enregistrements supprimés: Plage nommée dans la partie /xl/workbook.xml (Classeur)</removedRecord></removedRecords></recoveryLog>
3.6.0.4 (Build ID: 932b512) Checked both on Linux X64 and WIN 7 X64 corrupted xlxs (new office 2010) from export generated. XLS (old office 2007 Format) is OK
Same error still with Release 3.6.1 installed today 10.9.2012 WIN 7 X64
It looks very similar to my bug https://bugs.freedesktop.org/show_bug.cgi?id=50090
Hi, I reproduce this bug in this version (and some of the previous). I attach the file corrupted, and the diagnostic from Excel. I use Spanish language pack.
Created attachment 70758 [details] File generated with LibreOffice 3.6.3, that I cannot open in Excel 2010 File generated with LibreOffice 3.6.3, that I cannot open in Excel 2010
Created attachment 70760 [details] Diagnose / error message when try to open the file in Excel 2010
In my case, it seems it fail whenever I use conditional formats.
xlsx files created in Excel 2010; opened and then saved again in LO 3.6.4 (Windows7 32bit) are corrupted. Will open again in LO or Excel 2010 but loose all sheet tabs in workbook and also loose alpha column headings. Excel 2010 also one workbook shows several graphics boxes created by LO (why???) over some of the cells in the one remaining worksheet. Maybe other data corruption, but these are the most obvious. Easy to reproduce with any .xlsx file. Files created in older .xls in Excel are ok when modified in LO, so problem seems to be in new "compressed" xlsx (docx?) formats.
Hmm... a couple of things we can do to try to squish this bug: 1) Test the bug using LO 4 beta builds. I'm not expecting any miracles, but it's a relatively fast check with big payoffs if it fixes the problem. 2) Track down what, precisely, is changing in these files. There are a couple of XLSX files attached to this bug, but both of them demonstrate LO output. What we need are some small xlsx files saved in Excel, and then re-saved in LO so that we can do a side-by-side diff of the output. 3) Reproduce the attached error message, and include the relevant lines (per the referenced line and column) so that we know what input is causing Excel to choke. My Spanish is pretty weak, so if there's a way to get that error message in English, that would help me better understand the nuances of the archive error. Thanks!
This bug is assigned, without anybody in the ASSIGNED TO. Therefore restore it to NEW. @Qubit: thanks for the catch. Kind regards, Joren
Error still occurs on New LibreOffice R 4.0.3
I've got the same problem with docx-files. I opened a WORD-file (docx-format) in LibreOffice Writer 4.0.4 (dutch). I edited it and saved as a -docx file. But opening the file in Word2010 (dutch) results in an error message. Het Office Open XML-bestand XX kan niet worden geopend omdat er problemen met de inhoud zijn. Details: Ongeldig gekwalificeerd teken voor een naam. Locatie: onderdeel:word/styles.xml, regel: 2, kolom 2603 In English: The Office Open XML file XX can not be opened because there are problems with the contents. Details: Invalid qualified sign for a name. Location: part: word / styles.xml, line 2, column 2603 When I try to recover the document content, it says the file cannot be opened with Microsoft Word. What can be wrong?
A workaround: convert the .docx-file to .doc (e.g. with zamzar.com). After doing that you can open the .doc file in MS WORD without any errors.
Noticed that in Spanish LibreOffice incorrectely confuses the decimal character (in Spanish a comma) with the list separator character causing errors in formulas. This happens when saving the file to .xlsx but not when saving to .xls For example saving a file with this formula: =redondear(F2*1,21;2) (which in English is =round(F2*1.21,2) ) saves as: =redondear(F2*1;21;2) So the decimal character ',' is confused with the list separator character ';' This also happens in 4.1.1.2
The bug is still present in version: (in spanish) Versión: 4.1.2.3 Id. de compilación: 40b2d7fde7e8d2d7bc5a449dc65df4d08a7dd38 It is quite a blocker. I have to juggle with .xls format to share files with coworkers.
I can confirm that any ODS file that was created before LO Version 4.2.0.4 (Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 - Windows Version) has issues and can't be properly exported to MS Office .xlsx format, it will end as a corrupted file. All new ods document created with the current version 4.2.0.4 will be save correctly as a Microsoft Excel 2007/2010/2013 XML (.xlsx.) The document will open correctly in Microsoft Office. As a workaround for ods files that where created before 4.2.0.4 that can't be exported you will need to copy the content to a new file. You can easily accomplish this by right clicking the sheet in the affected document select Move/Copy.. sheet from the content menu then selecting Copy in the dialog box and new document in the Location Combo Box. The new file generated can be save as a ODS file that can export properly to MS Excel 2007/2010 format.
(In reply to comment #21) > I can confirm that any ODS file that was created before LO Version 4.2.0.4 > (Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 - Windows Version) has > issues and can't be properly exported to MS Office .xlsx format, it will end > as a corrupted file. When you say 'corrupted file', do you mean that the file will not open with any program (i.e. neither MS-Office nor LibreOffice), or just that the file will not open with MS-Office?
Created attachment 97364 [details] LibreOffice-generated .docx that freezes my MS Office 2010 I have just got a file generated by LibreOffice/4.2.2.1 on Linux which completely freezes my MS Office 2010 on Windows 7 to the point that the process has to be manually killed. Attached.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.