This article was previously published under Q259148
This article has been archived. It is offered "as is" and will no longer be updated.
Under stress, Microsoft Exchange or other programs may stop working and may generate Dr. Watson error messages ("Access violation").
If symbols are installed, the stack traces in the Dr. Watson log show that the problem occurs near the EnumProtocolsW function. The stack traces may vary in different situations. Two sample stack traces are listed here:
The EnumProtocols function in Windows Sockets (Mswsock.dll) is calculating a buffer length incorrectly, resulting in heap corruption.
To resolve this problem for Windows 2000, obtain the latest service pack for Windows 2000. For additional information, please see the following article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Windows NT 4.0
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.
To resolve this problem, 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform ----------------------------------------------- 21/03/00 21:48 76,560 Mswsock.dll Intel 21/03/00 21:48 20,752 Wsock32.dll Intel 21/03/00 21:46 120,592 Mswsock.dll Alpha 21/03/00 21:46 25,360 Wsock32.dll Alpha
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows 2000 Service Pack 1.
Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition