Microsoft KB Archive/106524

From BetaArchive Wiki
Knowledge Base

Article ID: 106524

Article Last Modified on 12/8/2003


  • Microsoft SNA Server 2.0, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 2.1, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 3.0, when used with:
    • Microsoft Windows NT 4.0

This article was previously published under Q106524


SNA Server generates a Dr. Watson error in SNABASE.EXE when it receives an invalid message over a Named Pipe connection from a client. The SNA Server also logs an Event ID 624 in the Windows NT Application Log (as shown in the Event Viewer) indicating that an SNADUMP.LOG was created for SNABASE.EXE. The following is an excerpt from a DRWTSN32.LOG that is created following one of these SNABASE errors:

Application exception occurred:
App: snabase.DBG (pid=148)
When: 10/31/1995 @ 11:29:1.2
Exception number: c0000005 (access violation)

NOTE: Your DRWTSN32.LOG file will appear somewhat different than this example.


SNABASE.EXE on the SNA Server is not properly handling an invalid incoming NewPipe messages from SNA Server clients over Named Pipe connections. The NewPipe messages are only sent to the SNA Server when the WNAP (16-bit) or SNABASE (32-bit) process is initializing on SNA Server clients.


Microsoft has updated the following files to correct this problem:


These corrected files increase validity checking on incoming NewPipe messages received from clients over Named Pipe connections as well as the other client/server protocols supported by SNA Server. In addition, SNA Server now logs an Event 631 in the Application Log when it receives an invalid NewPipe message from a client.


Microsoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):



For Win 3.x clients, a potential workaround is to start WNAP in advance (by adding WNAP.EXE to the startup group of Windows or Windows for Workgroups), so that it's not automatically invoked when an SNA application or emulator is started.

Additional query words: prodsna

Keywords: kbbug kbnetwork KB106524