Hello,

I have the following problem:

When I try to open a data file with KMyMoney it shows me the error message:

File was not parsable! /home/abuild/rpmbuild/BUILD/kmymoney-5.0.6/kmymoney/plugins/xml/mymoneystoragexml.cpp:1396

I have already tried to find an answer, renamed the file to .gz and opened it, but when I try to extract the file, I get the error messages:

! <filename>: Unexpected archive end.
! <filename>: Checksum error of the file <file to extract>. The file is damaged.

Is there anything I can do to recover the data file or is it really so severely damaged that this is impossible.

Thank you in advance

We definitely need more information before determining whether the file can be saved.
What version of KMyMoney, what platform/distribution, and where did you get it for the program you used to save the file, and to open it now?
What type if file is it? kmy or xml? If you are on Linux, can you do "file yourfile" (that is apply the "file" command to an original copy [you did make a copy, right?] of the file, and also to what resulted after trying to extract it, other than the error message above? What program did you use to try to extract it? Also, where was the file saved? Local hard disk, thumb drive, network file (what file system type)? All this is important information to try to make a good diagnosis.

Hello and thank you very much for the answer.

In the following, I try to answer your questions:
The version of KMyMoney is 5.0.6
I am working on Windows 64 bit.
I got the version from the official KMyMoney download site.
It is a kmy file.
I tried to extract it with WinRAR which didn't show additional messages.
The file was saved on a local hard disk.

I hope this may help in the diagnosis.

The kmy file is actually compressed with gzip, and perhaps WinRAR cannot handle that compression type - I'll have to do some research. If you right click on the original file (or a copy) in Windows Explorer. and click Properties, what type of file does Windows think it is? Do you have any backups?

For the original file (extension kmy) Windows says it's a KMY file.
For the file with the extension gz Windows says its a WinRAR-Archiv (.gz)

Actually it's not my file. They gave it to me because I recommended them to use KMyMoney which until now worked without any problems.
When I was searching KMyMoney automatic backup files on their computer, I found the last backup made in the year 2018.
And out of not lack of sense of responsibility, they didn't make any backup copies.

Is there any trustworthy person who could try to recover the data because it's very important data of a school?

Did you also look for files that ended in .kmy.#~ where # is a number between 1 and 9 or so? If you have those, you are lucky. The one with the lowest number is the one you want to try. Otherwise the following holds true:

According to the winrar website it supports uncompressing gzip compressed files. In case it cannot do so, chances are very low that the data can be recovered. See this report about a repair trial. One could give it a trial as the data contained is pure ASCII in form of XML, but looking at the bottom what it needs and that the success rate was on at 75% I don't think it is worth the effort. Looks like there is some work ahead of entering all transactions since the last available backup. So we are back to no backup, no mercy. Sorry.

Thank you for the response.

Of course, it's true. No backup, no mercy.

I'll try to investigate the source files to maybe learn the structure of the data file and see if I can find where the data is corrupted.

The format is XML. Once you see that in your corrupted file then we are a bit closer to a solution.

So far I only see Chinese letters when I open it in notepad

Seeing "chinese leters" suggests you are looking at a binary file. If the corruption is in the compression, there is probably no hope, unless uncompressing can succeed with the first part of the file and just runs into problems before the end. Is there any more verbose mode for winrar when you decompress one of the files? Also - I wonder if the problem is that the file is in some multi-byte character set. Probably not, but I think if you try opening it in Word instead of Notepad, that would rule out that problem. (No, it's clearly not really a Word file, but I think Word is likely to handle non plan Ascii text better than Notepad. Easy enough to try. If you don't have Word, LibreOffice Writer should do as well.)

The file I'm looking it is the .kmy file.
Word shows a lot of column breaks. Notepad++ shows more like

‹ºñä^ ì½[sãF¶.ø>¿ã™9»;âÈ…+Aø¸§C·ºJUÚ’ªÜíèð‰$™"³4.rIoó?NÄŒ#úÅýÐá‰ó°Ã;vÄðí¿0™ ‚$°r©„º½wÛªR‚Ä—XÈür]¾õí¿Œ}íŽF1ƒ?|e|­¥Ñ X0üÃWirsÐýêÿçÿòíÿzòáøúϧڻó?Ÿxú烗oÎNù/Öþ¬}+þûæýËügíÛãËÓÃë7Þÿ÷“ÃëSm@ú‡¯LÝpãÀ4¿z‘
:;¼ºþïçNÞ¼|sz²:ÒÔô΁aÍG~:½¼âŸ¦±¿Õùß½|ó§â_;Ù_û¢pß~¼:½Ô2æÉэ óùÙŇ''—§WWZŸ%÷â—ý0
f?=° Ÿ…ìŠ8‰(MÄO õédâ¯g_#>ZüðæýÕõ›ëëÕìSþð•5ûŽÂ¯´1 ȐFâ³Ä;ÑÅ?ÿŠ0J_7»Ñ×WGÇÙõ›7¹¼~“e·%®9>þðñýõ›“«ìÏ…¿È¾ø­iÚóÑe¿uòß~ûbíþ}wúçO‡gO/ß\.>_ü¬ÝR~ƒ=ÖÿJ»#~Z¸—|û¢0/¸y2Ëæé‚Ü_·3e9.0S–mB¿5ák-ÕfÙ*›åš&qDµw°¤G‚[íðÕ®g½Ù§®ïuæVþ,FðOüóéiþ²wøÝf×eͧ6éøJÒói¶\i½¡_\ébÂ/¯ó¡Ù%Ùê‹i¿ŽHÏ.bä«ù‡ƒ0¢}ÓìC—W­.m›eÆÉæ’'ÙR[ò¾}‘AÙ”Y
*[ÙڄŪÆrñwhj—Œo¡D;þÏÿø÷>ÿˆ¸UølÐ cŸÂVáqªñœ³ˆÞíðkíxD&íz¥:Õ°¾ý›! †Ú9I’#±ö:

Taking an application like word or libreoffice does not help here at all. You need to unzip the file first. For windows users, I suggest to use a bash like shell (e.g. git-bash) to try to unzip the file. At least, one can use the file utility to see what it thinks the file contents is. Windows is dumb at that point, because it only looks at the file extension. The file utility is smarter: it looks inside the file no matter of the extension. The output you need to find looks like this:

Code: Select all

$ file thb.kmy
thb.kmy: gzip compressed data, was "", last modified: Fri Aug 24 12:57:11 2018, from Unix


Good luck!

The problem is just that: I cannot unzip or decompress anything because of the errors which appear as I mentioned in my first post.

kde-wolf wrote:The problem is just that: I cannot unzip or decompress anything because of the errors which appear as I mentioned in my first post.

Hope you've got this issue solved?