APPC Display Call Fails With AP_STATE_CHECK (Primary_rc = 0002)

 Last reviewed: March 11, 1998
Article ID: Q182265
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0

SYMPTOMS

Occasionally, the APPC DISPLAY function will fail with the following error: 

   primary_rc   = 0x0002 (AP_STATE_CHECK)
   secondary_rc = 0x00000000
This problem seems to occur when two separate DISPLAY calls are made at the same time from two different threads of the same APPC program.

CAUSE

Although the APPC DISPLAY function is implemented in a thread-safe manner, it does not properly handle unsolicited status messages received from the SNA Server, which could cause AP_STATE_CHECK to be returned in error. This problem is not related to issuing separate DISPLAY calls from different threads.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 3.0, 3.0 Service Pack 1 (SP1), and 3.0 SP2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Microsoft has confirmed this to be a problem in SNA Server 4.0. A supported fix is now available for SNA Server 4.0, 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 Technical Support for more information. 

Keywords          : kbbug3.00 kbbug3.00.sp1 snaappc snaprog kbbug3.00.sp2 kbbug4.00 kbnetwork
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.