Microsoft KB Archive/180538

= SNA Server SDLC Connection Fails to Reactivate After Host IPL =

Article ID: 180538

Article Last Modified on 6/24/2004

-

APPLIES TO


 * Microsoft SNA Server 3.0
 * Microsoft SNA Server 2.11 Service Pack 1
 * Microsoft SNA Server 2.11 Service Pack 2
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 4.0

-



This article was previously published under Q180538



SYMPTOMS
An SDLC connection from SNA Server to a front-end processor (FEP) remains in a pending state after the host performs an IPL. The only means of recovery is to stop and restart the SNA Server service.

SNA Server may post an Event 23 in the Windows NT application event log with a qualifier of 00A1 or 0025 as a result of these symptoms.



CAUSE
SNA Server is erroneously handling the non-activation XIDs sent from the FEP on an SDLC connection and treating this as a connection outage.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was corrected in the latest SNA Server version 3.0 and 4.0 U.S. Service Packs. For information on obtaining these Service Packs, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K



MORE INFORMATION
With the fix applied, the Ibmsdlc.DLL interface allows for the correct handling of SDLC non-activation XIDs.

The SNA Server Ibmsdlc.dll (SDLC Link Service) file supports a "dumb card" driver interface that is published in the appendix of the SNA Device Interface Specification (SNADIS) guide. This link service will work with any dumb card implementation, such as Ibmsync.sys (the IBMSDLC driver), Microgate, DCA ISCA, Attachmate SDLC, as well as others.

Other SDLC link services implement the full SNADIS interface so the Ibmsdlc.dll is not used. Some examples of these link services include Eicon SDLC and Barr SDLC.

Additional query words: 0xA1 0x25 IPL pending connection

Keywords: kbbug kbfix kbnetwork KB180538

-

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

© Microsoft Corporation. All rights reserved.