Win95 LUA/RUI Application Hangs with Named Pipes

 Last reviewed: November 1, 1995
Article ID: Q138481
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1, and 2.11

SYMPTOMS

When running an LUA/RUI application on Windows 95 using the Windows 95 SNA Client, the application may hang.

For instance, if your program contains only the following code: 

   main()

   {
      int rc;

      sync_event = CreateEvent(0,0,0,0);
      lua_attach();
      lua_init();
      rc=pWinRUICleanup();
      printf( "RUI CLEANUP() %d\n", rc );
      return(0);
   }
The application never processes the return(0) statement to exit the program until you either kill the application thru the Windows 95 task list or stop the link service in SNA Server Admin. The printf statement executes. This only occurs when running Named Pipes for the client interface. If you are using TCP/IP or SPX sockets the program exits correctly. This error does not occur on Microsoft Windows NT.

CAUSE

RUI_kill_session is passing an invalid locality to sbpddrop().

RESOLUTION

Microsoft has confirmed this to be a problem in Microsoft SNA Server version 2.11. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

KBCategory: kbnetwork kbprg kbbug2.00 kbbug2.10 kbbug2.11 kbfix2.11a sp1
KBSubcategory: ntnetserv
Additional reference words: prodsna 2.00 2.10 2.11 3.50 3.51

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: November 1, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.