July 24, 2008 07:21pm pdt

Member Login

Top Experts

Yearly

1KCTS 709,274
2LauraEHu... 453,444
3Chris-Dent 287,215
4tigermatt 285,817
5Jay_Jay70 209,314
6oBdA 206,545
7toniur 135,882
8henjoh09 129,531
9martin_b... 120,001
10ChiefIT 116,432
11ryansoto 109,634
12Netman66 106,050
13RobSamp... 97,570
14leew 93,877
15Sembee 93,144

null

	[x] Attachment Details

Delay write failed - Windows was unable to save all the data for the file \Device\LanmanRedirector

Zones: Active Directory, Windows 2003 Server

Tags: Microsoft, Office, Office XP

I have seen many with problems with delay write failed, and one solution that comes back is this one - http://support.microsoft.com/default.aspx?scid=kb;en-us;321733

Do anyone know if this would apply for 2003 terminalservers connected to a 2003 DC/File server. The solution spesifies Windows XP or 2000.

My scenario is 3 TS and this error often occurs at the same time on at least two of the servers. Will also try the chkdisk command, but Dell Open Management states no error on the file sever.

Can it also be the switch or the network cards!?!

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:

           
           
             Event Type:	Warning
Event Source:	MRxSmb
Event Category:	None
Event ID:	50
Date:		1/21/2008
Time:		10:51:18 AM
User:		N/A
Computer:	TS03
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.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 56 00   ......V.
0008: 00 00 00 00 32 00 04 80   ....2..
0010: 00 00 00 00 0c 02 00 c0   .......À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 0c 02 00 c0               ...À
           
         

Start your free trial to view this solution

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.2

Question Stats

Zone: OS

Question Asked By: dunkapunk

Solution Provided By: PlaceboC6

Participating Experts: 1

Solution Grade: B

Translate:

Loading Advertisement...

Open Discussion

null

Comment by dunkapunk

Actually things are much better now after I applied SP2 on the TS as well. But I have not yet tried the
"Netsh int ip set chimney DISABLED" - what does this actually do? I would like to try this as well if the problem comes back, but I will try one thing at the time so I know what solves the problem.

null

Comment by PlaceboC6

The chimney includes technologies such as Receive Side Scaling and TCP Offload. TCP Offload is designed to offload network operations from the CPU and on to the network card. Only newer network cards support this. Say in the last 1.5-2 years.

I've seen these features cause performance and connectivity issues on servers many times. So if you continue to have wierd issues, try that command and see if it helps. You're not really losing anything by turning it off.

20080723-EE-VQP-34 / EE_QW_2_20070628