The information in this article applies to:
SYMPTOMS
Microsoft SNA Server (Snaservr.exe) may fail unexpectedly with an
access
violation. The following event will be logged into the Windows NT
application event log:
The following log entry will be created in the <Ntroot>\Drwtsn32.log file:
CAUSE
This problem can occur if the host system sends an invalid "User
Request Correlation Field" in the BIND for an LU6.2 session. Under normal
situations, an INIT-SELF Format 1 would be sent to the host
containing the URC field. The host should then reply with a BIND that contains
the same URC field. It was observed on a tandem host, that the URC field in
the BIND was badly formatted and caused SNA Server to access violate.
Please refer to the IBM SNA Format Manual for the valid format of the request
units.
RESOLUTIONSNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:Q184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack SNA Server 4.0This problem was corrected in the latest Microsoft 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):
This fix stops SNA Server from access violating, and instead sends a negative response to the invalid BIND. You will still need to address why the host is not sending a valid "User Request Correlation Field." STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 4.0 and 4.0 SP1. This problem was first corrected in SNA Server 3.0 Service Pack 4. Additional query words: prodsna snaserverservice kbbug4.00 kbfix4.00.sp1 kbbug3.00 kbbug3.00.sp1 kbbug3.00.sp2 kbfix3.00.sp3
Keywords : |
Last Reviewed: July 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |