SNARAS Goes Into Infinite Loop When Invalid Msg Type Is Received (196238)

SYMPTOMS

SNARAS may stop responding (hang) after a port is disconnected. SNARAS internal traces show that it has entered an infinite loop.

RESOLUTION

SNA Server 3.0

To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack

SNA Server 4.0

This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

STATUS

Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. This problem was first corrected in SNA Server 3.0 Service Pack 4.

MORE INFORMATION

The following is an excerpt of SNARAS internal trace that was captured while the service was in this infinite loop:

rassna.c 2857 SriCallback-message at 0x0021C2E0 of type 1311224 with rc 22 rassna.c 2942 SriCallback: Bad message 1311224 rassna.c 2944 SriCallback: Send Internal Error Response rassna.c 2857 SriCallback-message at 0x0021C2E0 of type 1311224 with rc 22 rassna.c 2942 SriCallback: Bad message 1311224 rassna.c 2944 SriCallback: Send Internal Error Response rassna.c 2857 SriCallback-message at 0x0021C2E0 of type 1311224 with rc 22 rassna.c 2942 SriCallback: Bad message 1311224

This is a deadlock situation with repeated occurrences of the rc=22 error.