COM Server warning

Blake · Post by **Blake** » Thu Sep 27, 2007 9:38 pm

I get this error on most occasions when I close MM:

I know it probably isn't something to do directly with MM but any hints to stop it happening would be useful.

P.S. Things I have running with MM are MiniLyrics (+embedder) and Last.FM client.

Guest · Post by **Guest** » Fri Sep 28, 2007 12:58 am

I get the same message everytime. I'm also running Last FM.

eadlist · Post by **eadlist** » Wed Apr 02, 2008 10:03 am

I am also consistently getting the same warning. I am running MM 3.0.3.1048 in Vista with the default install (no other scripts or plugins). I've tried closing all programs (including all those in Process Explorer) and still get the message.

abcdefghi · Post by **abcdefghi** » Sat May 03, 2008 9:46 am

It would be nice to have a response from the staff that this problem has been received and any possible fix.

Guest_2 · Post by **Guest_2** » Sun Nov 16, 2008 9:59 am

I get this warning while I am running my "Now Playing" script for messenger.

Melloware · Post by **Melloware** » Tue Nov 18, 2008 10:36 pm

This is a known issue to the MM team. I have the same problem with my application iMonkey . It is whenever an out of process COM object is controlling MM and you close it you get this warning. Luckily I am able to circumvent this Warning with some tricky Windows API code that looks for the presence of this warning and closes it automagically. So my users only see this warning briefly flash on the screen if at all when they close MM or iMonkey.

rovingcowboy · Post by **rovingcowboy** » Wed Nov 19, 2008 9:24 am

yes they know about this as said by melloware, i don't program so i found that it is easier to make the item close by using an tweak program that has the option to close hung programs, so that is another option to use besides fnding the offending plugin or script and removing it.
which most the time i seen is one of the online searching scripts.
not sure which one off hand only that it has been posted before in the forum.

Post by **Peke** » Wed Nov 19, 2008 7:52 pm

As Melloware said it is known issue due the fact that App which uses COM Access to MM is not integrated correctly (not blaming the third party developers) due the fact that there is no real MediaMonkey SDK for both Plugins and external applications which uses MediaMonkey Automatization Server (COM) to get information from MediaMonkey and do not close COM object connection after information is received nor correctly detect MediaMonkey Start/Shutdown (again not blaming the third party developers) again due the lack of information.

Hopefully something will change after MM 3.1 gets out as some things can be more clearly explained on already working Scripts/plugins.

spacefish · Post by **spacefish** » Thu Nov 20, 2008 10:06 am

This also happens with the Now Playing Vista Sidebar Gadget. Looking forward to when MM can address/affect this directly.

nohitter151 · Post by **nohitter151** » Thu Nov 20, 2008 10:09 am

It happens with pretty much every app I've seen that can interface with MM. The vista sidebar gadget, the melloware app, any instant messenger plugins, etc.

Post by **Peke** » Thu Nov 20, 2008 8:02 pm

Not all O:)

I think I must update WIKI after MM 3.1 beta release. I already promised few people.

Sandra89 · Post by **Sandra89** » Thu Aug 25, 2011 2:35 am

Good idea..)) It's time for me to update WIKI too))

COM Server warning

COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning

Re: COM Server warning