Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Services Snap-in|
The service did not respond to the start or control request in a timely fashion.
|English: Request a translation of the event description in plain English.|
I had this problem on Windows 2003 SP1 with services related to various Computer Associates products (Unicenter, ETrust). The problem was that my system PATH variable was too long.
See ME841713 for information about this event.
This error can also be seen if using APC’s UPS Powerchute Software. To resolve, boot up into safe mode, set the APC PBE Agent and APC PBE Server (where applicable) services to manual and reboot into normal mode. If the issue no longer occurs, download the latest version of PowerChute from APC to provide a permanent fix for this issue and then set the APC services back to automatic.
This is an issue with the Services snap-in on machines running Windows 2000 Service Pack 1. This is a timeout where the service has not reported that it has successfully stopped (or started) within 3 minutes. It seems that the service may still successfully start or stop, given time. The fix is to move to SP2, but there is also a workaround in MS article ME278712.
As per Microsoft: "This behavior can occur if the Terminal Services component is not installed or is disabled. Add the Terminal Services component by using the Add/Remove Programs tool in Control Panel before attempting to start the service". See ME222146 for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: ME222146, ME278712, ME841713|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated