Note: fixed in 1288: http://www.ventismedia.com/mantis/view.php?id=6160

-Rusty

Doesn't that result in the same thing?

Same problem on Windows 7, 64bit

[quote="ZeusII"]Hi!

Got this problem in my last reinstall (or at least I noticed it). I'm also using vista x64.

solved it by enterig component services: c:\windows\System32\comexp.msc

then go to component services > computers > my computer > dcom config

find mediamonkey entry, right click propierties

go to security tab and add your user to "launch and activation" and "configuration" permissions.

after doing this, no more errors logged.[/quote]

My concern is with network restrictions that may be applied by adding a User to the "launch and activation" and "configuration".

The simple way to get to Component Services, type comexp.msc in the run command press enter.

I solved the issue by going to 'Component Services > computers > My Computer > DCOM Config > Mediamonkey (Right Click) > Properties > Security Tab. Then select 'Use Default' for all three options.

Moatmai,

I haven't seen this either. If you're able to reproduce, can you generate a debug log as described at:
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341

Thanks.

-Rusty

Interesting. I haven't experienced this problem in quite a few beta builds. And I have been watching for it.
I am running Windows 7 64-bit with build 1287

I'm currently experiencing this issue with Windows 7, 32-Bit, Build 3.20.1287...

Uninstalling, then reinstalling MediaMonkey is quite a chore.

I get this same log event, multiple times. I can also hear Vista making audio sounds, as though some USB device has been detected (initially I thought that what it was), however the logs clearly stating DCOM 7DB2DA7A-8F3D-4329-990C-32E15C849F00.
The odd thing is, this happens even when MM isnt running, and seems quite intermittent.

I'm running 32bit vista on a macbook pro. MM 3.1.1.1261

Oh, I see from this forum thread that the most recent releases only address the Amazon autotag issue.
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=42218&st=0&sk=t&sd=a

I just downloaded 3.1.1.1261 (RC-3) and it appears that this hasn't been fixed. I guess I haven't seen the changelog yet either. Maybe the fix isn't in this release?

I just noticed the same thing in my event viewer.... doesn't seem to hurt anything though

been a media monkey user for many years, love it

Very nice! Thank you.

I created http://www.ventismedia.com/mantis/view.php?id=5826 so that it get fixed.

[quote="ZeusII"]Hi!

Got this problem in my last reinstall (or at least I noticed it). I'm also using vista x64.

solved it by enterig component services: c:\windows\System32\comexp.msc

then go to component services > computers > my computer > dcom config

find mediamonkey entry, right click propierties

go to security tab and add your user to "launch and activation" and "configuration" permissions.

after doing this, no more errors logged.[/quote]


Yeah, that is exactly what I do. Unfortunately you have to re-do it every time that you install a new version of MediaMonkey or update it. It started happening for me with the 3.1 beta and hasn't stopped. Although I had never seen it with 3.0.

There is one thing we have noticed regarding Vista and Win 7 x64 and that is, if MediaMonkey is installed using Windows XP Compatibility Mode everything is gets in its place and MediaMonkey Automatization COM Server is registered correctly.

Hi!

Got this problem in my last reinstall (or at least I noticed it). I'm also using vista x64.

solved it by enterig component services: c:\windows\System32\comexp.msc

then go to component services > computers > my computer > dcom config

find mediamonkey entry, right click propierties

go to security tab and add your user to "launch and activation" and "configuration" permissions.

after doing this, no more errors logged.