Gravatar for

Question by aga, Jan 19, 2016 9:14 AM

CES Service in stopped state


I've noticed that sometimes after my CES server is restarted the CES service fails to start automatically but all other services (RabbitMQ and Search API) startup fine.

I see these entries in the even log but I do not see any anything in the CES logs that indicate why it failed to start.

Event Log:

The Coveo Enterprise Search 7 x64 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

A timeout was reached (30000 milliseconds) while waiting for the Coveo Enterprise Search 7 x64 service to connect.

Any hints on how to debug this?


Gravatar for

Comment by georgechang, Jan 25, 2016 12:20 PM

Just wanted to comment to save this thread since I'm having the exact same issue.

1 Reply
Gravatar for

Answer by Jean-François L'Heureux, Jan 19, 2016 12:02 PM

This message seems to be logged by the Windows Services manager who starts the services at boot time. It seems that the CES service takes more than 30 seconds to start on your machine. Common reasons the CES service can be slow to start:

Gravatar for

Comment by aga, Jan 19, 2016 12:09 PM

Jeff, in my systems log there are no matches to "ConfigObjectCache" or "swapping to disk".

My issue is not that it's taking a while to start, but the fact that CES just doesnt start at all. I'm trying to figure out why it isn't starting automatically. I just posted the only error I see in the windows event log. There are no errors in the CES logs either

Gravatar for

Comment by Jean-François L'Heureux, Jan 19, 2016 12:13 PM

Then, I really don't know…

Maybe the CES service needs another service to be started before attempting to start. Something related to network maybe… You might want to set the service startup type to Automatic (Delayed Start) and give it a try.

Ask a question