The SNABase Service continuously generates event 561 errors (839197)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1

INTRODUCTION

This article describes how to prevent the SNABase Service from logging event 561 errors with a return code of 53 to the Microsoft Windows application event log. It is helpful to understand how to use the Microsoft Host Integration Server 2000 SNA Manager interface.

MORE INFORMATION

By default, all server broadcasts are enabled (Named Pipes, IPX/SPX, TCP/IP, and Banyan Vines) in Microsoft Host Integration Server 2000. Therefore, the following Windows event 561 error may be logged many times:
Event Type:	Warning Event 
Source:	SNA Base Service 
Event Category:	None 
Event ID:	561 
Date:		Date 
Time:		Time 
User:		User 
Computer:	Computer 
Description: Write to mailslot or socket failed, rc = 53  

EXPLANATION 
A Win32 WriteFile() or winsock sendto() call failed. The return code is shown.  

ACTION 
Provide network support personnel with the event log file(s) related to SNA, and 
the return code included in this message. For information about SNA log files, see 
the "Microsoft Host Integration Server Online Books."
The event is generated from the source SNABase Service. Error code 53 means "the network path was not found." This event with return code 53 is common when Host Integration Server 2000 is configured to broadcast protocols that are not supported on the network. Host Integration Server 2000 computers communicate with each other by using mailslot or datagram broadcast messages. As part of the broadcast, the SNABase Service keeps track of names of servers, client computers, and available transaction programs. To prevent additional logging of the event and error code, disable all irrelevant network transports for server broadcasts. To do this, follow these steps:
  1. Open SNA Manager.
  2. Right-click the SNA Subdomain name, and then click Properties.
  3. Click the Server Broadcasts tab.
  4. Click to clear all irrelevant network transports (typically, TCP/IP is the only protocol that is selected).
Although Microsoft Windows supports multiple protocols at the same time, you do not have to send the same Host Integration Server 2000 broadcasts over all available protocols. You can use the SNA Manager interface to specify the network protocol for server broadcasts.

You must make sure that one common protocol is available on each of the Host Integration Server 2000 computers that are in the SNA subdomain and then use that protocol for server broadcasts. You must also first install the protocol (for example, IPX/SPX, Netbeui, TCP/IP, and other possible protocols) before Host Integration Server 2000 will send a broadcast over that protocol.

REFERENCES

For additional information about event ID 561 in SNA Server 4.0, click the following article number to view the article in the Microsoft Knowledge Base:

321079 SNABase Service may not start properly with Events 561 and 624

Modification Type:MinorLast Reviewed:5/4/2005
Keywords:kbinfo KB839197 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.