MRxSMB : Delayed Write Failed (ID 50)

[denis@must-computer.com]

Hello everybody,

I have random network problems between a Windows 2003 Server (SP1)
(with Active Directory) and 2 Windows XP Pro (SP2) workstations working
with network shares on the server.

The workstations and the server are randomly "disconnected" and the
workstations receive an error message saying "Delayed Write Failed". In
the event log of the workstations, we can see an id 50 "MRxSmb" and an
id 26 "Application Popup" (= the message we have just received). On the
server, there is nothing in the event log. The other Windows 2000 pro
workstations are still working fine without any problem.

I have tried a lot of solutions found on the internet, including :
- Microsoft KB 890352 and 321733
- modifcation of the values for "enablesecuritysignature" and
"requiresecuritysignature" in lanmanserver and lanmanworkstation (both
on xp workstations and server)
- changing the value for the network link speed from "auto-negociate"
to "100 Mbtis Full Duplex" or "100 Mbits Half Duplex" (both on xp
workstations and server)

But the problem is still present.

I hope some people will be able to help me. So thank your very much in
advance !

Best regards,

Denis

PS : I'm sorry for mistakes I made in english. I'm a french native
speaker.

[denis@must-computer.com]

Any idea ?

Please help :-)

Best regards,

Denis

denis@must-computer.com a écrit :

> Hello everybody,
>
> I have random network problems between a Windows 2003 Server (SP1)
> (with Active Directory) and 2 Windows XP Pro (SP2) workstations working
> with network shares on the server.
>
> The workstations and the server are randomly "disconnected" and the
> workstations receive an error message saying "Delayed Write Failed". In
> the event log of the workstations, we can see an id 50 "MRxSmb" and an
> id 26 "Application Popup" (= the message we have just received). On the
> server, there is nothing in the event log. The other Windows 2000 pro
> workstations are still working fine without any problem.
>
> I have tried a lot of solutions found on the internet, including :
> - Microsoft KB 890352 and 321733
> - modifcation of the values for "enablesecuritysignature" and
> "requiresecuritysignature" in lanmanserver and lanmanworkstation (both
> on xp workstations and server)
> - changing the value for the network link speed from "auto-negociate"
> to "100 Mbtis Full Duplex" or "100 Mbits Half Duplex" (both on xp
> workstations and server)
>
> But the problem is still present.
>
> I hope some people will be able to help me. So thank your very much in
> advance !
>
> Best regards,
>
> Denis
>
> PS : I'm sorry for mistakes I made in english. I'm a french native
> speaker.

[Anthony]

Does it happen with any random write, or only with a particular application?
Anthony


<denis@must-computer.com> wrote in message
news:1156767444.167055.305360@p79g2000cwp.googlegroups.com...
Any idea ?

Please help :-)

Best regards,

Denis

denis@must-computer.com a écrit :

> Hello everybody,
>
> I have random network problems between a Windows 2003 Server (SP1)
> (with Active Directory) and 2 Windows XP Pro (SP2) workstations working
> with network shares on the server.
>
> The workstations and the server are randomly "disconnected" and the
> workstations receive an error message saying "Delayed Write Failed". In
> the event log of the workstations, we can see an id 50 "MRxSmb" and an
> id 26 "Application Popup" (= the message we have just received). On the
> server, there is nothing in the event log. The other Windows 2000 pro
> workstations are still working fine without any problem.
>
> I have tried a lot of solutions found on the internet, including :
> - Microsoft KB 890352 and 321733
> - modifcation of the values for "enablesecuritysignature" and
> "requiresecuritysignature" in lanmanserver and lanmanworkstation (both
> on xp workstations and server)
> - changing the value for the network link speed from "auto-negociate"
> to "100 Mbtis Full Duplex" or "100 Mbits Half Duplex" (both on xp
> workstations and server)
>
> But the problem is still present.
>
> I hope some people will be able to help me. So thank your very much in
> advance !
>
> Best regards,
>
> Denis
>
> PS : I'm sorry for mistakes I made in english. I'm a french native
> speaker.

