indiegirl

And a happy customer here too. We're local to Bluepoint, and they let us collect rather than deliver - saving us the delivery charges. I believe that you can ask to be removed from the mailing lists... Far cheaper than most other places (well, especially when delivery costs are removed)

Good question! I don't actually know - only that it was done a very, very long time ago, probably by a cheap firm!

We *think* we've solved the problem here. It was indeed network related...: It appeared that some clever sod had daisy-chained two of the three office network points together (coincidently the two which the PCs had the DWF errors on). Coupled with the fact that these were only running over Cat5e back to the switch, it created a painfully slow lag which caused the errors. The points have been recabled, and fibre's gone in, and wahey... no more problems :-) (just thought I'd update you all) Thanks for your thoughts.

ChrisH: I'll be plugging them into different switches if I can kingswood: I suspect that as these points go back to the Sixth Form cabinet, we could have the same problem as you . Both the machines are XP SP2, so I don't see any errors on that side. I would've thought that if it was a disk going, everyone who writes to that 'shared area' (which is the entire staffing lot - teaching and support) would have problems - which they don't. eejit: we get it when saving small Word docs! I will check for NIC driver updates though - just to see if that helps (and I don't think we have DMA on but some 'thoughtful' bugger (read my manager) might've put that on)... Thanks all for your suggestions so far, I'll probably report back once troubleshooting has taken place!

I'm definitely going to test out the network (next week, when it's much quieter). We don't use Roaming Profiles (god, no!). I was just interested to see what others might suggest. I'll try another machine as well in that office to see if the same problem occurs. It's just very strange that two out of three machines in the office would suffer...

Interesting. The main area we're saving back to (on our 'file server') is a brand new server where all staff and students have access. No other member of staff have had that error message when saving to the same shared area. Both local machines are also brand new. I know it's possible, but the likelihood of the server disk being about to go, or both local machine ones seems remote to me.

My school runs a Win2k3 server backend, with one domain. We have a 'shared' area for staff to save to, and individual 'home' areas as well. Two members of my staff (both in the same office) are reporting problems saving to the shared area. They tell me that they get a "delayed write failed" error message, with Windows being unable to save the .tmp file - so it can't actually save the .doc (in Word, for example). One of the two is also unable to save to her 'home' area. The problem is that this is intermittent - sometimes it will work, others it won't. The machines are all XP sp2 with all updates, and Office 2k3 with all updates. We thought that the updates had solved the problem this morning, indeed - both staff members could save to the shared area, although 3 hours later they reported that they couldn't. Another staff member in the same office is able to save to both areas problem-free. Now personally I think this could be a network lag, or certainly problems with the network cabling somewhere. My Network Manager (I'm a lowly technician) doesn't agree. Am I barking up the wrong tree? Has anyone else ever had the 'delayed write failed' error before?