SNA Server Fails to Activate DDDLU Pooled LU

 Last reviewed: May 1, 1997
Article ID: Q164650
The information in this article applies to:
  • Microsoft SNA Server, versions 2.11, 2.11 Service Pack 1, 2.11 Service Pack 2, and 3.0

SYMPTOMS

SNA Server 2.11 and 3.0 fail to dynamically activate an LU (through the host dynamic definition of dependent LUs) after the connection has been active for five minutes. After five minutes, the SNA Server stops sending NMVTs to request activation, and rejects client 3270 session activation requests (that is, Open(SSCP) requests) with the following error: 

   No free LU in LU Pool.

CAUSE

After five minutes, SNA Server no longer attempts to activate dynamically defined 3270 LUs.

RESOLUTION

To resolve this problem, obtain the hotfix mentioned below.

The updated modules are: 

   <Snaroot>\System\Snaservr.exe
   <Snaroot>\System\Trcservr.exe (used for debugging purposes only)

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 2.11, 2.11 Service Pack 1, and 3.0. This problem was corrected in the latest Microsoft SNA Server 2.11 and 3.0 U.S. Service Packs. For information on obtaining the service packs, 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 sna30
Keywords : kbbug2.11 kbbug2.11.sp1 kbbug3.00 kbfix3.00.sp1 sna3270 snaserverservice
Version : 2.11 2.11.sp1 2.11.sp2 3.0
Platform : WINNT
Issue type : kbbug
Resolution 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: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.