Two Separate Threads In WinSLI Critical Section Can Cause Hang

Last reviewed: March 19, 1998
Article ID: Q174467

The information in this article applies to:

Microsoft SNA Server for Windows NT, versions 3.0 and 3.0sp1

SYMPTOMS

Two separate threads from an SLI application appear to gain access to the SLI critical section, coinciding with an application's SLI call that hangs and never completes. This problem was observed with a Win32 SLI application which supported over 50 different threads, each calling the SLI interface. At times, an SLI call would hang and fail to complete.

CAUSE

The SNA Server Winsli32.dll was not behaving correctly.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0sp1. 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

KBCategory: kbnetwork kbbuglist kbprog
KBSubcategory: prodsna winlua snaprog
Additional reference words: critical section hang thread
Keywords : kbbug3.00 kbbug3.00.sp1 prodsna kbfix3.00.sp2
Version : 3.0 3.0sp1

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.