Cancelling SNA Windows 95 Logon Causes Sbpuinit() rc = 563

Last reviewed: March 19, 1998
Article ID: Q171934

The information in this article applies to:

  • Microsoft SNA Server, versions 2.11, 2.11 Service Pack 1 (SP1), 2.11 SP2, 3.0, and 3.0 SP1

SYMPTOMS

When an SNA Server 3270 EIS application calls sbpuinit() on a Windows 95 client configured to use a non-named pipe transport (for example, TCP/IP sockets, IPX/SPX, or Banyan IP), the SNA client software displays a user logon dialog box. If the user cancels this logon dialog box, the sbpuinit() function returns incorrectly with error 563 (DMDSTFL, or "service table full"), instead of error 625 (DMNONAP, or "NAP not up when starting service").

These error codes are documented in the SNA Server Emulator Interface Guide and \SDK\INC\FMI.H include file, which ships on the SNA Server compact disc.

CAUSE

The SNA Server Windows 95 Snadmod.dll does not retrieve the correct error to the sbpuinit() function when the logon dialog box is cancelled.

STATUS

Microsoft has confirmed this to be a problem in the SNA Server Windows 95 client version 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

The updated Windows 95 client modules are snakrnl.dll and snadmod.dll.

Keywords          : snaeis snaprog snawin95 kbfix3.00.sp2 kbnetwork
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.