Invokable APPC/CPI-C TP May Fail Intermittently with Event 60 (246794)
The information in this article applies to:
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 3.0 SP4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
This article was previously published under Q246794 SYMPTOMS
An invokable APPC or CPI-C application may fail intermittently. When the failure occurs, an event similar to the following is logged in the Windows NT application log on the SNA Server computer:
Event ID: 60
Source: SNA Server
Description: Failed to invoke APPC TP <TP Name>, sense data = 084C0000
Note: X'084C0000' is an IBM Sense Code that indicates AP_TRANS_PGM_NOT_AVAIL_NO_RETRY.
This problem occurs when an instance of the APPC or CPI-C application stops unexpectedly. In addition, this is most likely to occur if the application issues RECEIVE_ALLOCATE() calls for multiple Transaction Programs (TPs).
If another instance of the application is started after the first one stops, the effect is likely to be that host requests to invoke the application alternates between successful execution and failure. Note: Event 60s are general errors that are logged when an invokable APPC/CPI-C TP cannot be invoked. Therefore, they result for reasons not related to the problem described here.
CAUSE
The SNA Server DMOD fails to mark all TPs registered by a process (for example APPC or CPI-C application) as inactive when the process stops abnormally. SNA Server may route host ATTACH requests to the TPs that are still marked as active, which results in the problem described above.
RESOLUTIONSNA Server 3.0A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
|
Snadmod.dll | 11/22/99 | 2:40PM | Snashmem.exe | 11/22/99 | 2:41PM | NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
SNA Server 4.0To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Microsoft SNA Server versions 3.0 (all SPs), 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3.
This problem was first corrected in SNA Server 4.0 Service Pack 4.
Modification Type: | Minor | Last Reviewed: | 9/2/2005 |
---|
Keywords: | kbbug kbfix kbQFE kbSNA400PreSP4fix kbSNA400sp4fix KB246794 |
---|
|