Copying settings from MM4 leads to error and MM5 crashing [#17193]

[Snofru]

When I install 2281 anew and try to copy my settings from MM4 I get the attached error and afterwards MM5 doesn't really start and has to be killed by task manager.



MM4 and MM5 are installed as portable and both are used in german language. Installation of 2281 without transfer from MM4 works without issue.

[Ludek]

Hi, analyzing the crash log 340A0000 and I see EArgumentException "Invalid characters in path." when copying the MM4 database (MM.DB) to the MM5 location (as MM5.DB)

Unortunatelly I don't see the exact MM4 db location in the log, I'll add more debug messages to see more in the next build.
Do you know your MM4 database location? Did you specify a custom DB path in MediaMonkey.ini ?

[Ludek]

Could you please temporarily replace your current MediaMonkeyEngine.exe from build 2281 by this one: https://www.dropbox.com/t/jkviDDt8S0Kes8bN
and generate/submit new crash log?

Thanks!

[Snofru]

My MM.DB path is D:\MediaMonkey 4\MediaMonkey\Portable.

The alternative MediaMonkeyEngine.exe unfortunately didn't change anything. Another error with log ID 340A0000 was sent.

A detail I haven't mentioned so far: After sending the error log I always get another message box saying: "Application error. Invalid characters in path. Would you like to restart MediaMonkey in Safe mode?" None of the 3 options I get here do help though, MM5 always freezes.

And I should also mention that there were no such problems with version 2276.

If I can be of further help, please ask.

[Ludek]

Thank you, I have the new crash log here, it shows the last 200 lines of debug log, but unfortunatelly I still don't see the paths there to see why it is throwing "Invalid characters in path" exception while copying the MM4 database :-/

Could you please generate standard debug log using DbgView (item 4b here: viewtopic.php?f=30&t=86643 ) with DbgView started prior to MM5 and send me link to the debug log file (via private message or eSupport ticket).
Please keep the MediaMonkeyEngine.exe that I shared via DropBox when generating the new log.

Thanks!

[Snofru]

Log is sent to you via private message.

I have played around a bit and I found out that after trying to import from MM4, getting the error and killing MM5 by the Task-Manager and then trying again it simply runs through: Without any further issue the database is imported. So it is only a first-run-issue...

[Ludek]

Thank you for the debug log and info:
Could you please generate one more debug log using this MediaMonkeyEngine.exe : https://www.dropbox.com/s/xgbvryx4onzge ... e.exe?dl=0
This should finally show the cause of this issue.


Thanks!

[Snofru]

OK, log with the new .exe has been sent with the same ID as before: 340A0000.

[Ludek]

Thank you, but I would need to see the standard debug log (generated using DbgView started prior MM5 start) like you sent before (item 4b here: viewtopic.php?f=30&t=86643 )
Otherwise I don't see all the needed debug messages and still don't see the cause.

Mostly the info is presented within the crash log itself, but not in this case (where I need the standard debug log to see more).
Thanks for your help!

The issue is being tracked in Mantis as https://www.ventismedia.com/mantis/view.php?id=17193

[Snofru]

OK, I have PMed you the link to the Debugview log.

[Ludek]

Thank you,
could you please send me also your
D:\MediaMonkey 4\MediaMonkey\Portable\MediaMonkey.ini
and
C:\Users\<your user name>\AppData\Roaming\MediaMonkey\MediaMonkey.ini
It seems that you specified DBName=D:\MediaMonkey 4\MediaMonkey\MediaMonkey.exe in the MediaMonkey.ini in the AppData folder ?

i.e. MM5 tries to copy MediaMonkey.exe instead of the database (to be confirmed from the INI files).

[Ludek]

OK, skip that.

Traversing the code again (not mine code) I found that if MM5 does not find MM4 installed in standard location then it goes through all links on you desktop to find a link to MediaMonkey.exe , and there must be a broken link that is causing this strange issue.

Could you confirm that you have more than one link to MediaMonkey.exe on your desktop and what values in the links' target are ?

[Ludek]

By the link target I mean this Target value when you right-click the shortcut on the Desktop > Properties , see: https://www.dropbox.com/s/yzclyp8ezrlrt ... 4.png?dl=0
There are multiple MediaMonkey shortcut on your Desktop, right? I would need to know them all. Feel free to PM or share it here.

[Snofru]

Yes, I have 2 links for MediaMonkey on the desktop, one for MM4 and one for MM5.

MM4: Target: "D:\MediaMonkey 4\MediaMonkey\MediaMonkey.exe"; Execute in: "D:\MediaMonkey 4\MediaMonkey"

MM5: Target: "D:\MediaMonkey 5\MediaMonkey.exe"; Execute in: "D:\MediaMonkey 5"

I don't see anything special here. Maybe that MM4 portable is installed in a "MediaMonkey 4" subfolder while MM5 portable is directly in D:

Added later: I found that in D:\MediaMonkey 4\MediaMonkey\Portable I have an old MM5.DB (from July 2020) in addition to MM.DB. Not sure where this comes from, probably from myself saving the DB in the wrong place . I can try to delete it and see if the installation runs through this time if you like.

[Snofru]

OK, I have removed the MM5.DB in the MM4 folder but I still get the same crash as before.

Then I have found a backup folder of MM4 also at D: which I removed and it still crashes.