[SOLVED] New v1.8.1 rejecting .emb database password

[josh555]

I am elated to see that version 1.8.1 for Windows 64bit is available especially as it contains the much awaited 256bit encryption. However, when I try and open my existing .emb database with the usual password, an error message appears saying that it is an incorrect password for this database. Do I need to change anything? I have now reverted to v1.8.0 and all is working fine.

[KenK]

@josh555 you need to
- save your 1.8.0 database as a .mmb
- open that with 1.8.1
- save it again as a .emb
Remember to delete the .mmb afterwards.

[thiruma71]

Following these steps didn't help. Receiving SQL Lite error.

[Giapo]

i had the same problem.
Has anyone solved it?
thank you

[josh555]

Thank you Kenk, that has worked for me. However, I have opened the same encrypted database on my android phone and marked an entry as reconciled but even after synchronising the phone app, the change is not registering in the Windows desktop app (even after closing and reopening). Is there something else that I need to do? Both apps are definitely pointing to the same .emb file. The same applies in reverse and a change on the desktop is not registering on the android app.

[Eduardommex]

Hi
I am reporting the same problem. After updating Flatpak MMEx 1.8.1 version opened the mmb file and trying to save as encrypted emb file this error message come up: "SQL logic error[1]: Rekeying failed. Pagesize cannot be changed for an encrypted database." Could somebody help me?

[fenman]

+1

On Windows 11, it says that the password for this database is incorrect or the file is not a database.

[hxigor]

Same error here
SQL logic error[1]: Rekeying failed. Pagesize cannot be changed for an encrypted database

[guanlisheng]

can anyone share a mini database to reproduce the issue?

[hxigor]

can anyone share a mini database to reproduce the issue?

Here you are

Test_181_EMB.mmb

(113 KiB) Downloaded 28 times

Open the file and try to save it as EMB file, a password dialog will pop out and when you enter any password, the sql error occurs:
SQL logic error[1]: Rekeying failed. Pagesize cannot be changed for an encrypted database.

The database is an EMB file from version 1.8.0, where I saved is as MMB and then opened in 1.8.1, deleted everything except 1 account and 1 transaction, then optimized it and finally saved as MMB and then tried to save as EMB.

[yopiglop]

Same as hxigor here

[Renato]

I would suggest that users revert to version 1.8 or not use encryption until the bug is fixed.

[guanlisheng]

Thanks @hxigor and also the guy from the Github, we know it is page_size that triggers the issue now.

for some very old databases (e.g. before 2014), the page_size is 1024, while newer ones are 4096.

you can run PRAGMA page_size in wxSQLitePlus or any SQLite clients to tell the result.

• 4096, it will be fine to re-encryption

• 1024, you might have to update page size to 4096 via next reply

391296795-ff5eaba1-5a2a-4956-8c4b-3cc9c7937e70.png (97.3 KiB) Viewed 1350 times

[guanlisheng]

here is the instruction to update the legacy page size (1024) to the default page size (4096).

run the following code to update page size in place

Code: Select all

PRAGMA page_size = 4096;
VACUUM;

391297483-133c6503-74f5-4c1b-b9a9-c64899198041.png (108.71 KiB) Viewed 1214 times

[hxigor]

@guanlisheng
Thanks for the analysis and fix, changing the page size to 4096 worked!

[Giapo]

Could you explain in detail the steps to take?
Thank you

[Renato]

https://github.com/moneymanagerex/money ... ssues/6971