FIX: Message Screener Causes Handle Leak in Lsass.exe

You cannot run reports in Internet Security and Acceleration (ISA) Server 2000, and the following event ID message is logged in the event log:

Event Type: Error
Event Source: Microsoft ISA report generator Event
Category: None
Event ID: 21026
Date: 2002-10-13
Time: 00:50:00
Description: The action to create the scheduled report, "Weekly Report", with the specified credentials, failed. The error code in the Data area of the event properties indicates the cause.
Data: 0000: 0d 00 00 00

To get the Win32 error for the status code 13 (0x0d) in the Data field of the event, type the following line at a command prompt:

net helpmsg 13

This command returns the following output: Note This problem occurs only if ISA Server and the ISA Server SMTP Message Screener (Fltrsnk1.dll) are installed and running on the same computer. To verify that the message screener is installed, follow the steps in the "More Information" section of this article.

This problem occurs because the message screener is running in the Inetinfo process and is causing a handle leak in the LSAOpenPolicy handle table. The LSAOpenPolicy handle table is hosted by the Lsass.exe process.

After approximately 8 to 14 days, the maximum number of available handles is reached. After this occurs, the Report Generator (Repgen.exe) process fails when it calls LSAOpenPolicy. The Report Generator process fails because it uses the same parameter as the message screener to call LSAOpenPolicy. Any other processes or components that use the same parameter as the message screener to call LSAOpenPolicy also fail.

To work around this issue, shut down and then restart the Inetinfo process. The handles that are held by the Inetinfo process are now available to the handle table in Lsass.exe.

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. The English version of this fix 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.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

By default, the message screener is not installed during ISA Server Setup. To check to see if the message screener was installed during setup, follow these steps:

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Add or Remove Programs.
3. Click Microsoft Internet Security and Acceleration Server, and then click Change.
4. Click Custom Installation, and then click Add-in services.
   
   If the Message Screener check box is selected, it is installed.

To check to see if the message screener is running in the Inetinfo process, run the following command from a command prompt:

tlist -m fltrsnk1.dll

The output lists the active processes. If the Inetinfo process is listed, the message screener is running in the Inetinfo process.

The Tlist.exe is part of the Microsoft Debugging Tools. To install these tools, visit the following Microsoft Web site: http://www.microsoft.com/whdc/devtools/debugging/default.mspx