Hello Cause This problem can occur because of improper handling of the tick count overlap by the scheduler that is used to raise alerts and manage keep alive signaling. This overlapping happens after every 49 days of continuous running (for the server computer). In this case, the DWORD that is used for storing the tick count overlaps, and this can cause some alerts to be raised over and over again and intense (approximately 190 queries each second) LDAP querying on an Active Directory-integrated ISA Server-based computer for a short period. The problem occurs because the scheduler checks for overtimed tasks (after a new task is inserted to its list) by comparing the current tick count to the one that is stored in the task. When the tick count overlapps, future tasks that are scheduled (a minute later) are considered to be overtimed, and because of this, are run at once. After the task runs, it is re-inserted into the task list, only to be run again. This can happen at a rate of ten times each second. Resolution A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing. 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. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later: Date Time Version Size File name Platform ---------------------------------------------------------------- Apr 4, 2001 14:13:32 3.0.1200.62 211,216 Msfpc.dll Intel Workaround To work around this problem, restart all of the services: 1. At a command prompt, type net stop isactrl, and then press ENTER. 2. Type net start fwsrv, and then press ENTER. 3. Type net start w3proxy, and then press ENTER Best regards hanan _____ Send feedback to Microsoft <JavaScript:sendfeedback('Q293863',%20'TECHNET@xxxxxxxxxxxxx')> © 2002-2003 Microsoft Corporation. All rights reserved. <ms-help:/../shared/copyright/copyright.htm> -----Original Message----- From: shane [mailto:tsmullins@xxxxxxxxxxxxxxxxxxx] Sent: Wednesday, March 05, 2003 8:18 PM To: [ISAserver.org Discussion List] Subject: [isalist] fwsrv stopped responding to all requests, Please Help http://www.ISAserver.org I get the following error: ISA Server name: PROXY Due to an unexpected error, the service fwsrv stopped responding to all requests. This occurred 16433 time(s) in the past 17:01 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. Could someone please help me on this? I looked in the Event Viewer but could find no relevant information, Thanks Shane ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: nouran@xxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')