> For what it’s worth, I’ve seen conditions in .net where this > exception actually refers to memory conditions, not disk storage. > > - Scott Colestock
And to confirm what Scott mentioned, I have seen this message from a COM+ application and I have always hypothesized that it was due to some non-disk resource exhaustion condition; it rears it's head only after the application has been running between weeks and months. The "solution" has always been to bounce the box. :-(
