The information in this article applies to:
SYMPTOMSMicrosoft SNA Server logs an Event 60 error if it receives an FMH- 5 Attach request from a remote system and the invokable transaction program (TP) is not registered on an SNA Server client or fails to start within the timeout period. The event appears as follows:
EXPLANATIONAn attempt to invoke the APPC TP shown has failed. The error will be reported to the invoking TP on the remote system with the following primary return code: However, if multiple instances of this same TP name are registered on many SNA Server clients, it is difficult to troubleshoot this problem because this event does not indicate the Local APPC LU name that the FMH-5 attach was received. CAUSEThe SNA Server Event 60 was not originally intended to log the Local APPC LU name. 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.0Microsoft 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 STATUSMicrosoft has confirmed this to be a problem in SNA Server 3.0 and 4.0. This problem was first corrected in SNA Server 3.0 Service Pack 4. MORE INFORMATION
With this update applied, the SNA Server now indicates the Local
APPC LU
name within the Event 60 error log.
Additional query words:
Keywords : kbfix4.00.sp1 snaappc snaprog snatp |
Last Reviewed: November 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |