Microsoft KB Archive/245080

= Receiving Multiple Instances of Event ID 2022 =

Article ID: 245080

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT 4.0 Service Pack 1
 * Microsoft Windows NT 4.0 Service Pack 2
 * Microsoft Windows NT 4.0 Service Pack 3
 * Microsoft Windows NT 4.0 Service Pack 4
 * Microsoft Windows NT 4.0 Service Pack 5
 * Microsoft Windows NT 4.0 Service Pack 6

-



This article was previously published under Q245080



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When you are using a computer running Windows, you may receive the following error message:

Event 2022: Server was unable to find a free connection 1 times in the last 60 seconds.



CAUSE
This behavior occurs because the Server service is unable to keep up with the demand for connections.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this issue, use the following steps:  Start Registry Editor (Regedt32.exe). Locate and click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

 On the Edit menu, click Add Value, and then add the following registry value:

Value Name: MaxFreeConnections

Data Type: REG_DWORD

Value: Any Value Up to 100 (in decimal)

 On the Edit menu, click Add Value, and then add the following registry value:

Value Name: MinFreeConnections

Data Type: REG_DWORD

Value: Any Value Up to 32 (in decimal)

 Quit Registry Editor.</ol>

NOTE: You must restart the computer for the changes to take effect.

<div class="moreinformation_section">

MORE INFORMATION
A special resource task in the Windows service uses the MinFreeConnections and MaxFreeConnections value settings to preallocate connection objects. Under certain conditions, the demand for preallocated connection objects may exceed the default number configured in the MinFreeConnections and MaxFreeConnections value settings.

However, you may also receive the "Event 2022" error message due to certain system problems (for example, if the computer stops responding). You should correct any system problems before you consider changing the MinFreeConnections and MaxFreeConnections value settings.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

245077 Computer Stops Responding with Event ID 2022

The following list shows the default MinFreeConnections and MaxFreeConnections values for each Server service optimization setting. <ul> Minimize Memory Used <ul> MinFreeConnections = 2</li> MaxFreeConnections = 2</li></ul>

</li> Balance <ul> MinFreeConnections = 2</li> MaxFreeConnections = 4</li></ul>

</li> Maximize Throughput for File Sharing <ul> MinFreeConnections = 4</li> MaxFreeConnections = 8</li></ul>

</li> Maximize Throughput for Network Applications <ul> MinFreeConnections = 4</li> MaxFreeConnections = 8</li></ul> </li></ul>

For additional information about how to use the Windows registry to optimize Windows, click the article number below to view the article in the Microsoft Knowledge Base:

232271 How to Optimize Windows NT Server Using the Registry

Additional query words: hang

Keywords: kbenv kberrmsg kbprb KB245080

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.