I've tried many things to get this script to work but I get failures and\or errors each step of the way.

Can anyone recomend a way to backup and import autoplaylists that doesn't require a degree an physics to get it working?
:(

[quote="MusicBringer"]...I suppose you are running Monkey as a Administrator?[/quote]
Is that required? Running Monkey as a Administrator?

...I suppose you are running Monkey as a Administrator?

No, it means that the database is locked and therefore the script cannot access it directly. I don't know why it's locked or how you can unlock it though. Have you tried restarting your computer?

i believe that is an error that is saying there is an issue on line # and Character # of which the script author will have to fix or help you fix.

and until that issue is fixed it locked your database?

that is what i read it to be but i could be misreading it, so its still better to check with the script's author.

8)

I'm getting the following error, and I'm stumped. Has anybody figured out how to remedy this? I can't run Backup 5.8 because of this. I'm running MediaMonkey 4.0.6.1501 on Windows 7 Pro 64-bit.
[img]http://imageshack.us/a/img18/9681/backupplaylists.png[/img]

Hi Everyone,

I'm having trouble retrieving my Playlists using this script. I've just backed up my Library and Playlists using trixmoto's Backup and Playlist Backup scripts.
In the past I've had no problem backing up/restoring everything using these to the same PC, but am not trying to restore my most recent backup (WinXP) onto my new Win7 laptop and having difficulty. This difficulty is compounded by the fact that I've moved Library location from a dedicated USB HDD onto the Public folder of my Laptop, so paths are now different.

Anyway, I initially struggled to backup the main MM DB, scripts and *.ini file, but copying and pasting manually into the MM install directory has solved this (confirmed as installed Scripts now display under the Tools menu). However, this has led to a problem when executing the 'Import' function of the BackupPlaylists script from within MM - I'm getting the following errors:

[img]http://5img.com/img37/7342/97mmerror.png[/img]

I'm relying on somebody far more familiar with the MM database sctructures to point me in the right direction and wondering if anybody knows of a possible fix and/or cause for this error, or possibly a manual way round it?

Btw I don't have any Auto-Playlists configured, the Backup just contains standard playlists but I am keen to restore these as there are quite a number of them, each containing alot of tracks, making 'starting from scratch' an unenviable prospect!

Any support that can be offered will be much appreciated!

Thanks in Advance Guys.

Leigh

@Kiwichick,
But then will the autoplaylists already be in the copy! :)

If it is a copy of the same database then you should be fine.

"you cannot import these criteria into another database as the IDs will not match"

What if my "other database" is copy of the original database (on the same computer, just in another folder)? Will the IDs still be an issue? Will I have my autoplaylists? Cheers.

[quote="peterH"]I'm trying to install this into MM3 v3.2.2.1300 but I'm getting a "Product Installation Error". Any ideas?

Also tried the older v2.1 and got the same thing.

Thanks . :)[/quote]
http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=59

I'm trying to install this into MM3 v3.2.2.1300 but I'm getting a "Product Installation Error". Any ideas?

Also tried the older v2.1 and got the same thing.

Thanks . :)

If anything needed to explain/document (I raised scripting documentation issues to higher for MM 4.0+) I'll be glad to help

New version (2.2) is now available to download from my website. Changes include...

- Added update server to installation package
- Removed old MM2 code
- Fixed problems caused by apostrophes

Thanks, you are of course correct. My script is primarily designed for importing back into the same library, but if it was imported into a different library then it wouldn't really work. As you say in your thread, this would be too complex to try and fix as it's wholey undocumented.