Error=XML_ERROR_EMPTY_DOCUMENT ErrorID=13 (0xd) Line number=0
I worked on this piece recently, I need to use it soon, but I can't load this file due to Error=XML_ERROR_EMPTY_DOCUMENT ErrorID=13 (0xd) Line number=0, can anyone help me? How can I fix it?
| Attachment | Size |
|---|---|
| Chwal-Syjonie-Zbawiciela.mscz | 28.35 KB |
Comments
I looked at it with "Bless" hex editor program. It starts off as a normal file but is missing the last 23 bytes and it might have some internal derangement, too'
I changed its name name to "a.zip" and used the unbuntu command-line zip repair tool:
zip -FF a.zip --output b.mscz
The name changes aren't isn't essential, it just makes it easier to type in than the full title.
In reply to . by underquark
Can you help with how to use the program? I have an arrangement that won't open due to similar reasoning
In reply to Can you help with how to use… by Just._.Jay._
The score music from MuseScore is in a file format .MSCX which is like an XML file
MuseScore takes .MSCX file plus styles and other data and they get compressed into a .MSCZ file which is basically a .ZIP file
I'm using ubuntu 22.04. Windows and Mac have their own programs but I don't know much about them
Ark is an archive/decompress program (it can read ZIP, MSCZ files, extract files)
Bless is a hexadecimal editor that reads the bytes of a file and displays code or text.
Note that we are dealing here with files that won't open as opposed to those that do but that have corruption in the score itself with measure of the wrong duration etc.
My algorithm, for files that won't open is:
Is the filesize 0 bytes? If Yes, then Game Over
Can I open it with Ark? If Yes then try to extract the .MSCX file
If Ark fails, then I change the file extension to .ZIP and use the ubuntu console to run the Zip program with the -FF option which does a deep attempt at repairing a damaged .ZIP files:
zip -FF infile.zip -- output outfile,zip
If I still can't retrieve the file, I have a look around with Bless to try to see what's missing. i have seen one file where the first line is wrong and several where varying lengths of code are missing at the end of the file.
So, it seems to me that this "corruption" is at the file save level as opposed to internal problems with the MuseScore file. There are (at least) five types: 1]The zero-length file, 2]The file that looks to be the correct size but only contains repeated values of 00, 3]Files missing the end portion, 4]Files missing the beginning portion, 5]Totally garbled files with no recognizable MuseScore elements.
Whether the problem is a fault of the MuseScore program or of the operating system or of the interaction between the two, I can't say, except that I don't think I've ever seen it on any of my own music files and I have been using ubuntu since before I joined this forum.