OK, my bad ... I saw "error on FileStream" and missed that you said it initally burped on the .ToString().

It might have something to do with your ExceptionObj ... are you sure it exists? Are you sure .InnerException exists? I dunno ... I'm just grasping at straws here.

~~Bonnie


>>It probably has something to do with Write rights in IIS
>
>Hmmm... that probably doesn't account for the problem with ToString(), but it could be causing a problem with the file creation. I'll check that out and see if it narrows things down to only *one* problem <s>.
>
>FWIW, the Message property seems to be pretty useless, as it only returns the type of error, not the full text of the actual error condition as you get with the ToString().
>
>Actually, now that I think about it, your suggestion might apply if things were going south on the line implementing Sw.Write(), but it's barfing on the instantiation of the FileStream object.
>
>In doing some more experimenting, it seems that this behavior is definitely reflecting an error somewhere in the ExceptionHandler code. If, for instance I make a comparison of a value type to an integer value and the value type is null, I get the same behavior.
>
>The nagging question is why I'm getting an error from the ToString()?!?!