Page 1 of 1

database disk image is malformed[11]:...

Posted: Sat Mar 07, 2020 4:26 pm
by Wirmike
Posted this around 1h ago but seems to have disappeared from the forum!
The time stamp was odd - should it have been related to UK (GMT?).
Your website was unavailable for what seemed like forever! ARGHH!! I was beginning to become quite concerned!
Was there a problem? Perhaps a networking issue?

Anyhow, please see the re-written post below.

There have been other reports for this error, but none as can see for Mac AND none that seem to apply to my set of circumstances - hence the post.

I have just started to get this window when opening your App ...

"mmex Error

database disk image is malformed[11]: database disk image is malformed"|


It appears to affect even any of my backups when I try to run MMEX from them in Finder.

Also, if I restore a time-machine back-up (into a temp folder)!
Also if I try to run from a Dropbox file!
.. - irrespective of the time-stamp on any of the files I tried.

In short, I am totally unable to use MMEX!

Apart from a mysterious lock-up yesterday all the files seemed okay yesterday.
Everything else on my Mac seems to be okay today!





Mmex v:1.3.3
MacOS: 10.13.6

Can you help?

Re: database disk image is malformed[11]:...

Posted: Sun Mar 15, 2020 8:17 am
by guanlisheng
Hope v1.3.4 would avoid similar thing.

Re: database disk image is malformed[11]:...

Posted: Sun Mar 15, 2020 8:37 am
by Wirmike
Had that hopeful thought myself.
Any idea when v 1.3.4 will go live?
Regards

Re: database disk image is malformed[11]:...

Posted: Sun Mar 15, 2020 8:39 am
by guanlisheng
Should be soon and we have v1.3.4-beta for windows and Linux

Re: database disk image is malformed[11]:...

Posted: Tue Mar 17, 2020 1:17 pm
by siowena
@wirmike

When you say "when I try to run MMEX from them in Finder" I'm assuming you're clicking on the mmb file.

In that case, MMX when is starts attempts to open the last opened file and not the one you clicked on. (something that caught me out once or twice)

Have you tried to open the file (one of the backups or the file from timemachine) directly from the file open menu ?

---
Something else to try is use a SQLLite DB tool to see if the file is still intact as SQLLite DB and has not become corrupted.