Windows Delayed Write Failure on Network Drive

[RobertEBob]

I'll try to be brief but I think this is a complicated problem.

I have a MBP (10.5.2) running Fusion (1.1.2) with XP/SP3 installed. Everything is working fine except every now and then, I will get an error message that is as follows:

Windows - Delayed Write Failed

Windows was unable to save all of the data for the file "here it lists the file name". 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.

Despite the message, I've never really lost data ... it just makes me worry.

Here is the complication ...

I also have an iMac (10.5.2) running Parallels with XP/SP3 installed. I even run the same version of Quicken on both XP machines pointing to the same network drive (though not at the same time). I only get this "Delayed Write Failed" from my Fusion machine.

Any thoughts?

Thank you in advance.

[asatoran]

To make sure I'm reading you correctly, you have two XP virtual machines. One in in Fusion on your MBP and the other is in Parallels on your iMac. Both have Quicken and both can write to the same network share. (You didn't mention if the Fusion machine had Quicken, but you imply it later.)

1. VMWare Tools installed?

2. Is the MBP attached to the network wired or wireless?

1. If wireless, what happens if you attached the MBP wired? (or vice versa?)

3. Is the MBP on AC or battery?

1. If on battery, maybe NICs are going to power saving. Try plugging in AC.

4. For that matter, where is shared folder? (i.e.: NAS, another Mac, a PC?) Is that machine going to power saver mode?

5. Are your hubs and wireless access points on UPS'? Power sags (brownouts) can cause networking issues.

6. Was the Fusion virtual machine a new clean install or an import of the Parallels virtual machine?

1. If an import, what happens if you do a clean install of WinXP and Quicken?

I've had to diaganose a lot of "delayed write to network" errors at clients' offices. Older building in particular often have AC power issues that cause intermittent outages and disconnects with hubs. Everyone puts their CPU on a UPS, but it's surprising how often the DSL/cable modem and hubs are not.

[RobertEBob]

W O W ! ! ! Thanks. What a list of questions..... Thank you.

Your initial assumption is CORRECT. Same Quicken accessing a NAS using the same "shared folder" (but NOT at the same time). iMac w/Parallels does NOT get the error while MBP does.

Now, as to your questions:

1. Yes VMWare Tools is installed.

2. The error has ocurred both wired and wirelessly.

3. AC Only.

4. NAS - Maxtor 350GB HD w/2 USB connections (printers)

5. No UPS. Generally happens under "blue skys" ... not during a "brown out".

6. Both iMac and MBP were clean installs from the same CD ... No Import or translation.

My DSL modem IS on a UPS, but the switch I'm using is actually plugged into the same A/C outlet as the NAS and MBP!

Boy, this has caused me to think!!! Thanks so much. Please let me know if you have further questions. Thanks, again!

Bob

[asatoran]

Well, you did say it was a "complicated." :smileysilly:

But that is part of the usual checklist that my coworkers and I use at client's offices. The fact that you have another setup to test with makes troubleshooting easier. At least you appear to have narrowed it down. You didn't mention if the switch is on a UPS. If it is you'll want to check the condition of the UPS. (Pull the power cord and see how long the battery lasts.) Sometimes even simple things like changing the outlet. I've seen power strips with one burned out socket that caused my coworker to waste many mintues troubleshooting why the device doesn't turn on.

Good luck and let us know what you find.

[wila]

The hint to check UPS etc.. is good, but if you had no power failure then logic tells me it is something else.

I'm not american so do not use Quicken, but IIRC it uses a flat file database (ISAM style, just guessing MS Access mdb files?)

So this means that you are sharing database on an OS file level, not ideal. If the windows host OS that is sharing the "database" has something enabled which is called opportunistic locking then you will get errors. (oplocks are enabled by default on windows)

If both are writing at the same time... you might get this error... or your files can simply go corrupt.

Other reasons that can get you this type of error:

