The information in this article applies to:
SYMPTOMS
A Windows NT Server running SNA Server 2.11 slows down when running SNA
Server clients that use TCP/IP.
CAUSEAn SNA Server Service internal trace shows that SNA Server TCP/IP asynchronous writes are not completing. These pending writes continue to consume system memory. The SNA Server client configured for TCP/IP may continuously attempt to open a session with the SNA Server. The SNA Server tries to send a response but the write never completes and is unable to release the i/o (input/output) buffer memory. RESOLUTIONSNAIP.DLL now aborts a connection if the connection has more than 100 pending writes queued. Every time a connection is aborted, an event 706 is logged in the application log: You can configure the abort limit by adding the MaxPendingWrites registry parameter:
<snaroot>\SYSTEM\SNAIP.DLL STATUSMicrosoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words: prodsna
Keywords : kbnetwork ntnetserv kbbug2.10 kbbug2.11 |
Last Reviewed: November 19, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |