application throw error in 3200 beta

[Smith10]

Hello,

I accidentally posted this in the main help forum for MM. I understand that beta is a testing version and this may not be as critical. I am unfamiliar with testing, but wanted to try it anyways. I understand risks.

I have downloaded the 3200 beta version. I’m the one who reported previously on 12-22-25 that MM wan’t accessing OneDrive. I now can see my OneDrive, but as I am working in MM to get my new library created, I keep getting the following error:
<<
Application throw an exception Exception EAssertionFailed in module
MediaMonkeyEngine.exe at 012ADA50.
whenLoaded promise was acquired, but notifyLoaded was not called
(promise never finished)!
(C:\Sources\MediaMonkey2024_2_1\HTML5Monkey\BaseShared.pas,
line 5813).
Would you like to restart MediaMonkey in Safe mode?
Restart
Restart in Safe mode
Continue
>>
MM doesn’t actually do anything when I select any of the options. I have to go in to my Process Explorer and kill all MM-related items. I have also tried re-booting, but it still is happening today.

I have Windows 10 Ver 22H2.
Please advise.
Thank you.

Kimberley

[Peke]

Hi,
Can you replicate same behavior while using Clean portable MM 3200 installation?

NOTE: You can copy MM5.DB from your regular MM installation.

[Smith10]

Hello Peke,

Yes, today I was able to replicate the above error using a clean portable install on a USB drive.

I made sure I started the MM on the USB drive by right clicking (I also selected Run as Administrator). It did allow me to Sync my OneDrive this time. It completed that brief process before it threw the same error as above.

This time, when I selected the “continue” button it also came up with

Runtime Error 217 at 016ADA50

(So, I will say between your message and now, I also tried to uninstall the MM on my C drive (by using Windows ==> Apps==> Uninstall and then also deleted the MM folder under Program Files (I have an old .db file saved elsewhere), but I still got the same error rather quickly when I re-installed 3200 on the C drive. So, I guess I don't know how to make a clean install on the C drive...)

Does this provide any clues as to what is happening with the 3200 beta for me?

Thanks so much, Kimberley

[Peke]

Hi,
"Runtime Error 217" usually points to deeper issue with MM compatibility with other software/hardware on your system and can be basically anything including MM itself speifically trigger it on your system.

May I ask you to open support ticket, so that we can into more details.
Also make sure you are running Debug Version of MM Always and if it happens very quickly then creating full debug log using steps from https://www.mediamonkey.com/forum/viewtopic.php?t=86643 should not be to hard and you can ZIP ot to attach to Ticket.