SNA Service Table Objects Increased from 1 KB to 4 KB (276242)



The information in this article applies to:

  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 SP1
  • Microsoft SNA Server 4.0 SP2
  • Microsoft SNA Server 4.0 SP3

This article was previously published under Q276242

SYMPTOMS

On an SNA Server or Microsoft Windows NT workstation that is running the SNA Windows NT client software, the following event may be posted in the application log of the event viewer:
Event ID: 563

Description: The service table is full: too many network resources active
These events are typically seen on SNA Servers where many different SNA clients are running transaction programs (TPs) that can be invoked.

CAUSE

The Service Table (ST) has reached the maximum objects allowed.

RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in SNA Server versions 4.0, 4.0 SP1, 4.0 SP2, 4.0 SP3.

This problem was first corrected in SNA Server 4.0 Service Pack 4.NOTE: There is no hot fix for SNA Server 3.0, however this feature is included in Host Integration Server 2000. This feature only applies to SNA Server and the SNA WinNT client, not the SNA Windows 95 or Windows 98 client.

MORE INFORMATION

All SNA Server services and resources are required to register themselves in the SNA Service Table. All SNA Servers (and SNA clients) have there own ST that is used internally to manage the resources that are being used on that computer. Because the ST is a dynamic-memory allocated table, the SNA Server service (and SNA clients) locates the needed services through the ST within that current SNA Server subdomain. Some examples are:
  • One entry for every SNA Server service that is running in the domain.
  • One entry for every SNA Server configuration server (SnaBase) that is running in the domain (that is, primary and back-up servers).
  • One entry for each active Windows process that uses the client API interfaces (for example, the 3270 and 5250 Applets each take one entry).
  • One entry for every TP that can be invoked that is registered on the client computer.

Modification Type:MinorLast Reviewed:12/29/2003
Keywords:kbbug kbfix kbSNA400PreSP4fix kbSNA400sp4fix KB276242