The information in this article applies to:
SYMPTOMSSNA Server may encounter access violations or hard-coded break points within Snaservr.exe in an environment where corrupt 802.2 frames are being sent as a result of a bad network card or network card driver. The failures result in a Drwtsn32.log that may show the following type of failures: In the Windows NT Application log the following event will be logged with the same timestamp as the hard-coded break point: SNA traces of the failures may show corrupted XID frames or terminate during the processing of an XID. CAUSE
If an XID is received with an incorrect length field, the SNA Server XID
parsing code fails to handle the processing of the frame correctly.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 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 INFORMATIONWith the fix applied, the XID parsing behavior of SNA Server correctly handles XIDs with invalid length fields. Additional query words: EventID 686 Hardcoded
Keywords : kbnetwork snadlc snaserverservice kbfix3.00.sp2 |
Last Reviewed: November 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |