The specified network name is no longer available.
-
After my application (heavy file IO on UNC address) is running a little bit it chrashes always with: SystemIO Exception: The specified network name is no longer available. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.get_Length() On this time the Share is also not reachable by explorer, sometimes the compleate system is chrashing, on reboot I have then to kill the explorer.exe. I think I use some resources too much. What is the best way to analyse this? ProcessMonitor? WinDbg? But how? Thanks, daniel
-
After my application (heavy file IO on UNC address) is running a little bit it chrashes always with: SystemIO Exception: The specified network name is no longer available. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.get_Length() On this time the Share is also not reachable by explorer, sometimes the compleate system is chrashing, on reboot I have then to kill the explorer.exe. I think I use some resources too much. What is the best way to analyse this? ProcessMonitor? WinDbg? But how? Thanks, daniel
I don't know the best way to analyse this, but I have a possible solution. Instead of reading and writing to, say "\\SomeComputer\SomeSharing\..." try creating a Remoting application. The remoting application server will run in SomeComputer. Then, it always access everything as C:\ D:\ (or the apropriate local drive) and the clients access the remoting server application instead of the drive mapping. I did that when I started to have problems reading and saving files remotelly and all my problems where gone.