The information in this article applies to:
SYMPTOMSAn 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: 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. CAUSEThe 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 that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems 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 on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files. SNA Server 4.0A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this fix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files. STATUSMicrosoft has confirmed this to be a problem in Microsoft SNA Server versions 3.0 (all SPs), 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3. MORE INFORMATION
After you apply the update, the DMOD searches the service table to locate all TPs that were registered by the process using the Process ID (PID) of the stopped process to ensure that all of the TPs used by that process are marked as no longer in use.
Additional query words:
Keywords : sna3 sna3sp1 sna3sp2 sna3sp3 sna3sp4 sna4 sna4sp1 sna4sp2 sna4sp3 |
Last Reviewed: November 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |