PSS ID Number: 272194
Article Last Modified on 5/14/2003
The information in this article applies to:
- Microsoft Windows NT Server, Enterprise Edition 4.0
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP4
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP5
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP6
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP6a
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Workstation 4.0 SP1
- Microsoft Windows NT Workstation 4.0 SP2
- Microsoft Windows NT Workstation 4.0 SP3
- Microsoft Windows NT Workstation 4.0 SP4
- Microsoft Windows NT Workstation 4.0 SP5
- Microsoft Windows NT Workstation 4.0 SP6
- Microsoft Windows NT Workstation 4.0 SP6a
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Server 4.0 SP1
- Microsoft Windows NT Server 4.0 SP2
- Microsoft Windows NT Server 4.0 SP3
- Microsoft Windows NT Server 4.0 SP4
- Microsoft Windows NT Server 4.0 SP5
- Microsoft Windows NT Server 4.0 SP6
- Microsoft Windows NT Server 4.0 SP6a
This article was previously published under Q272194
SYMPTOMS
On a server that has more than 4,094 simultaneous open connections, the following events may be logged:
-and-
Although the event error messages indicate that a non-paged pool may be exhausted, System Monitor usually indicates otherwise.
CAUSE
This problem can occur because some allocations do not work in the server service. The allocations do not work because a calculation error occurred while attempting to grow an endpoint connection table. The calculation error causes a large pool-allocation request that does not work. The allocation does not work when there are approximately 4,094 simultaneous connections.
Note: Typically, the circumstances that are described in this section do not cause the Event 2019 event message. Typically, non-paged pool leaks cause it. The fix that this article describes does not resolve or prevent memory leaks.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English-language version of this fix should have the following file attributes or later:
Date Time Size File name Platform
---------------------------------------------------
10/10/2000 4:39:34 PM 450 KB Srv.sys Alpha
10/10/2000 4:41:30 PM 225 KB Srv.sys Intel
Note: The Srv.sys file can be located in the %systemroot%/system32/drivers folder.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kberrmsg kbfix kbprb KB272194
Technology: kbWinNT400search kbWinNTS400 kbWinNTS400search kbWinNTS400sp1 kbWinNTS400sp2 kbWinNTS400sp3 kbWinNTS400sp4 kbWinNTS400sp5 kbWinNTS400sp6 kbWinNTsearch kbWinNTSEnt400 kbWinNTSEnt400sp4 kbWinNTSEnt400sp5 kbWinNTSEnt400sp6 kbWinNTSEnt400SP6a kbWinNTSEntSearch kbWinNTSsearch kbWinNTW400 kbWinNTW400search kbWinNTW400sp1 kbWinNTW400sp2 kbWinNTW400sp3 kbWinNTW400sp4 kbWinNTW400sp5 kbWinNTW400sp6 kbWinNTW400SP6a kbWinNTWsearch
