Page 1 of 1

Error loading database since v 3.1.2 (build 744) upgrade

Posted: Mon Nov 09, 2015 7:37 pm
by Colourqueen
Hi

I've been happily using Moneymanager and syncing via Dropbox for about 9 months now.

However the latest Android upgrade has caused problems for me.
When I try to open my database from Dropbox, I get a stream of SQL errors. They whiz past on the screen - if someone can tell me how to catch them in a log, I will gladly do that.
The database seems to be OK after the errors but I find it all a bit disconcerting and wonder if everything is ok with the database.

The errors are to do with "Error executing Raw SWL, Error creating Asset Classes....

They happen each time I load an amended database from Dropbox.

I also noticed that the new version reset the number of transactions to view back to 'last 7 days'

Can anyone offer any advice please?

Thanks

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sat Nov 14, 2015 12:24 pm
by Colourqueen
Guys - any ideas?

I've updated to version 2015.11.13 (Build 745) and it is still happening.
I've deleted the database on the android and it still happens with no database present.
The message concerns Error executing Raw SQL and  error creating assetclass. Several sql statements flash past.

If I go into "Asset Allocation" in the menu, I get the message "error loading data in cursor loader" then it asks for a new database.

Thanks

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Tue Nov 17, 2015 8:42 am
by MisterY
Hi,

One thing you can try is to check the Logcat from the About screen. There are two options - one will open the message log in a separate screen while the other will open the log in an email, ready to be sent to us for analysis. The first option is better if you just want to check what is going on.
It is interesting that the messages still pop up even after you delete the database. Can you check the database file path in the Database settings?

Also, while I understand that this is the "Support Forum", I would still recommend using email should you need a faster response. Please have in mind that this is a hobby Open Source project to which everyone contributes as much of their free time as they can.

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Mon Dec 21, 2015 5:55 pm
by Colourqueen
Thanks I've finally got back to this.

When I check db schema, I get an error - tables missing: CURRENCYHISTORY_V1

I've checked the database file path, deleted the database named there, and re-synced from dropbox and still get the error.

I've captured in on the logcat and emailed it off.

I hope this helps get to the bottom of the issue.

Thanks again

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 6:23 pm
by Braik
Hi guys

Does somebody found the solution to this problem?

It's happening to me since 3 months, I am unable to open my database from my android device.

This problem happened first in my old Phone, after that it happenend on my tablet and now in new phone.

Please help

Braik

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 6:26 pm
by MisterY
Hi,

What exactly is the problem?

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 6:43 pm
by Colourqueen
Thanks for your interest.
My error stopped happening a couple of versions back.

The latest version (version 2016.05.03(build 839) is fine.

I was getting errors about tables not being present -  missing: CURRENCYHISTORY_V1. I did have a response when I sent in the logcat.
You said "It seems that the database upgrade script is triggeredalthough you already have the correct version of db".
Maybe this will help pin it down for Braik?

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 6:51 pm
by MisterY
Right. That's what I mean. There might be some edge cases that prevent the database from loading. So, some more details would be useful in troubleshooting.
One can always create a new database file for comparison.

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 7:15 pm
by Braik
It tells me "error loading data in cursor loader" and then "error your database file is corrupt !"

When it does not break my file and I loose my file even in the PC.

Any ideas ?

Braik

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Sun May 15, 2016 7:37 pm
by MisterY
You can try opening the file in DbBrowser for SQLite on desktop, or something like aSQLiteManager (https://play.google.com/store/apps/deta ... ager&hl=en) on Android and see if the file is a valid database.
In general, try to restart the app after switching databases.

I'm sorry but I can't offer any more meaningful assistance without knowing the details of your setup.
I have never had any issues opening the synchronized database on Android but I've seen other users run into different issues.

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Mon May 16, 2016 10:44 pm
by Braik
Hi,

It is not a database problem since I am able to open it in my PC (also with sqlite with no issues), some good news, now I can open it in my tablet, but still not able in my android phone

Always same message:
"Error your database file is corrupt !"
"Error loading data in cursor loader"

Please help me, some other info, could it be a problem because I have two dropbox linked accounts ? one personal where the app saves the file and another for my work ?

Thanks

Braik

Re: Error loading database since v 3.1.2 (build 744) upgrade

Posted: Tue May 17, 2016 8:33 am
by MisterY
OK, based on what you say I would assume that the database is not encrypted?
If so, please try opening the database with the following app:
https://play.google.com/store/apps/deta ... ager&hl=en
or something similar. You can also check it with Total Commander or any other file-system utility. Check the file size and try to view it as a text file.

There could also be an issue with the permissions on the database folder if something has changed with the system since the last time the database was accessed. You can try renaming or deleting the existing folder MoneyManagerEx on Internal Storage and let the app recreate it automatically. This will also automatically assign the correct permissions by the system. Then, download the database from Dropbox through the Dropbox Settings screen and you should be good to go.

Let me know if there are any issues encountered along the way.