- cheapo hubs instead of switches

- buggy network cards

- faulty cabling

--

Wil

[asatoran]

The hint to check UPS etc.. is good, but if you had no power failure then logic tells me it is something else.

I've seen power sags cause lockups in hubs/switches. (i.e.: power drops from 120VAC to 70VAC for less than 1 sec.) Very common if the utility compoany switches off one generating plant or has to disconnect one grid. (e.g.: auto accident knocks down a pole.) Power sags may cause a incandescent light bulb to dim briefly, but not flourescent bulbs. So the sag may not have been noticed.

At the client I mentioned above, replacing the Netgear switches with d-Link and Linksys switches didn't help. We still had to reset the switches every few days. No power outages reported. Then I remembered an old Radio Electronics article about the elevators in an old building causing intermittent power sags that had the tech troubleshooting for a few months. I put a UPS on the switches and I've not had problems with that client's network ever since.

But you are absolutely correct that cheapo equipment can be just as bad. And one of my coworkers wasted an hour troubleshooting a system because by coincidence the two spare patch cables he brought with him we also bad. :smileyblush:

[wila]

I've seen power sags cause lockups in hubs/switches. (i.e.: power drops from 120VAC to 70VAC for less than 1 sec.) Very common if the utility compoany switches off one generating plant or has to disconnect one grid. (e.g.: auto accident knocks down a pole.)

Sometimes things are different if you live in another part of the world, my bad. Over here power sags... sorry they don't happen or hardly ever, so it is not something I considered. A single power surge a year is about our current going rate if I'm not mistaken and we had our 1 second drop already this year.

Our cables are all underground, and yes those can be broken too, but it does not happen that often. No problems with storm, lightning...

Not as easy to implement in some countries due to sheer size.

--

Wil

[RobertEBob]

Many thanks to both asatoran and wila for your responses. I really appreciate the help, support and interest. Let me bring you up to date with a couple of clarifications and a plan ...

1. Even though I am using a share at the OS level the dataset is NEVER used from two machines at the same time ... I'm the only one using it. The iMac is in my kitchen and the MBP is in my office upstairs. Again, I've got Quicken on these two machines just for convienence sake.

2. These "Windows Delayed Write Failure" has happened on the MBP from a wired state as well as via wireless. The main constant in both scenarios is the target network drive is hardwired. Further, I'm using a Linksys 4 port switch, although it was a cheapie.

3. I am pretty paranoid about loosing data, but even though I've received about 5-6 of these "delayed" messages I don't believe I've lost any data ... at least my bottom line is what I expect it to be!

4. I think I've loaded both machines by the book; in other words I've

taken a conservative approach and made a fresh load of XP on both the

iMac (running Parallels) and the MBP (running Fusion). I might point

out that the iMac has Leopard 10.5.2 as an "upgrade in place" whereas

the MBP was purchased with Leopard as a "new" install.

PLANS:

I think I'll load another completely fresh XP on my MBP, get it completely updated (from mother Microsoft, load a clean version of Quicken and see where that leads. I'm about out of ideas.

Again, thanks to you both.

Bob;)

[jonoslack]

I also have this problem - frequently but not catastrophically.

I am running XP/SP3 on fusion 1.1.3 from a 17"MBP, accessing Visual Foxpro databases on client's local networks.

I am only doing what the clients themselves are doing via their pc machines, and they NEVER get this problem (around 2000 client machines running the same software on different networks).

I seem to get the problem randomly, although usually either 1. doing something intensive or 2. doing nothing for a few minutes with data tables left open.

I have seen it happen on linux servers, and on my mac server at home . . . . not yet with data on a Windows server.

Any more ideas on this one? anyone else had the problem? It clearly could be a big issue (and has sometimes been for me).

At the moment I cannot trust doing large data runs on client machines (and have to resort to an RDP connection).

all the best

[RobertEBob]

Thank you all for your responses...