Microsoft KB Archive/236599: Difference between revisions
(importing KB archive) |
(No difference)
|
Latest revision as of 17:08, 18 July 2020
Article ID: 236599
Article Last Modified on 9/22/2005
APPLIES TO
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
- Microsoft SNA Server 4.0 Service Pack 2
This article was previously published under Q236599
SYMPTOMS
While running a Win32 SLI application on SNA Server or an SNA Windows NT client, the application may end unexpectedly with no errors reported in the Windows NT event logs, and no Drwtsn32.log entry created. When this problem occurs, all SNA sessions supported by the application end.
CAUSE
The Winsli32.dll may encounter an access violation in WINSLI32!ipcOutput while processing the session end because of the way it queues RUI responses. No Drwtsn32.log entry is created because the SLI DLL catches the exception within its own exception handler. The key sequence of events is as follows:
- SLI issues RUI_TERM.
- SLI receives the RUI_TERM completion and queues this up.
- The application issues a SLI_RECEIVE, which results in SLI issuing an RUI_READ.
- SLI receives the RUI_READ completion (CANCELED-TERMINATED) and queues it up.
- SLI dequeues the RUI_TERM and frees its session CB and all associated VCBs, including the RUI_READ VCB that has just been queued.
- SLI dequeues the RUI_READ completion causing an access violation.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in SNA Server version 4.0 Service Pack 3.
Keywords: kbbug kbfix kbsna400sp3fix kbqfe kbhotfixserver KB236599