DOCUMENT:Q165047 13-JUN-2001 [sna] TITLE :Get_TP_Properties Returns Incorrectly If Conversation Started PRODUCT :Microsoft SNA Server PROD/VER:WINDOWS:3.0 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server, version 3.0 ------------------------------------------------------------------------------- SYMPTOMS ======== When a remote node sends SNA Server an Attach (FMH-5) for conversation, the Receive_Allocate() and the Get_TP_Properties() complete successfully, but the field containing the Local LU contains the Partner LU name. This causes the Get_TP_Properties() to return the wrong status for this LU. CAUSE ===== The APPC library extracts the Local Fully Qualified (FQ) LU name from the Logical-Unit-of-Work-Identifier (LUWID) in the Attach (FMH-5), rather than using a stored copy of the Local LU Name and Network name to reconstruct the Fully Qualified (FQ) LU name. While this works correctly for conversations started locally, it does not work for remotely initiated conversations where the LUWID contains the partner Fully Qualified (FQ) LU name. RESOLUTION ========== A fix is available to correct this problem. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 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 sna30 ====================================================================== Keywords : Technology : kbAudDeveloper kbSNAServSearch kbSNAServ300 Version : WINDOWS:3.0 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. Copyright Microsoft Corporation 2001.