[Luc Maes]

We are ecountering exactly the same problems, especially with applications
like MS Access or other applications that act as a database.

The clients are running Windows XP SP2.
The file servers are running Windows server 2003. (sp1 has been planned
for the end of the month, KB 890352 is already installed).

The application writes to a SAN volume that is connected by using a drive
letter mapping. Randomly, the application stops responding and event 50 and
26 are logged.

--
Luc


"denis@must-computer.com" wrote:

> Hello everybody,
>
> I have random network problems between a Windows 2003 Server (SP1)
> (with Active Directory) and 2 Windows XP Pro (SP2) workstations working
> with network shares on the server.
>
> The workstations and the server are randomly "disconnected" and the
> workstations receive an error message saying "Delayed Write Failed". In
> the event log of the workstations, we can see an id 50 "MRxSmb" and an
> id 26 "Application Popup" (= the message we have just received). On the
> server, there is nothing in the event log. The other Windows 2000 pro
> workstations are still working fine without any problem.
>
> I have tried a lot of solutions found on the internet, including :
> - Microsoft KB 890352 and 321733
> - modifcation of the values for "enablesecuritysignature" and
> "requiresecuritysignature" in lanmanserver and lanmanworkstation (both
> on xp workstations and server)
> - changing the value for the network link speed from "auto-negociate"
> to "100 Mbtis Full Duplex" or "100 Mbits Half Duplex" (both on xp
> workstations and server)
>
> But the problem is still present.
>
> I hope some people will be able to help me. So thank your very much in
> advance !
>
> Best regards,
>
> Denis
>
> PS : I'm sorry for mistakes I made in english. I'm a french native
> speaker.
>
>

[dlavrichev]

We had this problem as well. The most interestig part is that it appeared as soon as I moved the server to another network switch. In my case changing network card settings (from auto to 100 MBps/Full) made it even worse - the connection to the file server became very slow. Even moving clients and server on the same network switch did not help. Therefore, I moved my clients and server to another switch (I have 3Com 24 port Gigabit switch) and this problem disappeared right away. My final conclusion is that some switches have a serious latency issues, may be it is related to switching type (pass-through, store-and-forward). The bottom line: network switch was causing this problem.

[Kerj]

Hi,
I have been experiencing a similar problem with a Windows 2003 Server which also is at Service Pack1. It was trying to backup to a NAS drive. It was always crashing out about 1.1Gb in. I had read that a network switch change could fix it so I gave that ago. However that didn't work for me. Neither did enforcing QoS and giving the server and the NAS drive Highest priority.
I did a lot of searching and none of the suggested fixes worked. This included a small update KB??. It responded with "you have this installed"

I resulted to taking a Ghost image of the server and then trying Service Pack 2 for Windows 2003.
Rebooted.
Then ran the backup again. This time it worked. I managed to backup all 794Gb without a hitch.

Now I don't know if this will work for you, but it really fixed my issue.

I would just add, ensure you take an image before running the service pack just to be on the safe side.

Regards,

[Kerj]

Hi,
I have been experiencing a similar problem with a Windows 2003 Server which also is at Service Pack1. It was trying to backup to a NAS drive. It was always crashing out about 1.1Gb in. I had read that a network switch change could fix it so I gave that ago. However that didn't work for me. Neither did enforcing QoS and giving the server and the NAS drive Highest priority.
I did a lot of searching and none of the suggested fixes worked. This included a small update KB890352. It responded with "you have this installed"

I resulted to taking a Ghost image of the server and then trying Service Pack 2 for Windows 2003.
Rebooted.
Then ran the backup again. This time it worked. I managed to backup all 794Gb without a hitch.

Now I don't know if this will work for you, but it really fixed my issue.

I would just add, ensure you take an image before running the service pack just to be on the safe side.

Regards,