Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: "Craig" <cddefo@xxxxxxxxxxxx>
- Date: Fri, 24 Jun 2005 08:26:33 -0500
Hi Ray-
You're right-didn't help me either.
I know the fwsvr is always running, ISA shows the total up time. I think
it is just not responding quickly enough when the system checks it. After
rebooting & increasing the connections per client, it didn't log error for
24 hrs. It started logging it hourly starting at 10am, BUT it did not log
any error at 4pm, 6pm, 8pm-12am, 3-4am, or 6am. I am not sure why it is
happening.
"Ray Collins" <ray.collins@xxxxxxxxxxxxxxxxx> wrote in message
news:uFb7WYEeFHA.2420@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the tip, I have already changed this, no joy :-(
>
> "Craig" <cddefo@xxxxxxxxxxxx> wrote in message
> news:OvIZ5o$dFHA.892@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi Ray-
>>
>> I checked the log- No new errors since I increased the "Connection limit
>> per client (TCP and non-TCP) from 40 to 160. You may want to try this.
>> It is located in ISA server management | Configuration | General | under
>> the Additional Security policy | click Define Connection limits | then
>> change Connection limit per client (TCP and non-TCP) to 160.
>>
>> The key maybe a single early warning about exceeding connection limits.
>> Then sometime after that the error fwsrv is logged saying it stopped
>> responding to all requests. Try searching your log for the entry listed
>> below.
>>
>>
>>
>> Event Type: Warning
>> Event Source: Microsoft Firewall
>> Event Category: Packet filter
>> Event ID: 15112
>> Date: 6/22/2005
>> Time: 10:29:26 AM
>> User: N/A
>> Computer: Server
>> Description:
>> The client 192.168.0.20 exceeded its connection limit. The new connection
>> was rejected. For more information about this event, see the Windows
>> event viewer.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> Event Type: Error
>> Event Source: Microsoft ISA Server Control
>> Event Category: None
>> Event ID: 14079
>> Date: 6/22/2005
>> Time: 1:47:06 PM
>> User: N/A
>> Computer: Server
>> Description:
>> Due to an unexpected error, the service fwsrv stopped responding to all
>> requests. Stop the service or the corresponding process if it does not
>> respond, and then start it again. Check the Windows event Viewer for
>> related error messages.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>>
>>
>> "Ray Collins" <ray.collins@xxxxxxxxxxxxxxxxx> wrote in message
>> news:%23l7ehR3dFHA.3836@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi Craig,
>>>
>>> The Microsoft case I have open has now expanded to include input from
>>> Susan and a member of the ISA dev team that Susan put me in touch with.
>>> Still no resolution but more minds at work. :-)
>>>
>>> I will post the resolution when found.
>>>
>>>
>>> "Craig" <cddefo@xxxxxxxxxxxx> wrote in message
>>> news:uxy36LzdFHA.3012@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Problem still exists.
>>>>
>>>> "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@xxxxxxx> wrote in message
>>>> news:OrDDAfAdFHA.220@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> go into Server Mgmt and rerun the Monitoring wizard.
>>>>>
>>>>> --
>>>>> Kevin Weilbacher [SBS-MVP]
>>>>> "The days pass by so quickly now, the nights are seldom long"
>>>>>
>>>>>
>>>>> "Ray Collins" <ray.collins@xxxxxxxxxxxxxxxxx> wrote in message
>>>>> news:OuhpTg%23cFHA.4040@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> What do you mean "redoing the monitoring" ?
>>>>>>
>>>>>> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
>>>>>> <sbradcpa@xxxxxxxxxxx> wrote in message
>>>>>> news:uZNOmF9cFHA.892@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>>
>>>>>>> "Just to confirm, Susan suggested re-doing the SBS monitoring to get
>>>>>>> rid of the 14079 ISA errors on my SBS2003 SP1 test server - and that
>>>>>>> is true. I redid it last Sunday, and I have had no reoccurrence of
>>>>>>> the 14079 error since then. "
>>>>>>>
>>>>>>>
>>>>>>> Try redoing the monitoring
>>>>>>>
>>>>>>> Craig wrote:
>>>>>>>
>>>>>>>>Getting this error after SP1, how can I stop it from reporting
>>>>>>>>this? TIA
>>>>>>>>
>>>>>>>> Microsoft ISA Server Control 14079 6/17/2005 5:46 AM 5 *
>>>>>>>> Due to an unexpected error, the service fwsrv stopped
>>>>>>>> responding to all requests. Stop the service or the corresponding
>>>>>>>> process if it does not respond, and then start it again. Check the
>>>>>>>> Windows event Viewer for related error messages.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> An open letter to the Security Community::
>>>>>>> http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- References:
- Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Craig
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Ray Collins
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Kevin Weilbacher [SBS-MVP]
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Craig
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Ray Collins
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Craig
- Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- From: Ray Collins
- Due to an unexpected error, the service fwsrv stopped responding to all requests.
- Prev by Date: Re: licences issued in SBS 2003
- Next by Date: 2003 SP1 changes From name for reports
- Previous by thread: Re: Due to an unexpected error, the service fwsrv stopped responding to all requests.
- Next by thread: Error installing SBS SP1 - Admin Groups
- Index(es):
Relevant Pages
|
