Topic: MC24 upgrade did not retain my library info. (Read 4224 times)

bugeyed · « **on:** April 23, 2018, 01:43:13 pm »

How do I tell MC24 to find my files after upgrading from MC23 to MC24 23.0.16. It found some files, but they were not in my main music folder.
Edit: This should have been posted in the MAC forum. Sorry.

Awesome Donkey · « **Reply #1 on:** April 23, 2018, 02:32:03 pm »

Restore a library backup from MC23 into MC24.

https://wiki.jriver.com/index.php/Library_Backup

RoderickGI · « **Reply #2 on:** April 23, 2018, 04:09:38 pm »

This issue is all too common. I have rarely had a MC major upgrade find the library for the previous version of MC and upgrade it as part of the first install.

The major upgrades should find the previous version and use that, or if there is more than one previous version and library, it should offer a list of available versions with their libraries for the user to select the correct one.

Plus, my current bug bear, there should be an option to update all the Windows File Associations to the new version. The update hasn't done this properly for quite some time for me. Maybe three years or more. I use the Express Installation usually, but I have tried the Custom Installation. Not updating the Windows File Associations means that executing the mjr licence file doesn't work, as the incorrect version of the PackageInstaller.exe is used.

Restoring a backup from a previous version, including settings, doesn't update the Windows File Associations for file type not included in the MC functionality, which means the mjr file for one.

JimH · « **Reply #3 on:** April 23, 2018, 04:41:57 pm »

I don't doubt that it happens but I've never seen it.

Too bad our crack beta team didn't catch it.

Anything unusual about your install or backup locations?

RoderickGI · « **Reply #4 on:** April 23, 2018, 06:12:15 pm »

I have reported it before but didn't make a big issue of it. There seem to be a lot more reports of needing to restore a backup this year.

I have reported the Windows File Associations a few times as well. The upgrade process just doesn't seem to address that issue at all for me. Also quite a few reports of that nature this year.

Nothing special about my installations, except perhaps that I usually have two versions of MC installed when I upgrade. So MC22 plus MC23 when I upgraded to MC24. Main library on the HTPC is in the default location, so should be found. On my client I use a local library as the default, in the default location, so that should be found. Backup location on the HTPC are standard, and custom on the Client, but both as per Options. The backup location for multiple libraries is common to the PC of course, so all backups are in the one directory, mixed together.

Half the problem about catching it and reporting it is that it only happens once a year, and I only do two upgrades on two PCs. Replicating the problem to identify the cause would be a real pain, since I would have to uninstall all MC versions and licences, then install say MC22 and MC23, licence them then upgrade to MC24. I would probably have to start playing around with VMs, or full backup and restores of my boot disk, in order to identify the cause. Your crack Beta Team can only do so much.

PS: Also, there is the issue that the upgrade process usually isn't settled down at the time the Beta Team members do the upgrade. There are often a few things left undone in early versions. I waited until I think MC24.0.5 before upgrading this year. Same issue.

JimH · « **Reply #5 on:** April 23, 2018, 07:22:28 pm »

We'll take a look. Thanks.

RoderickGI · « **Reply #6 on:** April 23, 2018, 11:36:13 pm »

Thanks Jim.

Even if someone could just state the conditions under which a MC major upgrade will find and use the previous version library and settings, and the conditions under which it will not, would be a great start.

Things that might include are:
Only one other earlier version of MC installed.
If multiple earlier versions of MC, what happens?
The Library is stored in the default location, or not.
The installation is done as an Express or Custom install.
File Associations are checked and/or changed by the user during the upgrade. Or not.
The installation is a Client, or Server. If a Client, what does the default library need to be?
Does the upgrade change ALL Windows File Associations from the previous version to the new version, or just those listed during the installation? (Missing the mjr file, in the latter case.)

I'm sure there are more potential issues, but that is a quick brain dump.

Hendrik · « **Reply #7 on:** April 24, 2018, 01:50:34 am »

The OP was talking about Mac, I'm actually not quite sure how that works there since it doesn't use our normal Installer.

