MM4 didn't import MM3 database?

by **ODO** » Thu Dec 29, 2011 8:57 am

Hi

I initially screwed up just the same- the MM4 setup made it way too easy, and no warning was displayed :-(

I am running my MM installation in a "portable mode" from an external HDD since version 3. I edited the MM.ini to point every path to the right drive letter etc., and everything worked just fine as long as the drive was mapped to that specified letter.

Then I saw the "portable mode" check box in the setup and thought "Ihaah, they heard the call". Of course I checked it. After that I had a clean install as many said. I re-run the setup without the "poratble mode" checked and it upgrade the DB- and kept all settings specified in the previous MM.ini obviously as well. So as long as your DB has still the same size as before it will be intact even if the "last modified" date changed (and then there are backups... ;-)

)

My questions is now: if I run the setup with "portable mode" checked after the DB is upgrade will I loose all settings again? What is that setting for anyways?

Cheers,
Ondrej

by **KEP** » Wed Nov 16, 2011 5:22 pm

nohitter151 wrote:If you've moved the database from the default location, the automatic upgrade wouldn't take place.

Ahhhhh, the missing link! Any idea this exclusion occurs? Seems like a pretty lame limitation.

That KB ought to be updated to reflect this, and be clear on whether this is a bug or by design.

nohitter151 wrote:If you need to manually upgrade the DB, you can do so as described in the KB:
http://www.mediamonkey.com/support/inde ... ticleid=57

Leery of that one, as it specifically says that it's meant for upgrading v2 databases (which were MDBs, as I recall?).

At any rate, all I had to do was make a copy of my MM3 database, point MM4 at it (via DBName in INI), and the upgrade proceeded just fine. But that really seems like something that ought to be handled as part of the setup and/or first execution.

Thanks!

by **nohitter151** » Wed Nov 16, 2011 5:10 pm

KEP wrote:
Lowlander wrote:It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

Two upgrade installs, Zero upgraded databases.

If you've moved the database from the default location, the automatic upgrade wouldn't take place. Likewise installing MM4 in portable mode would not upgrade the MM3 database. If neither of these scenarios do not apply, I could not say why the upgrade didn't take place, but I can confirm that it's working fine for my PC and that the upgrade process is working for several other users who have reported so via the forum and support.

If you need to manually upgrade the DB, you can do so as described in the KB:
http://www.mediamonkey.com/support/inde ... ticleid=57

1) Go to the command prompt, and switch to C:\Program Files\MediaMonkey

2) Type dbupgrade.exe old_MM_database.DB new_MM_database.DB
where old_MM_database.DB is the location of the old database and new_MM_database.DB is the location where MM should generate the new database.

by **KEP** » Wed Nov 16, 2011 4:58 pm

Lowlander wrote:It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

Two upgrade installs, Zero upgraded databases.

by **Lowlander** » Wed Nov 16, 2011 2:14 pm

It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

by **KEP** » Wed Nov 16, 2011 1:58 pm

Lowlander wrote:I presume it should have picked up DB and settings. Seaming same issue here: viewtopic.php?p=318399#p318399

Similar issues, though hopefully just the technical ones. :lol:

I certainly got the prompt to steal associations. And could rant about that, were I inclined. (I really hate "opportunities" to screw up system settings, that can be chosen with one too-quick click! That should really be a far more conscious decision. It's nearly as bad as Flash trying to sneak McAfee past you! But I digress. :wink:

)

Doesn't sound like that poster was offered the opportunity to import the old DB either. So, is this something that's just supposed to happen by default, or is it like the associations and something you need to initiate? My instinct, as a developer, would be to create backups of (or at least ask to) both the DB and INI(s), to facilitate easy rollback.

Still trying to fully understand the utility of these newfangled collections, and your post over there was the first time I ran across "Types", so even more to look up now. Will get there, though. Thanks!

by **Lowlander** » Wed Nov 16, 2011 1:22 pm

I presume it should have picked up DB and settings. Seaming same issue here: viewtopic.php?p=318399#p318399

by **KEP** » Wed Nov 16, 2011 1:14 pm

Lowlander wrote:Did you do a portable install?

No.

EDIT: May not have mentioned before. Running Windows 7 x64 on all affected systems, so far.

by **Lowlander** » Wed Nov 16, 2011 1:08 pm

Did you do a portable install?

by **KEP** » Wed Nov 16, 2011 1:07 pm

KEP wrote:
Lowlander wrote:I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

Yeah, sure did. It seemed to lose a lot of the settings. Database location, folders to track, Auto Organize patterns, etc. Nothing tragic, but it was really more like a fresh install than what I might've expected.

Repro'd on another system. Installing MM4 over MM3 results in a totally fresh install. The old INI is wiped, the old DB is ignored. Shouldn't there be an option to use as many of the existing settings as possible?

by **KEP** » Sat Nov 12, 2011 1:53 pm

Lowlander wrote:I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

Yeah, sure did. It seemed to lose a lot of the settings. Database location, folders to track, Auto Organize patterns, etc. Nothing tragic, but it was really more like a fresh install than what I might've expected.

by **Lowlander** » Sat Nov 12, 2011 1:42 pm

I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

by **KEP** » Sat Nov 12, 2011 12:42 pm

Lowlander wrote:Yes, you can still customize the location of the database in MediaMonkey 4 the same way: http://www.mediamonkey.com/support/inde ... ticleid=46

Ah, great! Bad assumption on my part, I guess. When MM4 didn't do that automatically, it threw me. Later on I noticed MM4 didn't seem to take any MM3 settings into account, other than my license status.

Thanks...

by **MattTown** » Sat Nov 12, 2011 12:48 am

I also have MM3 on a D: drive to ensure that it all gets backed up, and have had previous re-installations trash "date added" and playcounts.

Is this understanding of the MM3 - MM4 upgrade process for a D: drive installation correct?

Close MM3
Download MM4
Install MM4 to the preferred location (eg D:\MM4)
Close MM4
Relocate the MM3 db to an appropriate place in the MM4 installation and upgrade the MM4 mm.ini file as per the KB article
Start MM4

Assuming this is right, do I have to do anything else to get the previous MM3 db contents gets imported without or corruption?

Thanks

by **Lowlander** » Sat Nov 12, 2011 12:34 am

Yes, you can still customize the location of the database in MediaMonkey 4 the same way: http://www.mediamonkey.com/support/inde ... ticleid=46

MM4 didn't import MM3 database?

Post a reply

Visual Confirmation

Expand view Topic review: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?

Re: MM4 didn't import MM3 database?