Article ID: 139674
Article Last Modified on 12/8/2003
APPLIES TO
- Microsoft SNA Server 2.0, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 2.1, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 3.0, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q139674
SYMPTOMS
SNA Server may log the following error if an internal client-server communication error is detected:
This message, however, does not indicate the underlying cause of the error.
CAUSE
Message 631 is logged by SNA Server if any of the following error conditions is detected in a message sent by another SNA Server component:
- The mhtype is invalid.
- The message ID is invalid.
- The sequence number is wrong.
The mhtype, message ID, and sequence number are included in all messages passed between SNA Server components (for example, between SNA Server and a 3270 or APPC application, between SNA Server and a link service, and between SnaBase and an SNA client).
RESOLUTION
Microsoft has updated the following files to correct this problem:
SNAEVENT.DLL
SNALM.DLL
SNAIP.DLL
SNANW.DLL
SNANB.DLL
SNABV.DLL
SNAAT.DLL
With this fix applied, Message 631 now logs the following information:
- The reason for logging the event.
- Message header information.
- Expected sequence number.
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
Additional query words: prodsna 2.00 2.10 2.11
Keywords: kbbug kbfix KB139674
