SNA Server Rejects Host's BIND Response when the Primary Session Level Pacing Receive Window Size Is Zero (223373)
The information in this article applies to:
- Microsoft SNA Server 4.0 SP2
This article was previously published under Q223373 SYMPTOMS
After you upgrade your VTAM version to 4.4 on the host, SNA Server starts rejecting the host's BIND responses with an UNBIND(06):
Invalid session parameters:
The BIND negotiation has failed because the primary half-session cannot
support parameters specified by the secondary.
In the Windows NT application log the following event may be seen:
Event ID: 22
Description: APPC session activation failure:
BIND negotiated parameters unacceptable, Sense data = 10050000.
CAUSE
SNA Server checks the BIND response pacing parameters to ensure that the PRIMARY RECEIVE WINDOW FIELD SIZE is equal to THE SECONDARY SEND WINDOW SIZE. If this is not true, then the BIND response is rejected.
RESOLUTIONTo resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
WORKAROUND
To workaround this problem, change the configuration files on the host that are responsible for coding the BIND image so that the BIND RSP ensures the PRIMARY RCV WINDOW SIZE = THE SECONDARY SEND WINDOW SIZE rather then making byte 13 equal zero.
Also note that IBM has produced a PTF and an APAR that addresses this problem for
OS390 V2.5 and VTAM 4.4. For information about obtaining this PTF and APAR, please contact IBM Technical Support or visit IBM's Web site at http://www.ibm.com.
STATUSMicrosoft has confirmed that this is a problem in Microsoft SNA Server version 4.0 Service Pack 2. This problem was first corrected in SNA Server version 4.0 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/22/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE kbsna400sp3fix KB223373 |
---|
|