Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event ID: 26 occurs when you log off from a server that has Terminal Server enabled in Windows Server 2003 SP1


View products that this article applies to.

Symptoms

When you log off from a server that has Terminal Server enabled in Microsoft Windows Server 2003 Service Pack 1 (SP1), an event that resembles the following may be logged in the System event log:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 8/12/2005
Time: 7:33:18 PM
User: N/A
Computer: TSSERVERNAME
Description: Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file \;V:Shared\Username\IE\index.dat. 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.

This problem occurs when the My Documents folder is redirected to a remote shared directory.

↑ Back to the top


Cause

This problem occurs because the Microsoft Window Redirector closes the network connection to the file server before the Window Redirector closes the handle to the file.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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

To apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Mrxsmb.sys5.2.3790.2587436,22408-Dec-200503:52x86
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Mrxsmb.sys5.2.3790.25871,168,38408-Dec-200504:34IA-64
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Mrxsmb.sys5.2.3790.2587784,38408-Dec-200504:34x64

↑ Back to the top


Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbautohotfix, kberrmsg, kbexpertiseinter, kbbug, kbfix, kbHotfixServer, kbqfe, kbwinserv2003presp1fix, kbwinserv2003sp2fix, KB891194

↑ Back to the top

Article Info
Article ID : 891194
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 339