Warning about upgrading to 4.02pr1

[jptheripper]

Did a clean install with the new mymovies 4.02pr1. Got an unfixable sagemymovies api failed

uninstalled and installed 4.01 and it worked perfectly, just a warning before anyone upgrades make sure you backup everything!

[PLUCKYHD]

Originally Posted by jptheripper

Did a clean install with the new mymovies 4.02pr1. Got an unfixable sagemymovies api failed

uninstalled and installed 4.01 and it worked perfectly, just a warning before anyone upgrades make sure you backup everything!

yeah did an upgrade today and looks like they once again made some database changes. I wouldn't hold your breath on them getting into SMM given my current time.

[panteragstk]

3.18 still works just fine for me.

[jptheripper]

I have been using 4.01 since it came out and it works great. Just dont use 4.02.

[CptKirk]

Just received this email from My Movies yesterday. Looks like they are pushing users to update to at least 4.02. Any chance that SMM might be updated to continue to work?

Software Update Required

Our records shows that you within the last month have been logged in with an outdated version of My Movies, specifically the product:

My Movies Collection Management 3.19 (Pre Release

Due to security changes in communication with our online service, our users is requested to update their user clients before June 1'st 2012. The software will continue to operate after this date, but will after this date no longer be able to load meta-data from our online service.

Users running My Movies for Windows Media Center or My Movies Collection Management 4.00 or 4.01 for Windows 7 is required to upgrade to version 4.02 or later.

Users running My Movies for Windows Media Center or My Movies Collection Management 3 for Windows Vista is required to upgrade to version 3.25 or later.

Users running My Movies for Windows Home Server 2011 is required to upgrade to version 2.10 or later.

Users running My Movies for Windows Home Server V1 is only required to upgrade if client PC's are upgraded to a version that requires a later version on their Home Server.

Users running My Movies 2 for Windows Media Center 2005 will for now not be required an update. However, we strongly recommend getting these systems upgraded to Windows 7.

Users running systems installed by a licensed professional My Movies installer will also not be required to update unless they are also signed into a user account, which is optional on these installations.

If you are in any way have problems with upgrading, or is unsure how to do this, please contact support@mymovies.dk where we are able to help you.

Notice! The latest versions of the My Movies product suite have it's internal "mymovies.xml" files encrypted. If you as a professional partner, or supplier of non-competitive software solutions rely on these files, you may contact us on installers@mymovies.dk, where we will be able to suggest optional alternatives.

The files were originally encrypted due to the fact that other software products were creating these files considered internal by My Movies, causing problems for My Movies installations. One of the softwares that until recently was using the "mymovies.xml" files is MediaBrowser, which have since changed their used format to "movie.xml". The encryption of the "mymovies.xml" files is known to have caused problems for users of both My Movies and MediaBrowser, and we have as of My Movies 4.03 Pre Release 4 added an option to store "movie.xml" files for use with MediaBrowser. This option will, as MediaBrowser is a partly paid-for competitive software require 500 contribution or purchased points, which equals $20 if purchased.

We are sorry for the inconvenience this upgrade requirement gives. Should you have any questions or concerns, let us know, and we will do what we can to help you.

Best regards,

Rasmus Johansen and Brian Binnerup
My Movies

[panteragstk]

That's odd. I haven't received any such notification.

[sm4284]

I received the same email

[PLUCKYHD]

That really sucks guys but not much I can do about it. I no longer even have the source code to SMM to even modify it. I can probably break open the existing jar. Due to personal reasons though I don't see time to do that in the near future.

[Ender]

Originally Posted by PLUCKYHD

That really sucks guys but not much I can do about it. I no longer even have the source code to SMM to even modify it. I can probably break open the existing jar. Due to personal reasons though I don't see time to do that in the near future.

Well that is unfortunate, oh well. I guess I will have to see if I can get the BMT/Diamond combo to produce as accurate meta data, and fan art as MyMovies did.

Tis not the end of the world, just makes it a bit more interesting, and knowing how I like to tweak things this should be an adventure.

[wjones]

I upgraded to 4.02 (dec 15th) following the mail from my movies.
After the client update install, it updated the DB automatically.

SMM still works fine.

Just my $0.2c!

Cheers

[Wified]

It appears that MyMovies on a WHSv1 install works fine with Collection Management 4.02. It's working fine for me.

But, if you try to upgrade your client's CM to 4.03, SMM on the WHS doesn't work (API failed).

It appears from the above posts that if you are running MyMovies on a Windows 7 server, instead of a WHS, CM 4.02 will break SMM.

Is this correct?

[panteragstk]

Originally Posted by wjones

I upgraded to 4.02 (dec 15th) following the mail from my movies.
After the client update install, it updated the DB automatically.

SMM still works fine.

Just my $0.2c!

Cheers

So you are using Collection management 4.02 and SMM is still working? Please clarify your post. This is a very important part of Sage so I really need to be sure it is working before I try anything else.

[Wified]

Originally Posted by panteragstk

So you are using Collection management 4.02 and SMM is still working?

I can confirm that this is working on my WHS install. I tried 4.03b3, and SMM API failed.

[wjones]

Originally Posted by panteragstk

So you are using Collection management 4.02 and SMM is still working? Please clarify your post. This is a very important part of Sage so I really need to be sure it is working before I try anything else.

Correct, I am using Collection management 4.02 on my Win7 PC in client only mode. When I installed this over the top of the old version (3.19), it upgraded the DB automatically.

The DB is hosted on my WHS v1 box and was installed via the standard WHS installer.

Not much more details I can give.

HTH

[PhilH]

I can also confirm that 4.02 does work. I have the Client on a Windows 7 machine.

I have WHS v1 with MyMovies 2.0.0.100.

I ran 4.02 & it asked to update the DB. I told it yes & it modified the DB. I added a movie & told SageTV to scan. A little bit later the movie showed up in SMM. Worked just like always..

Phil

[jptheripper]

really? so it only works with whs? crud.

[panteragstk]

From what they're saying it will work on the windows 7 client. If that is true then it should work just fine on a windows 7 server. The client is where most people have issues with the API failing. I guess I'll find out.

[SteveD]

Originally Posted by panteragstk

From what they're saying it will work on the windows 7 client. If that is true then it should work just fine on a windows 7 server. The client is where most people have issues with the API failing. I guess I'll find out.

I upgrade a windows 7 64 pro server with the database and 4 clients without any issues other than fighting with windows 7 pro not wanting to upgrade to SP1 which is a requirement for version 4.02.

[sm4284]

I can confirm that 4.02 works with no problems on my setup, windows 7 64bt server.

[Texas-Hansen]

I just ran into this same issue and 4.02 worked for my setup.. I upgraded MM Collection Management on my desktop to 4.02 and I have MM on my server which is a WHS v1. Sage MM seems to be working fine right now with this combination.

My only concern is that eventually we'll all have to upgrade to a higher version of MM on our clients and Sage MM will likely stop working. Hopefully, PluckyHD will find some time in the future to make changes that allow it to work as Sage MM is really an awesome product.