This is for Windows:
- The installer will find your library from MC20 to MC23 automatically, earlier versions require a manual restore.
- It'll only import the "Default Library" (the one MC came with, no matter which one is your startup library), however it doesn't care if you renamed or moved it (it'll find it)
- Settings are stored on a per-user basis, so if you need to install using an entirely different user account (because yours isn't an Admin), migration won't find its things
- Installation mode makes no difference
- If multiple old versions of MC exist, it should use the newest
- File Associations should be updated in the installation process, just like a fresh install

Of course that doesn't rule out that there might be a bug in any of those steps, but at least in our testing it seems to work reliably.

JimH · « **Reply #8 on:** April 24, 2018, 06:19:38 am »

Thanks, Hendrik. I added this to the wiki here:
https://wiki.jriver.com/index.php/Upgrade#Data_Migration

astromo · « **Reply #9 on:** April 24, 2018, 07:09:37 am »

On Windows, I didn't have a problem with MC23 -> MC24. Otherwise I would have flagged it. Don't forget we're ahead in time over our way (apart from the Kiwis ... gee what am I saying?

hee hee

), so I think the Ozzie contingent does a pretty good job at picking up the odd thing or two.

Even so, being the cautious type that I am, I manually backed up the MC23 library and stashed it somewhere handy before upgrading to MC24. Didn't need it but for the sake of a couple of extra steps that take virtually no time at all, it's cheap insurance. And if it's not needed, no big deal.

Hopefully the Mac version can match Windows reliability for this function soon.

RoderickGI · « **Reply #10 on:** April 24, 2018, 06:10:09 pm »

Thanks Jim and Hendrik.

I'll have to take more notice and try to report what I find in the next major upgrade, MC24 to MC25. But I can confirm that Windows File Associations did not get updated in my MC22-23 and MC23-24 upgrades. I was left with a mix of two versions of MC with File Associations in Windows, and the mjr association was left with the older version each time. I've had to go in and manually update Windows so that only the latest version has any file associations.

I think it happened with MC21-22 as well, but don't recall for sure. At least one of those three upgrades did find the correct previous library, which was a surprise for me.

There seem to be quite a few people reporting problems that are fixed by restoring a backup, and reporting issues that are fixed by selecting the correct PacakageInstaller.exe, so I don't think my installations are unique.

dmast · « **Reply #11 on:** August 10, 2018, 01:09:51 pm »

For what its worth, I am having the exact same problem, described by RoderickGI (multiple Media Center installs, trying to now load a fresh MC24 NOT in C drive). Everything works except, Library restore does not restore my settings.

RoderickGI mentioned "manually update Windows so that only the latest version has any file associations." Briefly, how do I do that?

dmast · « **Reply #12 on:** August 10, 2018, 02:14:46 pm »

OK, I sorted it out. I tried updating the preferences, but wasn't quite sure if I was doing it correctly, and it didn't work. So, I deleted all old installs of MC, including registry entries, then installed MC24 fresh, where I wanted it. Turns out that the most recent library backups still didn't load, but I was able to load one about 6 days old. So, I am good to go.

RoderickGI · « **Reply #13 on:** August 10, 2018, 07:58:13 pm »

For future reference, and if you want to check the file associations/default apps in Windows 10.

Windows 10 Start >Settings > Apps > Default apps > Choose default apps by file type.

dmast · « **Reply #14 on:** August 12, 2018, 03:52:30 pm »

Thanks RoderickGI!

Spike1000 · « **Reply #15 on:** August 13, 2018, 02:54:32 am »

Quote from: Hendrik on April 24, 2018, 01:50:34 am

- Settings are stored on a per-user basis, so if you need to install using an entirely different user account (because yours isn't an Admin), migration won't find its things

This is a bigger deal than it sounds and should be made more clear in the Wiki and during the upgrade process. MC (or anything else for that matter) shouldn't be run under a admin user. It's poor practice. Best practice it use the principle of 'least privilege'; ie run as an ordinary user and enter admin credentials/accept UAC prompts when needed (eg during an upgrade).

It would be really handy if this was (ideally) dealt with seamlessly or at least detected at upgrade time and a box popped up saying please use a backup to ensure all settings are migrated. . .

Spike

RoderickGI · « **Reply #16 on:** August 13, 2018, 06:09:19 pm »

Quote from: Spike1000 on August 13, 2018, 02:54:32 am

It would be really handy if this was (ideally) dealt with seamlessly or at least detected at upgrade time and a box popped up saying please use a backup to ensure all settings are migrated. . .

It is for me, and most users I believe.

I run my HTPC using a normal user account, and install all MC updates with the same account. UAC prompts as required.

Installing under an Admin account, then running under a different normal account makes no sense at all.

Spike1000 · « **Reply #17 on:** August 14, 2018, 02:23:47 am »

Quote from: RoderickGI on August 13, 2018, 06:09:19 pm

Installing under an Admin account, then running under a different normal account makes no sense at all.

Indeed that's silly. You should install and run under an ordinary account.

Maybe the need to restore settings when an upgrade is done when MC is running as an ordinary user doesn't affect everyone in the same way. I see it every year when I upgrade but I now routinely use the backup and restore method. It caught me out first time and I worked around it but my concern is that some people may lose some customisation on up upgrade and not appreciate that's not normal and it can be avoided.

Spikel

jeh14 · « **Reply #18 on:** August 20, 2018, 01:40:00 am »

I don't think I've ever had a problem with a MC upgrade not retaining my library info.

I have, however, never (in my recollection) seen MC retain any significant subset of my settings.

With every new major version of MC I have to change my directory and file name settings, my ripping settings, my... about 80 or 90% of everything in the entire Tools | Options tree.

(Is this thread the best place to discuss this, or should I start a new thread?)

JimH · « **Reply #19 on:** August 20, 2018, 02:49:56 am »

If it fails, backup in your old version, restore in your new version and read carefully when you do.

jeh14 · « **Reply #20 on:** August 27, 2018, 09:53:24 pm »

Quote from: JimH on August 20, 2018, 02:49:56 am

If it fails, backup in your old version, restore in your new version and read carefully when you do.

Worked like a charm! Thanks!!! It even kept my various "scheduler" settings (which I have set to record various radio shows' net feeds).

INTERACT FORUM

Author Topic: MC24 upgrade did not retain my library info. (Read 4224 times)