https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/168546&feed=atom&action=history
Microsoft KB Archive/168546 - Revision history
2024-03-29T13:21:06Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/168546&diff=88286&oldid=prev
3155ffGd: importing KB archive
2020-07-18T15:34:03Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB168546"></span>Access Violation May Occur After Upgrading to 3.0 SP1 =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 168546<br />
<br />
Article Last Modified on 6/24/2004<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SNA Server 4.0, when used with:<br />
** Microsoft Windows NT 4.0<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
This article was previously published under Q168546<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
<br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
After upgrading SNA Server 3.0 with Service Pack 1, the SnaBase or SNA Server service may fail unexpectedly with an access violation or SNA Server may unexpectedly stop accepting new client connections. This problem can occur if SNA clients are connecting to the server over MS Networking (named pipes) or Netware IPX/SPX. A Drwtsn32.log entry may be generated when this failure occurs, indicating a FAULT in the top-level routine along with the following stack-back trace (which may vary):<br />
* snalm!QueueBuffer<br /><br />
<br /><br />
or<br />
* ntdll!RtlAllocateHeap<br /><br />
snalm!GetReadBuffer<br /><br />
snalm!AceptConnection<br /><br />
snadmod!AcceptClientConnection<br /><br />
snadmod!DMODServiceThread<br /><br />
<br /><br />
or<br />
* ntdll!RtlDestroyHeap<br /><br />
ntdll!RtlFreeHeap<br /><br />
snalm!CleanupConnection<br /><br />
snalm!CloseConnection<br /><br />
snadmod!CloseLtab<br /><br />
snadmod!IoThread<br /><br />
<br /><br />
or<br />
* security!NtLmSspControl<br /><br />
security!DeleteSecurityContext<br /><br />
snalm!CleanupSecurityContext<br /><br />
snalm!CloseConnection<br /><br />
snadmod!sepdnhpe<br />
<br />
If new clients cannot connect, the SNA Server or SnaBase internal trace may indicate the following error after accepting a new client connection:<br />
<div class="errormessage"><br />
<br />
ACCPT HeapAlloc failed, rc 0<br />
<br />
</div><br />
<br />
</div><br />
<div class="cause_section"><br />
<br />
== CAUSE ==<br />
<br />
SnaBase or SNA Server memory local heap corruption is occurring within the IO completion port handling of named pipe or IPX/SPX clients.<br />
<br />
</div><br />
<div class="resolution_section"><br />
<br />
== RESOLUTION ==<br />
<br />
The SNA Server has been updated to correct this problem.<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed this to be a problem in Windows NT SNA Server version 3.0 Server Pack 1. This problem was corrected in the latest SNA Server version 3.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):<br />
<div class="indent"><br />
<br />
S E R V P A C K<br />
<br />
<br />
</div><br />
<br />
</div><br />
Keywords: kbbug kbfix kbnetwork KB168546<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd