MediaMonkey forum

Hi:

The error message below staring appearing today.
I am running Windows 10 Pro. Version 1903
Could somebody help me fix the problem?
Thanks.

Which version of MediaMonkey are you using?

Version 4.1.24.1883

Capture this in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... p?f=1&t=69

Hi:
My apologies for not responding earlier.
The problem resolved on its own.
If it shows up again, I will submit a support ticket.

Thanks for your help.

Hi:

This issues has come up again:



I tried to capture this in a debug log (step 4b) and attach the log to a Support Ticket but I am unable to capture the log. I am just not computer savvy enough despite following the instructions. Is there another way to provide a solution?

I am currently using MM version 4.1.26.1896

Thanks for your help.

It's really simple (although it may not seem so):
1) Download and install the debug version of MediaMonkey like any update of MediaMonkey
2) Download and run DBGView
3) Reproduce the problem
4) Save the log in DBGView and attach that to a Support Ticket

https://www.mediamonkey.com/forum/viewt ... p?f=1&t=69

I'm sure it is quite simple, but this online posted is not sure what needs to be done.

So here is what I have done:
I execute DbgView, running DbgView as administrator
I opened and closed MM. After MM is closed the Access violation error pops up.
I close the error message pop up.

From what I understand, I am suppose to see logs being generated in DbgView. I do not see any logs being generated.
So I go to file, save as in DbgView and save file as DbgView Data (*log)
File is save to my desktop. When I open file, (file opens in notepad), the file is empty. File size is 0 bytes.
Is this the file that needs to be sent to your help desk?

Most don't need to run DBGView as Administrator. Did you install the debug version of MediaMonkey? That is required as the regular version doesn't generate the logs in DBGView.

Ah, I didn't install the debug version MM.

So, I'm pleaseed to let you know DbgView created and automatically emailed log report to your help desk. I assume your help desk will email me with a solution.

Thanks for your help.

No, only if you attach a debug log to a Support Ticket will there be feedback.

MediaMonkey Support was finally provided a fix:

1) Run Registry Editor (press WinKey + type "regedit")
2) Delete the following key:
Computer\HKEY_CURRENT_USER\Software\MediaMonkey\Interface\V4\

Thanks for all your help.

I'm having the same issue with the Access violation at address...when I click on a song. It used to only happen occasionally but with one of the recent updates it seems to occur every other time I double click a track to play. This happens on new and old tracks. It rarely does it when auto-playing through tracks or shuffling, but I've noticed it happen a couple times.

I've already deleted Computer\HKEY_CURRENT_USER\Software\MediaMonkey\Interface\V4\
This seemed to work for a few days, then it got really bad again today. Every track I clicked gave me the access error and one kept repeating. Because of that (and that deleting Interface\V4 had inadvertently deleted some track info) I went ahead and reinstalled Media Monkey again. Since then I've seen the error message once or twice already.

This problem is seemingly minor but very obnoxious now that its getting progressively worse. Is there a fix to this or no? I'd be happy to purchase Gold if that is shown to fix the issue somehow. Otherwise I feel like my days using MM are numbered. I've been a MM user for a long time too, so its a real shame.

Capture this with DBGView (step 4b) and attach the saved log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?p=69

Hi,
Deleting registry entry "HKEY_CURRENT_USER\Software\MediaMonkey\Interface\" do not influence in any way on files as that registry entry only saves UI elements like windows position, size, layout and etc. Can you please make screenshot (or take a picture with your phone) of screen showing the error and attach it in support ticket (same login info as for forum)?