Hi,
I guess that Ludek can also agree, that it is our pleasure to work with users like you to make Win Win situation.

Happy Monkeying!

OK, success!

I can confirm, that the new MediaMonkeyEngine.exe works here without issue!

Thanks for the good cooperation!

OK, I got it finally.

This error was really well hidden deeply in the code, thanks for reporting!

Here is new MediaMonkeyEngine.exe that will work finally without a crash: https://www.dropbox.com/s/dbo4ym7r5mk7d ... e.exe?dl=0


Thanks again!

Note: Once you confirm that the issue is finally fixed then replace back the original EXE from 2281 (as this custom one isn't fully compatible with the UI part of 2281 and would throw error e.g. in List (by Album) view)

This issue is really curious, I am sorry to say that I need another debug log (generated using DbgView) with following MediaMonkeyEngine.exe : https://www.dropbox.com/s/bu8syty0vmk60 ... e.exe?dl=0
to understand from where it takes the unexpected values.

Thank you for your patience, I would really love to undestand this issue finally.

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.

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.

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.

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 ?

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).

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

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

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

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!

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...

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!