Disk Full - Path is too Deep - Delayed Write Failed - MRxSMB - EventID 50

[James Meyer]

This problem started friday.

My client has a windows 2000 server at their head office.
The stores are connected VIA PPTP vpns through netopia routers.

They use excel files to track they're daily stats and such.

Since friday, whenever someone in a store saves an excel file located on a
network share on the server, they get one or more of these errors:
The disk is full

The path is too deep

Windows - Delayed Write Failed
Windows was unable to save all the data for the file
The data has been lost. This error may be caused by a failure of your
computer hardware or network connection.

In the error log I get an event id 50, with a source of MRxSMB

We have 100GB+ free
The paths are like \\192.168.2.88\Public\! Daily Totals\Daily Sales
Tracking - May 2006
But even \\192.168.2.88\Public\ doesn't work
Disk Caching isn't on
I've tried changing the network card to 10/Half Duplex instead of auto

And, lastly, it all works if your in the Head Office and just going over the
LAN without a VPN

Any help would be much appreciated.

James Meyer

 

[Guest]

James:

I've had a similar problem with one of my outer buildings connected via
fiber for some time (no VPN). Last week, a second building has all of the
sudden started experiencing the same problem. In my situation, smaller files
can be written to network drives, no problem. It's when they try to write
larger files that the user receives the exact same errors types:

Delayed Write Failed
Source: MRxSmb
Evert ID: 50

Last Word in log file is: c000020c

For a while I thought it was a fiber problem and the fact we use Telesyn
fiber converters. That gear checked out good last week. Of all my research,
I have found one article just yesterday that may hold some hope. Here's the
link:

http://tuketu.com/technology/windows/Windows Delayed Write.mht

and here's the article for fear that the link may become inaccessible at
some point in time:

Windows Delayed Write
Saturday, July 30, 2005 17:51

Symptoms:
Event ID 50, Windows Delayed Write Failed, source MrxSMB.
Happens in my case when a Windows XP, sp2 host is writing a backup file
(ntbackup) to a remote drive (a mapped drive letter), with the remote drive
being hosted by a Windows Server 2003, sp1 host. The last word of the event
logged (when viewed as words, not bytes) is c000020c, which is "Status
Connection Disconnected" NT status code.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters\enablesecuritysignature is set to "0" on the XP client, "1" on the server.

See Microsoft knowledge base KB890352
(http://support.microsoft.com/default.aspx?scid=kb;en-us;890352) and KB321733
(http://support.microsoft.com/default.aspx?scid=kb;en-us;321733).
Changes:
Initial changes: Changed registry key "enablesecuritysignature" to "0"
(false) on the server.
Changed server's and client's ethernet adaptors to use 100mbps full duplex,
rather than auto negotiation on the link. In other words, I forced both
adaptors into 100mbps full duplex mode. (They are both connected to the same
linksys switch).
Solution:
The final solution seems to be related to the "autonegotiate" option on
various network adaptors. When the network is under stress for long periods
of time, the adaptor may enter a temporary state of "auto" negotiating the
link, causing the link to be down for a brief period or something. Forcing
the link to be 100mbps, full duplex (for example) eliminates the problem.

See Also
<http://www.tangent-systems.com/support/delayedwrite.html>
http://www.adras.com/Windows-Delayed-write-error-when-backing-up-to-network-share.t16-18.html

http://www.tech-archive.net/Archive...blic.windows.server.general/2004-10/2360.html

Hope this helps! I'd like to see a MVP ring in on this issue too. This is
far too serious a problem ion production networks with remote locations not
to be thoroughly documented!

Regards,
John