FIX: The BizTalk Server 2004 File Adapter may cause a NonPagedPool memory leak

Article translations Article translations
Article ID: 886226 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

The Microsoft BizTalk Server 2004 File Adapter may cause a NonPagedPool memory leak by issuing too many input/output request packets (IRPs). The possibility of the memory leak increases with the number of receive locations that use the File Adapter.

To verify that your BizTalk Server-based server is experiencing a NonPagedPool memory leak, use Performance Monitor to monitor the following counters:
  • Object: Memory
    Counter: Pool Nonpaged Bytes
  • Object: Process
    Instance: BTSNTSvc
    Counter: Pool Nonpaged Bytes
In some extreme cases, when all available system NonPagedPool memory is used up, you may receive an error message that is similar to the following in the System log on your BizTalk Server-based server:
Event ID: 2019
Source: Srv
Description: The server was unable to allocate from the system nonpaged pool because the pool was empty.
If you receive this error message, your BizTalk Server-based server may stop responding (hang). Additionally, your BizTalk Server-based server may restart if the Automatically restart option is enabled on the Startup and Recovery dialog box that you can open from the Advanced tab of the System Properties dialog box. To access the System Properties dialog box, right-click My Computer, and then click Properties.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751 How to obtain the latest BizTalk Server 2004 service pack

Hotfix information

Prerequisites

The following prerequisites are required for this hotfix:
838454 FIX: You cannot access information about messages in the MessageBox database or track messages in your archives in BizTalk Server 2004
840008 FIX: You cannot access the headers and the body of an HTTP failure response in a SOAPException exception
842138 FIX: BizTalk Server 2004 RTM Version does not support the transactional protocol in the BAM API

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 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 tool in Control Panel.
   Date         Time   Version     Size       File name
   ---------------------------------------------------------
   28-Sep-2004  00:05  3.0.5346.0  1,026,560  Btsmsgcore.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in BizTalk Server 2004 Service Pack 1.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 886226 - Last Review: June 1, 2006 - Revision: 2.1
APPLIES TO
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
Keywords: 
kbbiztalk2004sp1fix kbsiteserv300sp4fix kbbiztalk2004presp1fix kbbug kbfix kbhotfixserver kbqfe KB886226

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com