The information in this article applies to:
SYMPTOMS
An APPC or CPI-C application may unexpectedly hang while sending data on an
active conversation to a partner program running on a remote system. This
problem only occurs with SNA Server 4.0.
CAUSEIf SNA Server 4.0 receives an LU6.2 BIND request that contains a compression control vector or fully qualified PCID control vector, this could corrupt internal SNA client-server credit settings. This could cause the SNA Server client APPC interface to stop sending requests to SNA Server after several hundred messages are sent. WORKAROUNDReconfigure the remote system so that it does not initiate any LU6.2 sessions, and change SNA Server so that it always initiates the LU6.2 session. In SNA Server, automatic LU6.2 session activation can be accomplished by configuring a non-zero automatic activation limit on the APPC mode entry, and partnering the Local APPC LU with the Remote APPC LU that the APPC or CPI-C application will be using. STATUSMicrosoft has confirmed this to be a problem in SNA Server version 4.0. This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this 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:
Keywords : prodsna snaappc snacpic snaprog snaoledb snaodbc snaserverservice snatp |
Last Reviewed: December 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |