SNA Server Twinax Connection to IBM 5494 Traps with 0x00000050

Last reviewed: February 1, 1996
Article ID: Q139507
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, version 2.11

SYMPTOMS

After you stop an SNA Server that is connected through Twinax to an IBM 5494 or 5394 Controller (that is connected to an AS/400) and then restart the server, the server fails with the following STOP message:

   STOP:0x00000050

CAUSE

The SNA Server Twinax driver support is not handling the startup sequence properly when connecting through an IBM 5394 or 5494, which differs slightly from the native startup to an AS/400.

When the SNA Server Twinax link service starts, a Memory Descriptor List (MDL) entry that is passed from User Mode to Kernel Mode is corrupt, hence the bugcheck is called displaying the STOP:0x00000050.

RESOLUTION

When you stop the SNA Server service, reboot the server before restarting the service.

Microsoft has updated the following files to correct this problem:

   IBMTDLC.SYS
   ANDWTDLC.SYS
   SNATDLC.DLL.

STATUS

Microsoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 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


KBCategory: kbnetwork kbsetup kbbug2.11
KBSubcategory: ntnetserv
Additional reference words: 2.11 prodsna


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