OOXML considered corrupted by MSOffice

User Support Calc
1

Greetings, thanks in advance for any assitance you may be able to provide.

I updated yesterday to CODE 24.04.9.1. I noticed shortly after than any OOXML created via CODE cannot be open by any MSOffice program (they compain its corrupted). LibreOffice has no issues and files created prior to the update can be opened as well. ODF documents are also unaffected (when switching in the NextCloud admin ui to create new files via ODF instead of OOXML). It affects docs and sheets.

image
image1464Ă—672 13.5 KB

Any ideas?

EDIT: I say “upgraded” but I had built it from scratch again. It was not done via a package manager upgrade.

2

Will check - but can you attach a sample file to a ticket in case there is something interesting in the file specific to your locale, setup etc. =)

1 Like
3

Apologies, it wasnt immediatly clear to me where to create a ticket. Also the forum restricts my ability to upload attachments as im a new user so I’ll link a share to my NC instance. This includes two files, old and new (dated), the old file works fine and the new exhbits the behavior.

4

My simple test exporting our sample test document worked fine. Let me look at yours.

1 Like
5

Your files fail; interestingly:

file ~/Downloads/Kurtis\ *
Kurtis 08-26-2024.xlsx: Microsoft Excel 2007+
Kurtis 10-24-2024.xlsx: OpenDocument Template

6

Turns out you (somehow) saved this as an OpenDocument Template file - if you load in COOL - and Download As an XLSX file - then it works just fine in Excel.

How did you manage to do that ? =) it’s worth noticing that just renaming a files extension in your file-sync client doesn’t change the format (although it does if you’re doing a Save-As in COOL =)

1 Like
7

That one is easy! Lol. These are loaded from a blank template that NC complains needs to be in ODT

image
image720Ă—309 22.2 KB

I did test this also and it worked for me.

CODE is default with fresh unmolested configs. When switching to OOXML in the NC UI it automaitically selects the file extension as .xlsx.

The strange part is this did work for the longest time, maybe it never should have?