Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172635

From BetaArchive Wiki
Knowledge Base


Article ID: 172635

Article Last Modified on 6/29/2004



APPLIES TO

  • Microsoft SNA Server 3.0
  • Microsoft SNA Server 3.0 Service Pack 4
  • Microsoft SNA Server 4.0



This article was previously published under Q172635


SYMPTOMS

If the SnaBase or SnaServer services fail with an access violation, the TCP/IP socket ports that they use may not be cleaned up properly. When you attempt to restart the SnaBase or SnaServer service, you will see the following error logged in the event viewer:

Event ID: 567
Description: Creation of a named pipe failed, rc = 10048, pipe = <socket
number>

The 10048 error corresponds to Winsock error WSAEADDRINUSE (address in use). After this problem occurs, the server must be restarted in order to restart SNA Server.

CAUSE

If SnaBase or SnaServer encounters an access violation, it leaves some sockets in the open state. NOTE: You must still investigate the original cause of the access violation. Open a case with Microsoft Product Support Services, and provide the following information:

<Ntroot>\Drwtsn32.log
<Snaroot>\Traces\Snadump.log
Windows NT application logs
System event logs


STATUS

Microsoft has confirmed this to be a problem in SNA Server version 2.11.

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 and 3.0 Service 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):

S E R V P A C K


MORE INFORMATION

With the fix applied, SNA Server cleans up the sockets in the top-level exception handler supported by Snadmod.dll. The cleanup will always happen, provided the exception handler is invoked, and services can be restarted without restarting the computer in such situations.

Keywords: kbbug kbfix kbnetwork KB172635