So I have downloaded SQLite3 in the hope that I can debug it.
I saved my .MMB by renaming a copy as .DB and opening it in SQLite3.
Then .clone as NEWDB.DB, then renaming that as .MMB.
When I try to open it (open Existing Database) in MMEX, I get a popup message:
"MMEX upgrade
Have MMEX support provided you with a debug/patch file?"
It is trying to copy NEWDB,mmb to NEWDB.mmb_upgrade_v0_YYYY-MM-DD.bak, but needs a debug/patch file in order to do this.
Otherwise, I am stuck trying to resolve the inability to debug my MMB with years of finance data.
Your help would be gratefully received.
INFOTABLE_V1: Exception unable to open database file[14]:
Moderator: Renato
Re: INFOTABLE_V1: Exception unable to open database file[14]:
The first part of my topic was:
Win64 11, MMEX v1.5.15 64bit
On every navigation operation, I am getting popup error messages:
NFOTABLE_V1: Exception unable to open database file[14]
with a variety of
INFOID
INFONAME
INFOVALUE
Each table takes an age to load.
Although I (apparently successfully) Import a CSV of transactions, they do not appear in the account, and are not saved when I quit MMEX.
This first started over a week ago on v1.5.14, and upgrading to v1.5.15 has not improved it.
File/ Save Database As ... does not work. Explorer comes back with an inappropriate message:
"path/filename
File not found.
Check the filename and try again."
Win64 11, MMEX v1.5.15 64bit
On every navigation operation, I am getting popup error messages:
NFOTABLE_V1: Exception unable to open database file[14]
with a variety of
INFOID
INFONAME
INFOVALUE
Each table takes an age to load.
Although I (apparently successfully) Import a CSV of transactions, they do not appear in the account, and are not saved when I quit MMEX.
This first started over a week ago on v1.5.14, and upgrading to v1.5.15 has not improved it.
File/ Save Database As ... does not work. Explorer comes back with an inappropriate message:
"path/filename
File not found.
Check the filename and try again."
- Renato
- MVP MMEX User
- Posts: 655
- Joined: Mon Apr 25, 2011 7:36 pm
- Are you a spam bot?: No
- Location: near Zurich
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Probably a problem with the access rights to the database or other files of MMEX.
Renato Forum Administrator
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Thank you Renato.
I checked the properties of mmex.exe and added write permission for myself as user.
Also the database file .mmb, which had all the necessary permissions.
But I still get the same issues.
There are 112 dll files as well, which do not have write permission for me as user.
Can you advise which may need to have write permissions added?
I have also tried running mmex as administrator, but still get the same issues.
-
- Super MMEX User
- Posts: 126
- Joined: Fri Jan 03, 2020 3:24 pm
- Are you a spam bot?: No
- Contact:
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Any chance you have the database open in two places?
Just to rule it out, have you restarted the computer?
Just to rule it out, have you restarted the computer?
- Renato
- MVP MMEX User
- Posts: 655
- Joined: Mon Apr 25, 2011 7:36 pm
- Are you a spam bot?: No
- Location: near Zurich
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Suggestion:
1) Download the latest version https://ci.appveyor.com/project/moneyma ... /artifacts
2) install this version with option delete old version.
3) copy .mmb database to documents folder if it is not already there.
4) start MMEX and select this .mmb database.
But see also in the personal messages.
1) Download the latest version https://ci.appveyor.com/project/moneyma ... /artifacts
2) install this version with option delete old version.
3) copy .mmb database to documents folder if it is not already there.
4) start MMEX and select this .mmb database.
But see also in the personal messages.
Renato Forum Administrator
Re: INFOTABLE_V1: Exception unable to open database file[14]:
I have installed the latest v1.5.16 as you describe but still get the same INFOTABLE_V1 errors.
I have sent you a private message.
I have sent you a private message.
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Do you have the DB open in MMEX and SQLite3 at the same time?
If not, then it sounds like it is having permissions problems accessing the settings file. Have you tried the standalone version of MMEX?
If not, then it sounds like it is having permissions problems accessing the settings file. Have you tried the standalone version of MMEX?
- Renato
- MVP MMEX User
- Posts: 655
- Joined: Mon Apr 25, 2011 7:36 pm
- Are you a spam bot?: No
- Location: near Zurich
Re: INFOTABLE_V1: Exception unable to open database file[14]:
Hello Bigessay
Your .mmb database is perfectly fine, I was able to open it without any problems.
I suspect that the permissions to access the Documents folder are not set correctly.
As a trial, I would save the .mmb to another directory (using CTRL-C and CTRL-V) and then open it in MMEX.
It could also be errors in the file system, which can be analyzed with the Windows Terminal (Administrator) (right mouse button on Windows Start) by entering chkdsk c: and fixed with chkdsk c: /f (requires a restart of Windows).
Another possibility is to delete the file mmexini.db3, it contains the settings of MMEX and is automatically recreated with default values.
Your .mmb database is perfectly fine, I was able to open it without any problems.
I suspect that the permissions to access the Documents folder are not set correctly.
As a trial, I would save the .mmb to another directory (using CTRL-C and CTRL-V) and then open it in MMEX.
It could also be errors in the file system, which can be analyzed with the Windows Terminal (Administrator) (right mouse button on Windows Start) by entering chkdsk c: and fixed with chkdsk c: /f (requires a restart of Windows).
Another possibility is to delete the file mmexini.db3, it contains the settings of MMEX and is automatically recreated with default values.
Renato Forum Administrator
Re: INFOTABLE_V1: Exception unable to open database file[14]:
My thoughts were the mmexini.db3 hence the reason for asking to run the standalone version.Another possibility is to delete the file mmexini.db3, it contains the settings of MMEX and is automatically recreated with default values.