| Event Id | 686 |
| Source | SNA Server |
| Description | Application exception occurred: App: snaservr.DBG (pid=150) When: 3/18/1996 @ 19:10:9.145 Exception number: c0000005 (access violation) |
| Event Information | If you use the SNA Server MS-DOS Client using Novells ODI IPX/SPX protocol stack and the SNA Server DOS router to communicate with an AS/400, then SNA Server will log this event . According to Microsoft CAUSE The trap in SNASERVR.EXE occurs when the SNA Server buffer pool becomes corrupted. In this case, the corruption occurs because the client is sending a 10-byte frame to the SNA Server when it was expecting a 47-byte frame. Because the incoming frame was smaller than expected, SNA Server fills it in with zeroes or EBCDIC spaces that cause the buffer pool to become corrupted. The trap in SNABASE.EXE results because of the preceding trap in SNASERVR.EXE. RESOLUTION The IPX/SPX transport now verifies that the incoming message length is valid. If the length is invalid, the message is ignored and an event 631 is logged. Microsoft has updated the <snaroot>\snanw.dll file on both the SNA Server and the client to correct this problem. |
| Reference Links | SNA Server Event 686 When Using MS-DOS Client with ODI Stack. |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.