A program may stop responding, and event 50 and event 26 are logged, when the program tries to write data to a volume mount point on a Windows Server 2003-based computer

When a program that is running on a Microsoft Windows Server 2003-based computer tries to write data to a volume mount point, your program may stop responding. The following events are logged to the System log:

Event message 1

Event Type: Warning
Event Source: MRxSmb
Event ID: 50
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file \Device\LanmanRedirector. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Event message 2

Event Type: Information
Event Source: Application Popup
Event ID: 26
Description:
Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file \\ServerName\VolumeMountPointName\FileName. This data has been lost. This error may be cause by a failure on your computer hardware or network connection. Please try to save this file elsewhere.

This problem occurs when the program writes to a volume mount point that is located on a storage area network (SAN) that is connected by using a Universal Naming Convention (UNC) connection.

Note This problem does not occur when the program writes to a volume that is connected by using a drive letter mapping.

This problem occurs because data transfers from the client to the server do not progress. Subsequently, Windows disconnects from the volume mount point. Therefore, Windows cannot write to the volume mount point.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, 32-bit versions

Windows Server 2003, Enterprise Edition for Itanium-based Systems

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about mount point volumes, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: