Microsoft KB Archive/223373

= SNA Server Rejects Host's BIND Response when the Primary Session Level Pacing Receive Window Size Is Zero =

Article ID: 223373

Article Last Modified on 9/22/2005

-

APPLIES TO


 * Microsoft SNA Server 4.0 Service Pack 2

-



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.



RESOLUTION
To 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.



STATUS
Microsoft 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.



MORE INFORMATION
The IBM Formats Reference Manual indicates the following for byte 13 of a BIND response:
 * Bits 0-1: Reserved
 * Bits 2-7: Primary receive window size, in binary, for session-level pacing

NOTE: A value of 0 means no pacing of requests flowing to the primary (for one-stage pacing in the secondary-to-primary direction, this field is redundant with, and will indicate the same value as, the secondary send window size--see byte 8, bits 2-7). The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For information about how to contact, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

65416 Hardware and Software Third-Party Vendor Contact List, A-K

60781 Hardware and Software Third-Party Vendor Contact List, L-P

60782 Hardware and Software Third-Party Vendor Contact List, Q-Z

Additional query words: BIND PACING

Keywords: kbbug kbfix kbsna400sp3fix kbqfe kbhotfixserver KB223373

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.