OPEN SSCP RSP ERROR Returns Err1:000F and Err2:0003Last reviewed: February 3, 1998Article ID: Q179018 |
The information in this article applies to:
SYMPTOMSAn FMI application may fail with unusual error codes (e.g. Err1:000F and Err2:0003) when it receives an OPEN SSCP RSP ERROR response from SNA Server.
CAUSEThere is a problem in the resource location code inside the DMOD. The SNA Server DMOD receives OPEN requests from the application and sends the requests to each SNA Server service respectively. For this to occur, the DMOD has to intercept OPEN responses from the SNA Server services. The DMOD performs an invalid test to determine whether or not an OPEN message is a response. The test does not allow for OPEN PLU CONF OK and CONF ERR messages. The DMOD treats the OPEN PLU CONF OK and CONF ERR messages as if they were OPEN error responses. This causes the DMOD to look into its queue of pending open requests from the application, and by chance, it finds a match. In turn, the DMOD returns the OPEN SSCP RSPERR with unusual error codes like Err1:000F and Err2:0003.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 2.11 SP1, 2.11 SP2, 3.0, 3.0 SP1, and 3.0 SP2. 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. Keywords : kbbug2.11.sp1 kbbug2.11.sp2 kbbug3.00 kbbug3.00.sp1 prodsna kbbug3.00.sp2 kbbuglist Version : WINDOWS:2.11SP1,2.11SP2,3.0,3.0SP1,3.0SP2 Platform : WINDOWS Hardware : x86 Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |