The information in this article applies to:
SYMPTOMSSNA Server may unexpectedly stop forwarding FMH-5 Attach messages to a specific branch-based SNA Server client computer (where the invokable transaction program [TP] is registered or running). When this occurs, SNA Server reports an Event 60 (DLOAD timeout) in the server's application log. For example:
084C0000 refers to AP_TRANS_PGM_NOT_AVAIL_NO_RETRY.
On the client computer, the APPC or CPIC invokable TP may never be invoked, or if it is running, the TP's call to CMAPPC or RECEIVE_ALLOCATE will not complete. To recover from this problem, the SnaBase service on the Windows NT client computer must be stopped and restarted. CAUSE
This problem can occur when the SNA Server client's sponsor
connection (LAN session) to the server-side SnaBase service is lost. This problem
occurs when the client-end of the client end of the LAN connection fails
first.
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 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 WORKAROUNDTo work around this problem, determine and correct the cause of the underlying LAN session failure between the SNA Server client and the server. STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 4.0. This problem was first corrected in SNA Server 3.0 Service Pack 4. Additional query words:
Keywords : kbbug4.00 kbfix4.00.sp1 snaappc snacpic kbbug3.00 kbbug3.00.sp2 snabaseservice snaserverservice snatp snawinnt |
Last Reviewed: November 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |