RC2 Update MM2 to MM3: Cannot convert db [F3991 RC3]

[skst]

I installed RC4 over RC3. Same conversion error. I uninstalled MM and re-installed RC4. It ran, of course, because it forgot where my DB is. Unfortunately, when I exited, it crashed with a generic "An error occurred" dialog. I did virtually nothing while it was running--there were no tracks in the library. I opened the Genre node to be sure it wasn't using my library. And, I resized the left panel. Then I hit ALT+F4.

Can I send you a log from somewhere?

I guess I won't bother pointing MM.ini to my DB until it can run and exit without crashing.

[rusty]

skst, haven't seen this in RC4. If you can reproduce the problem, please generate a debug log using dbgview.exe (this is described in the how to report a bug post at the top of the forum).

Thx.

-Rusty

[skst]

Yes, I can reproduce it. Unfortunately, that computer is offline while some remodelling is being done. It should be done soon and I can put up the debug log some time this weekend.

[skst]

The db upgrade still fails in 3.0.1.1127.

I uninstalled the previous RC and installed 1127. I manually moved MediaMonkey.ini from local settings/appdata to /program files and added the DBName= key so that it'd point to where the MM2 db is. Ran it. "There is a problem upgrading your database to the new version." (Or words to that effect.)

I'll generate a debug log using dbgview.exe and submit it.

<... time passes ...>

I can still submit it if you want, but I think the important message is:

Code: Select all

00000076	3.22031283	[2252] Delphi exception, type ESQLiteException, message: Error executing SQL "PRAGMA SYNCHRONOUS=OFF;" : file is encrypted or is not a database (26, 26) 	
00000077	3.22031283	[2252] Exception code: 250477278 	
00000078	3.22031283	[2252] Exception flags: 3 	
00000079	3.22031283	[2252] Number of parameters: 7 	
00000080	3.22031283	[2252] (no debug info) Find error: 7C812A5B 

Now, I can assure you that I haven't (intentionally) encrypted the db. AFAIK, I last ran MM2 on it, installed MM3, and ran MM3. So--AFAIK--MM2 could read it but MM3 cannot convert it. I also uploaded it to rusty, and he didn't say it was encrypted.

Of course, maybe it's been corrupted since then. I'd be happy to upload the db again if it'd help. Please advise as to my next steps.

[Teknojnky]

did you try manually running dbupgrade.exe oldmm2.mdb newmm3.db

??

note that mm3 needs to point to a mm.db not the mediamonkey 2 .mdb file.

[nohitter151]

Does compacting the database via File -> Maintain Library have any effect?

[Guest]

I did not try using dbupgrade because no one from MM (e.g., rusty) said that I should. I didn't want to chance eliminating the problem since the MM team seems to want the auto-upgrade to work.

[skst]

Dag nab it. That "Guest" post was me not being logged in.

MM3 may want to use the MM.db file, but it must still be able to convert from the MM2 MDB file to the new DB format.

Also, I cannot use the program since MM shuts down after the inability to convert the db--no menu bar, no UI, no process.

[Teknojnky]

mm3 should still import if you specified a non-exist mm.db and not the mediamonkey2 mdb file. it supposed to find the mdb file automatically by looking in the default location and/or registry settings for mm2.

I think your problem is you have the mm2 databased specified for the mm3.db which will not work since its expecting a sqlite db and not access, and since its trying to open the file as sqlite, it can't even convert it.

So, if you can try to change your mm3 database to a new (non existing) mm.db file and see if it will import your mm2.

if that does not work, then try to manually import it via the dbupgrade.exe and make sure you specify that converted .db file in the mm3 ini file.

[skst]

That does sound like what's happening, but why would MM3 think that a MediaMonkey.mdb file is a SQLite file?? Shouldn't it figure out that it's an Access file and upgrade from MM2 to MM3??

I'm confused. The only way I know of specifying a non-standard location for the MediaMonkey.mdb file is the DBName key in MediaMonkey.ini in the [System] section. There's no Registry setting and MM3 doesn't scan my hard drive, looking for MM.mdb files (I hope). If I change that to point to (a non-existent) mm.db file, how will MM3 find my MediaMonkey.mdb file?

In fact, when I uninstalled MM2 and installed a clean MM3, it created a default MM.db file and did not find my MediaMonkey.mdb to convert it.

Plus, if I understand correctly, you're saying that MM3 will not work when it's installed over this particular MM2 configuration. IMHO, that doesn't sound like a good idea since I suspect there are a few users who move their databases. (In fact, I'm not sure why there's still no UI for doing so.)

I'll try dbupgrade and post what happens, but I truly hope this isn't the official upgrade path for MM2 users. I'll save a copy of MediaMonkey.mdb in case someone wants to look at it. Thanks for the help.

[Teknojnky]

I don't know if all cases were tested, as far as MM 3 finding the location of the mdb, Yes I am sure it would require that the mdb either be in the default location or an existing MM 2 installation which would reference it. There was a post earlier in the beta about it, I don't remember who posted it tho.

Specifying the database is I would expect a non-standard (while still valid) configuration, I know when I started using MM I specifically set it up manually (which perhaps was not good for testing) so I would not disturb my mm2 install at all.

By set up manually, I mean I installed it and then manually moved and configured the mediamonkey.ini and database myself.

Anyway, I hope you can get it working again with minimal effort once you manually convert the database.

[skst]

I couldn't find any doc on dbupgrade.exe and it doesn't give you a usage page when run without params, but I figured out it's:

Code: Select all

dbupgrade {mdb} {db}

It ran and converted my MM2 MDB file just fine. I updated the DBName= entry to point to it, and everything seems cool.

Now, if only the MM3 install or MM3 itself could notice that DBName= is pointing to an MDB file and auto-run dbupgrade on it....