Did you meet this issue before? When you try to launch the reporting service, it complains “The service did not respond in a timely fashion”. Usually I think RS is just a piece of cake but this time it seems to be a hard bone.
The reason this time is different is you have no places to check errors with the only exception of event viewer. In your RS log, no info has been dumped out yet because your RS has not started to work. In your event viewer, it only reminds this tedious statement “The service did not respond to the start or control request in a timely fashion.” whatever how many times you attempt to start your RS.
I searched around for solutions this morning. Seems below situation fits for most.
It is because of security upgrading.
so the solution is to either to uninstall the KB(s) or increase the timeout of responding time of the service.
Please refer as below
“I uninstalled that first patch (KB948109) and the service came back up. (I thought the sysadmins had rolled back that patch already, but apparently they had only removed KB951248).”
or to increase the timeout as this linker
However, this fix doesnt fit for me after trying. My one is because of trust betweem domains.
As a last resort before lunch, I tried to launch RS with windows login instead of the service account. Hum~~guess what…? It worked!
Why? My windows account and RS server are in the same domain but the original service account is in the other domain. Thus, when you start the RS, it goes to check your service account validness by communicating with the other domain. Somehow, the other domain cannot respond as quick as it is expected. Then, RS pops up “not in a timely fashion”. Make sense?!
My 2 cents. Maybe some value for you. Hopefully!