The information in this article applies to:
SYMPTOMSAn APPC or CPI-C application may receive the following error message when it issues a TP_STARTED call that informs the APPC library that the TP (Transaction Program) is starting: The following is an excerpt of a SNA Server APPC API trace that captures the failing TP_STARTED call:
If a CPI-C application is being used when this occurs, the following error message is returned by the CPI-C library after it receives the THREAD_BLOCKING error from the APPC library:
NOTE: There might be other reasons for getting a PRODUCT_SPECIFIC_ERROR(20) that are not necessarily related to this article. Further reasons for getting a PRODUCT_SPECIFIC_ERROR(20) can be found in Microsoft Knowledge Base articles by searching for "CM_PRODUCT_SPECIFIC_ERROR". This problem can occur when an APPC or CPI-C application has previously called WinAPPCCleanup or WinCPICCleanup to deregister the application from the APPC or CPI-C library. If the application subsequently calls WinAPPCStartup or WinCPICStartup to reregister the application, the next APPC or CPI-C call may fail with the THREAD_BLOCKING error. CAUSE
This problem occurs because the APPC library is not properly clearing the internal IS_BLOCKING flag when WinAPPCCleanup is called. The IS_BLOCKING flag is used by the APPC library to determine whether another APPC blocking call is already outstanding on the thread that a next APPC call is being issued on. RESOLUTIONA 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. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
NOTE: Date and time information will be provided as soon as it becomes available. NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files. WORKAROUNDModify the APPC or CPI-C application such that it only calls the WinAPPCStartup/WinAPPCCleanup or WinCPICStartup/WinCPICCleanup sequence once for each process startup or termination. STATUSMicrosoft has confirmed this to be a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2. Additional query words:
Keywords : sna3 sna3sp1 sna3sp2 sna3sp3 sna3sp4 sna4 sna4sp1 sna4sp2 |
Last Reviewed: August 27, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |