Message content does not expire correctly, message content remains on the NTFS file system, and a memory leak occurs in Windows Server 2003

In Microsoft Windows Server 2003, you may experience one or more of the following problems with the Network News Transfer Protocol (NNTP) service:

• The content of a message is not removed from the NTFS file system if that message is rejected by a program such as an antivirus program.
  
  In Windows Server 2003, an event sink interface is available that lets programs interact with the NTFS file system. A program can use this event sink to reject a message by resetting a flag.
  
  However, when the onpost event is triggered, the content from the message that triggered this event is already stored in the NTFS file system. If the event sink rejects this message, only the hash table entry for that message is actually removed. The message content remains in the NTFS file system.
• Message expiration does not work correctly after you rebuild an NNTP virtual server.
  
  After you rebuild an NNTP virtual server, NNTP messages that are configured to expire after a certain time do not expire correctly. The message item time in the hash table is stamped with the current NNTP virtual server rebuild time.
• A memory leak occurs when you configure multiple sink events for the NNTP service.

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

No prerequisites are required for this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

Windows Server 2003, 32-bit editions

Windows Server 2003, 64-bit Enterprise Edition

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

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: