The service did not respond to the start request in a timely fashion

[rkone 0]

I'm having problems using the service feature of emby server.  Most of the time I get the error in the title when trying to start the service.  If I keep trying, maybe on the 10th or so attempt it will finally work.  Because of this problem the service never runs on startup. It does seem to take a long time for a service to start, even when it does go.  Does no one else have this problem?

[FrostByte 5049]

Try starting it automatic delayed, but no I'm not having this problem and I'm running as a service

Edited July 2, 2015 by FrostByte

[Luke 37057]

if you grab the server log it might indicate why it took so long to start

 

http://emby.media/community/index.php?/topic/790-how-to-report-a-problem/

[jani 4]

I'm seeing this as well. Here's the log, and no, it's not truncated. I'm just on a little older PC with a 5400rpm disk.

 

My services timeout is set to the default 30s and the service is set to delayed start. Even if I try to start manually, the timeout is met. Windows' Event log says:

A timeout was reached (30000 milliseconds) while waiting for the Emby Server service to connect.
The Emby Server service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

As suggested for example here, shouldn't Emby be reporting back to the services manager that it's still alive and just a bit slow to start? I know I can increase the timeout for all services, but IMO that is not the correct fix.

Edited July 6, 2015 by jani