SNA Server Logs Events 684 and 685 When Using SDLC Connection

Last reviewed: February 3, 1998
Article ID: Q176849

The information in this article applies to:

Microsoft SNA Server, versions 2.0, 2.1, 2.11, 2.11 SP1, 2.11 SP2, 3.0, 3.0 SP1, 3.0 SP2

SYMPTOMS

An SNA Server computer using an SDLC Link Service for host connections may log the following message in the Windows NT application event log at random intervals:

   Event ID: 684
   Description: A buffer pool audit has been triggered by a pool extension.

The description also lists the number of allocated trusted headers. Each successive Event 684 shows a larger number of allocated trusted headers.

Eventually the allocated trusted headers will reach the maximum value, and the connection to the host will be lost. At this point, the following message will be logged in the application event log:

   Event ID: 685
   Description: An attempt was made to extend a buffer pool, but the
   related pool had reached its maximum size. The affected component is
   terminating, and an audit of the buffer pools just before termination is
   attached.

   <Listing of the buffer pools omitted>

A trace of the SDLC Link Service shows numerous DLCST UPSN messages (update station statistics) being sent to the SNA Server service. For more information about DLCST UPSN messages, refer to the following Microsoft Knowledge Base article:

    Article-ID: Q139594
    Title : Meaning of "DLCST UPSN" in an SNA Server Data Link Control
   Trace

CAUSE

Messages from the Link Service are being placed into the buffer pool much faster than the SNA Server service can process them. This is usually caused by a problem elsewhere in the system, for example, in the SDLC adapter or driver. However, SNA Server should deal with this situation without dropping the host connection.

The UPSNSTAT messages let the SNA Server service track statistics for sending in RECFMS messages to the host. RECFMS has been retired from SNA for type 2 nodes, and UPSNSTAT is not in the published Microsoft SNA Device Interface Specification, so UPSNSTAT message handling has been removed from the Ibmsdlc.dll Link Service. This eliminates the effects of the problem.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0 Service Pack 2 and earlier. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.

Keywords          : kbbug2.00 kbbug2.11 kbbug3.00 snasdlc kbbuglist
Version           : WINDOWS:2.0,2.1,2.11,2.11SP1,2.11SP2,3.0,3.0SP1,3.0SP2
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.