Also if you look at your firewall rules makes sure you don't see the odd mediamonkey_autoconf ones. Remove those and go add mediamonkey.exe manually. I do believe you have to do it everytime you update MediaMonkey as the EXE changes and the firewall is smart enough to know that it's not the same EXE.

The MediaMonkey_autoconf* rules are rules added by MM installer so that you don't need to approve the access manually,
details here:
http://www.ventismedia.com/mantis/view. ... 261#c45392
After MM re-install the MM rules are deleted and created again -- I wonder why this isn't working for you??

Could you write down how the rules looks like after MM re-install?
If you go to Windows Firewall > Advanced settings
You should be able to see the rule details like this:
https://www.dropbox.com/s/q834yf4g4eaxn ... f.png?dl=0
Could you please attach screenshot of the tabs General, Advanced, Programs and Services ?

Thanks!

It is also strange that you need to stop the service manually before installing update as the installer does close the service before re-installing automatically ( http://www.ventismedia.com/mantis/view.php?id=13410 )

When you upgrade mediamonkey, you will need to Stop the service update mediamonkey, start the service, go remove mediamonkey from firewall rules then re-add it. I have this problem every time I update but it takes only like 10 15 minutes to resolve.

Server 2012 R2
Also it's normal for the service to stop when you open MediaMonkey as MediaMonkey.exe takes over for the service EXE and then when you close MediaMonkey it restarts the service.

I also have the mediamonkeyservice.exe in my firewall rules but I really think it only calls an instance of mediamonkey.exe

Double checked and and it's only mediamonkey.exe that needs to be in firewall rules (using netstat - ano) it's the only PID out of the two that is listening on any ports. So the MedieMonkeyService.exe only calls mediamonkey.exe. Also if you look at your firewall rules makes sure you don't see the odd mediamonkey_autoconf ones. Remove those and go add mediamonkey.exe manually. I do believe you have to do it everytime you update MediaMonkey as the EXE changes and the firewall is smart enough to know that it's not the same EXE. Would be to easy to bypass firewalls if they only went by program name.

I've been driven barmy with a similar problem. Set up MM on Server 2012 Essentials (domain controller, although I'm not using domain PCs, but am using it for backup). Music is on a share on the 2012 server, so is locally accessible. Set up DNLA - visible to PCs - for a day. Try it as a service, service is running, no library visible on network. After a while the libraby disappears. Reboot - no library. Try all combinations and permutations with/without MM running/as a service. Create a new DNLA instance - now visible - for a day. Then go back to many reboots, removal/recreation of DNLA instances with varying success.

A WM sharing instance on the same box behaves impeccably.

Finally turned of the Windows Firewall at Domain level, and all is working, even with MM running as a service. I will play with firewall rules later and may report back later, but its taken me months to get this far! I don't understand why the firewall would be the cause as it seems to work initially for a while then disappear...

I'm using MM as it seems to be able to work better with Sonos (if you use reduced playlists for random play, as Sonos can't cope with the size of my music collection).

Just answered my own question. I needed to restart the computer!

I have build 4.1.1.1703 & have just started using MM Server as a service. MM shows this is running but the task manager shows it stopped & I can't restart it (access denied). I am Administrator using Windows7.Any help would be appreciated.

I just tried this. Started debug and wasn't getting anything. Started mmw and played a vid and got lots of info. Stopped the vid and file/end MMW. After a few seconds there was no more input.

I then tried to find with MMA ... no input to debugview.

Will send the file to support. Stick a fork in it .. it's dead

Edited: A support ticket has been created and log attached.

I will give this a try ... but there is so much running ...

Is the service a 'debug' version?

Have you tried running DBGView to see if it captures anything (I haven't tried this)?

Yes. I just restarted my box and service shows as running. MMA (haven't tried sony but will and edit this post) can not find the server. MMA does see my daughters wmp, our NAS and my desktop Vuse servers.

Is there any way to capture a log for the service? Or test the service?

Is this repeatable after Windows restart?

I turned off my MMW (1658) and went into the living room to watch some tv (dlna) and my Sony can't connect to the server now. I tried with MMA (167) and it couldn't find the server either. Start MMW back up and both sony and MMA find it right away.

What ever was changed (a different thread talked about that) has made the service undiscoverable again.

very big thanks!

mediamonkey service now running the first time! and this without any problems! great job!

Thanks Ludek .. I'll look out for a fix

Eric

Really? I am using 1658 and the service does start on boot of computer. Then start MMW and it stops (as i have been told it should). Then shut down MMW and the service starts again.

Actually I re-tested it and the service really no longer starts server in recent builds!

To be fixed as http://www.ventismedia.com/mantis/view.php?id=11303 in build 1660.

Thank you for reporting!