SNA Manager Fails to Display Status for Dependent APPC LUs

Last reviewed: March 19, 1998
Article ID: Q168037

The information in this article applies to:

  • Microsoft SNA Server, versions 3.0 and 3.0 SP1

SYMPTOMS

SNA Server Manager fails to display the User Name and Client for an APPC or CPIC application that is using a dependent LU6.2 session. Instead, the status information displays as:

   User Name: <Not In Use>
   Client: <n/a>

CAUSE

The problem with the dependent LU occurs because the session is created before there is an internal user record. Normally, internal user records are created first. When Manage is notified of an APPC session, it matches the data with an existing user record. In this case it fails to find a match.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

With the fix applied, Manage periodically refreshes the APPC session data so that after the user record is created, Manage gets the new APPC session info, and is able to match it with the user record.

Keywords          : kbbug3.00 kbbug3.00.sp1 snaappc snacpic snamanager kbfix3.00.sp2 kbnetwork
Version           : 3.0
Platform          : winnt
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: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.