SNA Server Traps After Receiving BIND +RSP With Invalid Data

Last reviewed: March 19, 1998
Article ID: Q171876
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.11 Service Pack 1, 3.0, 3.0 Service Pack 1

SYMPTOMS

An A Server access violation (0xC0000005) may occur in routine s1pnsuns() if an AS/400 responds with an invalid BIND +RSP.

CAUSE

The SNA Server service (Snaservr.exe) does not parse the user data in the BIND +RSP correctly. An invalid BIND +RSP from AS/400 may lead to an access violation.

RESOLUTION

A hotfix to SNA Server for Windows NT, version 2.11 (post SP2) and version 3.0 (post SP1) is available to correct this problem.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 2.11 Service Pack 1, 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
Keywords          : kbbug2.11.sp1 kbbug3.00 kbbug3.00.sp1 prodsna snaappc snaserverservice kbfix3.00.sp2 kbnetwork
Version           : 2.11,3.0
Platform          : winnt
Issue type        : kbbug


================================================================================


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.