c# – Delayed Write Failed on Windows 2003 Clustered Fileshare

c# – Delayed Write Failed on Windows 2003 Clustered Fileshare

Ive heard of AutoDisconnect causing similar issues (even if the device isnt idle). You may want to try disabling that on the server.

I am having similar problems:

  • writing to a machine that is also part of a Windows 2003 R2 NLB cluster sometimes results in Delayed Write Failed or the semaphore has timed out or the specified network name is no longer available
  • this is reproducible for the same files, even after rebooting all machines involved
  • if I rename the problem-files (some of which are quite small), the problem remains
  • if I write the files to another location (fysical disk) on the same machine, the problem remains
  • I uninstalled all anti-virus software, problem remains
  • I have reset the tcp-ip stack, problem temporarily disappears, but after some time the problem returns for the same files

PARTLY SOLVED the problem:
I deleted (not stopped) the host from the NLB cluster. Problem solved.

Seems to have to do something with writing to a share on a server that is also part of a network load balancing cluster

I have not yet found other people posting NLB cluster related file write problems. However, I did find many posts complaining about similar problems, none of which seem to have been solved.

Anne

c# – Delayed Write Failed on Windows 2003 Clustered Fileshare

Ive seen other people reporting the delayed write failed error. One recommendation was to adjust the size of the cache, theres a utility from sysinternals (http://technet.microsoft.com/en-us/sysinternals/bb897561.aspx) that will allow you to do that.

Related posts:

Leave a Reply

Your email address will not be published. Required fields are marked *