The Mezzmo service doesn't start automatically

[buckyschwartz]

I'm running the latest version of Mezzmo (4.1.3.0) on Windows Server 12 R2.

The Mezzmo service doesn't start automatically when my server is rebooted. I can start the service manually and everything works just fine.

In Windows Services, I've tried setting the Startup Type to both Automatic or Automatic (Delayed Start) and neither of those settings made the Mezzmo service start automatically.

Ian Schwartz
Ottawa, Canada

[Paul]

Hi Ian,

Sounds like there is another service or program conflicting with Mezzmo server at start up. We'll know more if we see a set of logs. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and stop your Mezzmo server. Reboot your computer, When Mezzmo server does not start up, then exit Mezzmo app (if running) and zip up all the logs and email them to us at support [at] conceiva [dot] com.

[buckyschwartz]

I've tried emailing those logs to Conceiva Support and the messages got bounced, so I'm giving uploading them here a try. Please let me know if this is sufficient.

Happy New Year...Ian

[Paul]

Thanks for the logs. They show that Mezzmo server is not even starting up at all. This suggests that something on your computer is stopping the Mezzmo server Windows service from starting up. I guess it's another Windows service that is very slow to start up.

[buckyschwartz]

Thanks for the logs. They show that Mezzmo server is not even starting up at all. This suggests that something on your computer is stopping the Mezzmo server Windows service from starting up. I guess it's another Windows service that is very slow to start up.

That doesn't give me much to go on. Should I expect a more in-depth reply? A solution?

Ian

[Paul]

Hi Ian,

Assuming you have the Mezzmo Windows service set to 'Automatic' and logging turned on, then the logs show that the Mezzmo Windows service is not even getting started. Windows OS starts Windows services when you start your computer so this will be something to do with your current Windows configuration. You can try disabling some other Windows services listed in the Services window to try to isolate the Windows service that is taking so long to start. If no success, let us know and we'll help further.

[ftanner]

He might also try looking in the Windows Applications Event Log and see if there are any warnings or errors there regarding Mezzmo. Alot of times startup conflicts will show up there.

[Dion]

In Windows Services, I've tried setting the Startup Type to both Automatic or Automatic (Delayed Start) and neither of those settings made the Mezzmo service start automatically.

For what its worth don't put it on Automatic Delay. Will take it 2 minutes to startup after boot.

[wrnoof]

I know this is a bit late, but I am having a very similar problem. Mezzmo service does not start when powering up the PC. It will start if, once manually started, I am rebooting without powering down. I switched the Mezzmo media server setting to console application and, now, the problem went away whether rebooting or powering up. I was once told the difference between running as a service vs. console application, but have long since forgotten. Not sure it makes any difference.
Bob

[Peter]

When running as a service the server starts when the PC starts without requiring you to login so this means the server can start earlier before network interfaces have been initialized. Setting the service to run as Automatic (Delayed) can help to start the server by editing the properties of the service in Windows services.

[jasonhille]

In my case, I had 2 services attempting to run from one instance of Mezzmo Pro. I have a custom server name for my media library which generates a service with that name. I also had the default service, named Mezzmo (default server name). Both were trying to run automatically at startup and conflicting because there is only one instance of Mezzmo.exe running. There are 2 fixes. Once, simply disable one of the services. In my cause I disabled the default service, restarted my PC to test if my custom server name/service would startup automatically, and it did. Alternatively, you could delete the service you don't want/need and restart. Run your registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es. Export the ..\services folder as a backup. Find the service name you don't need/want and delete the folder. Restart your PC to test if the other service starts automatically.