Article ID: 181121
Article Last Modified on 9/22/2005
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
This article was previously published under Q181121
SYMPTOMS
To improve the ability to troubleshoot SNA Server Event 9 (subcode 1117) and Event 12 errors, these events have been enhanced to include the following additional information:
- Client Domain
- Client User (name)
- LU name (3270 LU)
- FMI Sense Code
When SNA Server logs an Event 9 (subcode 1117), the SNA Server has detected an SNA protocol violation by the 3270 emulation product being used. The Event 9 indicates a non-fatal protocol violation which would not cause a user to lose their 3270 session. If SNA Server detects a nonrecoverable 3270 protocol violation by the 3270 emulation product, SNA Server logs an Event 12.
Using SNA Server 3.0 (including 3.0 SP1 and SP2), it's not possible to determine which client workstation caused these problems to occur, making troubleshooting more difficult. These events have been enhanced so that the specific client user can be tracked down.
To debug the exact cause of these events, SNA Server 3270 message tracing is needed on either the server or the client computer.
STATUS
MORE INFORMATION
SNA Server 4.0 already includes these enhancements to SNA Server Event 9 and 12. These changes have been retrofitted to SNA Server 3.0 Service Pack 3 (SP3) in order to improve diagnostic capability for the 3.0 product.
Here is the event message text for these enhanced events:
Keywords: kbbug kbfix kbqfe kbhotfixserver KB181121