Podcasts suddenly not updating...

[Kilmatead]

Just this evening, all podcast update requests error out with:



A forum search turned up this thread, however it is related to the beta testing, and I am using (the old-but-trustworthy) 3.0.6.1190.

What's obscure is that it worked fine this morning, and I made no changes (none whatsoever, it wasn't even used) to MM.

What did occur though, was Windows Update decided to give me IE8 (as if I would actually use it), and the new Office 2007 SP2 update, which I vaguely remember asking if I wanted Outlook (Office version, not express) to commandeer RSS feeds... though I suspect IE8 may be more to culprit, as I recall MM funnels through it distastefully for worldly access from time to time...

Any notions?

This affects all podcast update requests, either specific ones, or "Update All" - though Update All does not visibly display the error, it just dies ignominiously.

(Vista x64)

[nohitter151]

Its related to the upgrade to IE8. The bug has already been fixed in the latest beta version.

[Kilmatead]

The bug has already been fixed in the latest beta version.

Which suggests I ought to update to the beta... I was rather waiting for the proper release, as I recall it (3.1) fiddles with the database format or something, and I hoped to avoid messing with what-ain't-broke.

Could I just remove IE8 instead, or does the new MM build (whenever it goes public) rely upon it over IE7? Or, perchance, is the latest beta acceptably harmless (regarding the DB change)?

I've been a bit out of the loop for these things of late...

[nohitter151]

The database is automatically updated when you run MM3.1 for the first time, and once it has been changed it is no longer backwards compatible with previous MM versions. However, simply making a backup of the MM.DB file prior to the upgrade should be sufficient to protect you should you decide you need to go back to 3.0.

In terms of 3.1 - it is actually no longer a beta and is in Release candidate testing, this means its quite stable and nearly ready for a release.

I honestly don't know how difficult downgrading internet explorer will be, so that is an option if its possible to do somehow. However, there isn't much risk in upgrading to 3.1 (at least in my eyes), since backing up the database is a sure way to protect yourself even if something goes wrong for you in 3.1.

[Kilmatead]

Fair enough. Cheers.

"Downgrading IE" is exceptionally easy when one uses image backups.

I suppose my concern pertaining to the DB was that I keep it on an external drive, and was unsure if the new installer would be intelligent enough to cope with a modified .ini file, installing over the old MM (which tends to be frowned upon with betas)...