SageMymovies API failed - Log Needed!

[seaverd]

I have been following this thread as I have not upgraded Mymovies from version 3.18. After reading this thread, I saw that some people had luck with version 4.02 of My movies collection manager for windows 7 64 bit. So I went to mymovies website to see if they had an archived version available for download, since current version is 4.03. When I could not find it, Brian sent me an email saying he would look into it. I am reluctant to make the move to 4.03 as my system works (can't access mymovies any more but the automatic folder monitoring is keeping things working).

Brian indicated that he would need a log from someone. Here is the link for how to collect a mymovies log:

http://code.google.com/p/sagemediama...portingAndLogs

Can someone with this issue please capture a log and send it to: support@mymovies.dk

Also, please post here so I can follow up with Brian.

Thanks,

Dan

[panteragstk]

I can make it easier for you and upload 4.02 if you need it. As long as the database is backward compatible with 4.03, if not the api failing can be a few other things. Let me know if you want 4.02 or not.

[PLUCKYHD]

I am the one who requested the log from Brian. I will need the log from you since you are the one having the issue. I am not aware of anything in 4.03 that should break it but can't remember it's been over a year since I even looked at the SMM code.

[seaverd]

Plucky,

You have been a great help in the past, and in reading your posts I saw that you were no longer using this plugin and were not going to update it. So along those lines I asked Brian for version 4.02 since members on this forum reported that it worked and that the current version did not. I am still on 3.18 so I have no logs to provide, which is why I was posting for the several members on this board who reported the API failure to provide a log. The reason I have not upgraded is 3.18 kind of works since I have folder monitoring going on. If you are willing to help resolve the issue, I would be willing to try the upgrade to 4.03 in order to generate the logs.

[panteragstk]

For those that need 4.02 here it is.

[Ender]

I am as of present not having issues with SMM, and Collection Management software ver 4.03. All data appears to transfer to sage properly.

It would, to my humble opinion be, that since you are still on 3.18, and as discussed here that it is plainly a my movies problem, and an upgrade is in order.

One could test this, just image your boot drive, and install, if anything goes sideways, just restore the prior image.

[panteragstk]

If you are still on 3.18 then that may be your issue since they did some database changes that are no longer compatible with that version. AFAIK you have to be on 4.02 or higher to get database updates. I have no clue if that has anything to do with the api failing.