Serviio

Windows 7 didn't have this issue.
I upgraded to Win 10 and ~every third boot I get the message "Cannot connect to Serviio server, it does not seem to be running".
I had to revert to Win 7 for other reasons and the problem went away again. When I re-upgraded to Win 10 it is back.

I've reinstalled Java. Any other ideas?

Thanks, Joe

My guess is that Serviio Console is starting before the Server. If you start your PC, get the message and acknowledge it, and then wait a few minutes - can you then run Serviio Console?

If so, the simplest thing to do is to run Serviio Console manually only when you need it (it's not required for server operation, just configuration) - to do so, simply remove the Console shortcut from you Startup.

Nope, still gives the same message.
I had to manually start the service then the console.

Thanks, Joe

Ok. Can you please post a detailed log of the Server starting after a reboot and we can try and work out what's happening.

Well, it figures. It had been happening nearly every morning when I start my computer. Now that you ask for a log file it hasn't happened.

I'll post the logs next time it happens.
Thanks, Joe

Success!
I believe I have found the sequence to reproduce the issue.
I often exit Serviio when I want to play video games (right-click task bar icon 'exit serviio'). I did that last night and lo and behold I had the error again. I repeated that sequence just now with same result.

I end up with 2 files... the log plus a temporary '.1' copy of the previous log that shows the shutdown. I trimmed the '.1' file down and have attached both.
[I had to rename the file to upload]

Thanks, Joe

When you are rebooting is it really rebooting
Note that in Windows 10 - if you have fast startup turned on, which is the default, then the Shutdown button will perform a hybrid shut-down instead of a full shut-down. A hybrid shutdown is a variant of hibernation which, like awakening from sleep or full hibernation,does not restart any services (such as the Serviio server) upon rebooting. Hence after a fast restart" you will get this error, as the Serviio service has not been restarted as it would be after a cold (full) reboot.

So to overcome - firstly confirm that my suspicion above is correct (that it's not a full shutdown - test by selecting "Restart" rather than Shutdown, which will force a cold boot) and if correct either:

• Don't shut down Serviio when playing games ; or
• If you manually stop Serviio, you need to manually restart the Serviio service each time (using services.msc or the batch file that comes with Serviio - run as Administrator)
• Use "Restart" instead of Shutdown to force a cold-reboot whenever you have shut down Serviio; or
• Disable Fast Startup (Google is your friend).

Thanks, I did not know Windows 10 defaulted to Fast Startup. I didn't use hibernate in Win7 so thought it would be the same.

I'll probably disable it.

Thanks, Joe