Microsoft KB Archive/188238

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 09:37, 21 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 188238

Article Last Modified on 10/27/2006



APPLIES TO

  • Microsoft SNA Server 3.0 Service Pack 4
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 3.0 Service Pack 2
  • Microsoft SNA Server 3.0 Service Pack 3
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 Service Pack 1



This article was previously published under Q188238

SYMPTOMS

The SNA Server Manage Agent service (MngAgent.exe) may generate an application exception error when APPC sessions are not properly cleaned up. When this problem occurs, the Windows NT Application Event Log will contain a message similar to the following:

   Event ID: 624
   Source: SNA Server
   Description: Creating dump file C:\SNA\traces\snadump.log for
   mngagent.exe



If Drwtsn32.exe is the default debugger on the computer running Windows NT Server and SNA Server, an entry similar to the following will be included in the drwtsn32.log in the Windows NT directory:

   Application exception occurred:
      App: exe\mngagent.dbg (pid=<process ID #>)
      When: <date> @ <time>
      Exception number: c0000005 (access violation)

CAUSE

Partner APPC sessions are not being cleaned up properly when SNA Server receives notification from a client to close an APPC session. This eventually leads to the application exception error.

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 Microsoft 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 that this is a problem in SNA Server versionsSP2, 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 4.0, and 4.0 SP1. This problem was first corrected in SNA Server 3.0 Service Pack 4.

Keywords: kbbug kbfix KB188238