Description: I am converting MS Excel 2007 XML spreadsheet (not the XLSX) to xlsx file using the following command: /usr/lib64/libreoffice/program/soffice.bin --headless --invisible --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --convert-to xlsx --outdir /var/tmp test.xml. This fails with the message: Error: source file could not be loaded File size of this xml file is 11Mb. Other smaller file (upto 5Mb) are converted without any proble. Steps to Reproduce: 1. Pick any XML file larger than approx. 5Mb 2. use command: /usr/lib64/libreoffice/program/soffice.bin --headless --invisible --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --convert-to xlsx --outdir /var/tmp test.xml 3. Actual Results: No xlsx file created. Get the message "Error: source file could not be loaded" The status returned by soffice is: 0 Expected Results: xlsx file shoud be created in /var/tmp directory Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: When opening the same file in the interactive session of Libreoffice, It gives General Input/Output error. When press retry button on this message box, it opens the file with no further error. The file in this case have 15922 rows.
Created attachment 158045 [details] This is an MS Excel XML with anonymised data for testing. Please see attached MS Excel XML with anonymised data for reproducing the issue in the support.
On Win10 with LO 6.3.4, no problem to open the file. 5.3.6 is an old version, could you give a try to last stable LO version 6.3.4? (also, please compress your file instead of sending a file of 11,5MB, the same file zipped is less than 400kb)
Thanks. I will take care and upload zip files. As per our linux system administrator's the libreoffice-5.3.6.1-21.el7.x86_64 is the latest available for the Linux!! I am not allowd to download/install any software.
What's your Linux distrib? If it's already fixed on a newer version, we won't be able to do anything.
Thanks. I will ask the Linux admin to get the new version.
Since there's no specific fix, let's put this one to WFM then.