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: Microsoft ISA Server Control|
Due to an unexpected error, the service <service name> stopped responding to all requests. This occured <number> time(s) in the past <number> hours. Try to stop the service or kill the corresponding process if it does not respond, and start it again. Check the Event Viewer for related error messages.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Why are some errors “unexpected”?
- Service: fwsrv - See ME916152, ME919515, ME937258, ME944762 and ME956268.
- Service: isasched - See ME944762.
See "Technet Blog" for a possible solution to this problem.
See ME840180 for information about this event.
If this is a SBS 2003 box with ISA 2004, redo the SBS monitoring wizard, as this appears to get rid of this bogus event.
See ME887311 to resolve this problem.
From a newsgroup post: "If this problem appeared after installing the patch found in ME888258, do the following to resolve the problem:
1. Remove the patch.
2. Apply the workaround steps in ME889189
2. Run the script http://isatools.org/ms04-039.js on the ISA".
Services: w3proxy, w3schdwn, fwsrv. As per Microsoft (ME293863): "A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next ISA Server service pack that contains this fix."
I was getting these errors because when I logged on to the Proxy server the power options in control panel were changed from "Always On" to "Laptop/Portable". The problems stopped when settings were changed again.
|Private comment: Subscribers only. See example of private comment|
|Links: ME293863, ME840180, ME887311, ME889189, ME916152, ME919515, ME937258, ME944762, ME956268, http://isatools.org/ms04-039.js, Technet Blog|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated