SNA Server Event 60 Should Log Local APPC LU NameLast reviewed: March 11, 1998Article ID: Q182268 |
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:
Event ID: 60 Source: SNA Server Description: Failed to invoke APPC TP <name> (<hex name>), sense data = <sense code> EXPLANATION An 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: AP_ALLOCATION_ERROR. The sense data shown is the secondary return code, which will be one of the following hexadecimal values: [ other sense codes not shown ] X'084C0000' AP_TRANS_PGM_NOT_AVAIL_NO_RETRYHowever, 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.
STATUSMicrosoft has confirmed this to be a problem in SNA Server 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.
MORE INFORMATIONWith this update applied, the SNA Server now indicates the Local APPC LU name within the Event 60 error log. The updated modules for the SNA Server computer (this is not necessary on the SNA Server NT client computer) are as follows:
<snaroot>\system\snaservr.exe <snaroot>\system\snaevent.dll Keywords : snaappc snaprog snatp Version : WINDOWS:4.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |