SNA Server May Fail to Log Event 624 and Create Snadump.log

• Microsoft SNA Server, versions 3.0, 3.0 SP1, and 3.0 SP2

SYMPTOMS

When SNA Server or an SNA application ends abnormally due to an access violation or internal breakpoint, SNA Server normally logs an Event 624 and produces an Snadump.log file in the <snaroot>\traces directory, to assist support personnel in diagnosing problems. In some cases, SNA Server fails to log an Event 624 and produce an Snadump.log file.

CAUSE

In some cases, the SNA Server exception handling code was failing to produce an <snaroot>\traces\snadump.log following an access violation or unhandled exception in an SNA Server module.

STATUS

Obtain the following fix or wait for the next SNA Server 3.0 service pack.

This fix should have the following timestamp:

   11/21/97  10:57a        9,600  <snaroot>\system\snadump.dll
   11/21/97  10:57a        9,840  <ntroot>\symbols\dll\snadump.dbg

Microsoft has confirmed this to be a problem in SNA Server version 3.0, version 3.0 Service Pack 1, and version 3.0 Service Pack 2. 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 Technical Support for more information.

Keywords          : kbbug3.00 kbbug3.00.sp1 snabaseservice snaserverservice snawinnt kbbug3.00.sp2 kbbuglist
Version           : WINDOWS:3.0,3.0SP1,3.0SP2
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix