Delayed Write Failed -- \Device\LanmanRedirector

[William Stokes]

Hello,

We have had problems with one application (Lotus Notes) which use files on a
network share. Basically the application crashes and after that theres this
message in the system event log:

Source: MRxSmb
EventID:50
"Windows - 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."

I googled this error up and found this MS article:
http://support.microsoft.com/default...b;en-us;321733. This,
however doesn not apply to our workstations cause we already use XP SP2 in
which this error should be fixed. Also we already have the registry setting
described in the workaround.

I upgraded our network switches to 1GB devices (HP 2900 series) this spring
and these errors started to appear about the same time so I think that it's
fair to assume that this has got something to do with this? Otherwise the
network itself seems to be ok. Workstations and servers are connected at 1Gb
speed. File shares, apps and pings work ok across the network. Theres no
errors in the switch logs. Only network errors I can find are in the XP
clients system log. Network files that the problem software use are on a
Win2003R2 server. Files are personal to each user so they have full rights
to them and since these are personal files this is not a sharing violation
(=file locked by another user). I already talked to software vendor (IBM)
and their opinnion was that this is a network problem. Our hardware
(WS's/SRV's) is less than a year old so all network adapters and drivers
should be up to date.

At some workstations this error can also be seen in the system log (not so
often as the MRxSmb error):
EVENT ID 4226, TCP/IP has reached the security limit imposed on the number
of concurrent TCP connect attempts.
Could it be that in 1Gb network the restriction on 10 incomplete outbound
TCP connetions is too low??

Any idea how to troubleshoot this MRxSmb error further?

Thanks
-Will

[jim harris]

I too, have been stymied with this Delayed Write issue very similar to yours - new 1GB network with XP SP2.

Have you found a solution yet ?


You are not following a thread, so we can't know what you are referring to..

[TheOtherGuy]

The locking and delayed write errors are probably caused by opportunistic locking.

The link below has the registry entries needed to disable. I suggest disabling on the server and on the workstation.

http://support.microsoft.com/kb/296264

Note: The keys and values do not exist and have to be created and you will have to restart the machines after making the registry entries.

Nosnjectn,

I was able to resolve this for my client by disabling opportunistic locking.

The customer has been error and lock up free for over a year now.

[Nosnjectn]

Will,
i too am having this problem, i have been working with MS, EMC, Dell, as well as our internal Tier 1 team. nobody seems to know what the issue is. were you able to resolve it and if so how?

i followed those instructions from MS and disables O locks on the server. the entry was not even present in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters path. so i created a new DWORD entry in the parameters folder and set it to 0. rebooted, and today the users are still having the issue.

so now i am so the same on the client side (according to that article) i am going to choose 5 users and disable O locks on their end and see how it goes.

if this does not work that i don't know what the hell to try next. i mean MS doesn't have a solution and we pay GOOD $$$ for support.

i attached a word doc that has 2 screen prints. the error on the users desktop and the event log from the users event viewer

the server is a standard install of windows 2K3 STD and the users are windows XP with latest SP and updates.

any other suggestions would be appreciated.

Thanks,
Dave

OMG let's try that in English

-so now i am going to do the same on the client side
-if this does not work than i don't know what the hell to try next

Mel,

we originally started with everything set to auto and during out troubleshooting we even tried hard coding it.

we have a VOIP network, each user has 2 network jacks at their desks. 1 jack goes to an Enteresys switch (not part of VOIP network). the 2nd jack is connected to a Cisco POE switch (which is our VOIP network) we have tried both, hard coded and auto. both failed.

we also tried disabling the NIC TEAM, no good. Dell said the server is perfect and all up to date. EMC said the storage array is perfect no errors anywhere.

per MS we disabled "IPv4 large send Offload" and "Receive Side Scaling" on both NIC cards on the server this did not work either (FYI the server is a Dell PE1950) brand new. Array is Clarion.

HELP ME PEOPLE!!!!!!!! LOL

[Mel K.]

Check the network duplex/speed settings. If you're on GbE, then set
EVERYTHING to auto unless you have a very good reason to hardcode the
settings. I had the same error with our EMC and setting it to auto resolved
the issue.

[moncho]

Been down this road too.

Have you tried replacing the cabling, making sure each
machine and switch is on a UPS, removed software like
Norton and hard coding the NIC speed settings?

The solution for my client was a combination of
removing Norton (NOT just disabling it) and
a new Cat5 cable for the server.

moncho