Access Violation in Masfd.dll Results from Using Winsock Direct Path to Communicate with Storage Area Network

This article was previously published under Q289229
This article has been archived. It is offered "as is" and will no longer be updated.
When you are using a server application such as Internet Information Services (IIS), which is included with Windows 2000, and you try to communicate with a Storage Area Network by using the Winsock Direct path, an access violation occurs in Masfd.dll.
This behavior can occur when an overlapped TransmitFile is done with the REUSE flag but the socket is closed before the socket REUSE processing is complete.

This behavior only occurs with the Winsock Direct path. It does not occur with the regular TCP/IP code path of Masfd.dll.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Microsoft has confirmed that this is a problem in Microsoft Windows 2000.

This problem was first corrected in Windows 2000 Service Pack 2.
race condition assert

Article ID: 289229 - Last Review: 10/23/2013 16:28:13 - Revision: 3.2

Microsoft Windows 2000 Service Pack 1, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Service Pack 1

  • kbnosurvey kbarchive kbbug kbfix kbwin2000presp2fix kbnetwork kbprogramming KB289229
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)