Symptom 1

On a Windows Server 2003-based computer that is running Microsoft Internet Security and Acceleration (ISA) Server 2004, the following event is logged in the Application log every 49.7 days:

Event Type: Error
Event Source: Microsoft ISA Server Control
Event Category: None
Event ID: 14079
Date: DATE
Time: TIME
User: N/A
Computer: ComputerName
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 for related error messages.

Note This event is logged multiple times.

Additionally, the Isasched service may be affected. The following event may be logged in the Application log:

Event Type: Error
Event Source: Microsoft ISA Server Control
Event Category: None
Event ID: 14079
Date: DATE
Time: TIME
User: N/A
Computer: ComputerName
Description:
Due to an unexpected error, the service isasched stopped responding to all requests. Stop the service or the corresponding process if it does not respond, and then start it again. Check for related error messages.

Back to the top

Symptom 2

On a Windows Server 2003-based computer that is not running ISA Server, a similar problem occurs when the following conditions are true:

•	You call the CreateTimerQueueTimer function repeatedly in an application.
•	You set a specified period to trigger the timer that is created by the CreateTimerQueueTimer function. Note The specified period should be less than 10 minutes.
•	The application runs for more than 49.7 days.

After 49.7 days, the timer is triggered immediately instead of being triggered after the specified period. After several minutes, the timer is triggered correctly.

Back to the top

This problem occurs because of the mathematical error in a kernel timer manipulation. ISA Server uses a timer to monitor the Firewall service. Other applications that use a timer that is created by the CreateTimerQueueTimer function may also experience this issue.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with SP1, x86-based versions

File name	File version	File size	Date	Time	Platform
Ntdll.dll	5.2.3790.3038	769,024	06-Nov-2007	06:28	x86

Windows Server 2003 with SP1, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdll.dll	5.2.3790.3038	1,636,352	06-Nov-2007	04:13	IA-64	SP1	Not applicable
Ntkrnlmp.exe	5.2.3790.3038	6,534,656	06-Nov-2007	04:13	IA-64	SP1	Not applicable
Wntdll.dll	5.2.3790.3038	765,952	06-Nov-2007	04:13	x86	SP1	WOW

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdll.dll	5.2.3790.3038	1,253,376	06-Nov-2007	04:12	x64	SP1	Not applicable
Wntdll.dll	5.2.3790.3038	765,952	06-Nov-2007	04:12	x86	SP1	WOW

Windows Server 2003 with SP2, x86-based versions

File name	File version	File size	Date	Time	Platform
Ntdll.dll	5.2.3790.4183	765,440	06-Nov-2007	06:16	x86

Windows Server 2003 with SP2, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdll.dll	5.2.3790.4183	1,636,864	06-Nov-2007	04:22	IA-64	SP2	Not applicable
Ntkrnlmp.exe	5.2.3790.4183	6,568,960	06-Nov-2007	04:22	IA-64	SP2	Not applicable
Wntdll.dll	5.2.3790.4183	766,464	06-Nov-2007	04:22	x86	SP2	WOW

Windows Server 2003 with SP2, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Ntdll.dll	5.2.3790.4183	1,254,400	06-Nov-2007	04:22	x64	SP2	Not applicable
Wntdll.dll	5.2.3790.4183	766,464	06-Nov-2007	04:22	x86	SP2	WOW

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top