The information in this article applies to:
SYMPTOMS
A connection is configured for independent LU6.2 sessions between SNA
Server and a mainframe computer. When activating this connection, the
SNAServer service (Snaservr.exe) may terminate unexpectedly, generating a
Drwtsn32.log file in the Windows NT directory.
In addition, SNA Server will log an Event ID 3 Qualifier 1106 in the Windows NT Application Event Log:
CAUSE
This problem occurs when SNA Server receives a BIND from the mainframe that
does not contain a Network-Qualified PLU Network Name Structured Data
Subfield. The BIND does contain a fully-qualified Network Services Primary
LU Name Field, but SNA Server ignores this. SNA Server tries to process
the BIND but fails because a remote LU data structure that is expected to
be present for the Network-Qualified PLU Network Name Structured Data
Subfield is absent.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.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 MORE INFORMATIONWith the fix applied, SNA Server functions properly when it encounters a BIND without a Network-Qualified PLU Network Name Structured Data Subfield. Additional query words:
Keywords : kbnetwork snaappc snacpic snaprog kbfix3.00.sp2 |
Last Reviewed: November 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |