Solved

Resource Limit Error

Posted on 1998-09-22
2
292 Views
Last Modified: 2013-12-28
On my exchange server, I get the following error in my event log:  Resource limit reached while attempting to open an association.  There were no free control blocks available for net type 1 Base IL TCP/IP Driver 8 282 (10).

Do I need to raise a limit in the registry somewhere or is this an environment variable?  Any help would be appreciated.  
0
Comment
Question by:thamlin
2 Comments
 
LVL 5

Accepted Solution

by:
Mujeeb082598 earned 100 total points
ID: 1792868
Hi :)

This will clear any doubts u have.

PSS ID Number: Q166602
Article last modified on 04-17-1998
 - Microsoft Exchange Server versions 4.0, 5.0
---------------------------------------------------------------------
 
SYMPTOMS
========
 
The Microsoft Exchange Server message transfer agent (MTA) has a limit on
the number of allowed socket control blocks for TCP and TP4. This limit is
currently a shared maximum of 64 (0x40). The minimum number that must be
allocated to either TCP or TP4 is 2, which means that the maximum any one
transport stack can have allocated is 62 (0x3E). The default is set to 20
(0x14) for each.
 
When the limit is reached, the following error message is logged in the
Windows NT event log:
 
   MSExchangeMTA   Warning   Resource   9156
   A resource limit has been reached while attempting to open an
   association. There are no free control blocks available for network type
   1. The configured count is 40. [BASE IL MAIN BASE 1 282] (10)
 
STATUS
======
 
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 4.0.
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.
 
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 5.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 5.0. For information on
obtaining the 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
================
 
The MTA uses one control block for each connection (whether remotely or
locally initiated). It also uses one to listen for incoming connections.
 
If slow links (slower than 128Kbps) and/or large messages are involved and
message backlogging is therefore likely, you can allow 10 control blocks
per X.400-Link. This enables MTA traffic to be handled more efficiently by
virtue of multiple connections to each remote link, without suffering from
a resource shortage.
 
NOTE: There is no requirement to change the TP4 Thread or TCP/IP Thread
values; the code will self-adjust based on the count of control blocks.
 
The following registry values hold the TCP/IP and TP4 control block
settings:
 
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\
   Services\MSExchangeMTA\Parameters\TCP/IP Control blocks
 
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\
   Services\MSExchangeMTA\Parameters\TP4 Control blocks
 
With the fix implemented, a maximum total of 2,000 control blocks is
allowed.

0
 

Author Comment

by:thamlin
ID: 1792869
Thanks
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An article on effective troubleshooting
This article summaries thoughts and ideas from two years of sustained use. It provides good reasoning to make the jump to Windows 10.
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question