Activating Numerous DLC Connections Results in Inactive LUs (216047)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 4.0
This article was previously published under Q216047 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
An SNA Server that has numerous DLC 802.2 connections may experience
symptoms similar to the following if the connections are activated
concurrently:
The number of connections that can be activated before experiencing this
problem will vary. In general, this may occur in environments that have 50
or more DLC 802.2 connections where each connection has many 3270 LUs
defined.
CAUSE
The SNA Server DLC 802.2 link service uses an internal buffer pool to
handle messages that it has to process. If this buffer pool is exhausted,
the link service may discard some of the messages that is it receiving from
the SNA Server service or from the DLC protocol stack. If the link service
discards these messages, the symptoms described above can occur.
RESOLUTIONSNA Server 4.0To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
SNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0SP2, 3.0 SP3, 4.0, 4.0 SP1, 4.0 SP2. This problem was first corrected in SNA Server version 3.0 Service Pack 4 and SNA Server version 4.0 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/22/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE kbsna300sp4fix kbsna400sp3fix KB216047 |
---|
|