What in your solution has a parameter named s? To zoom down to theproblem, first remove all the code from the HasResponse procedure andmake it to return always True. This will rule out the code in theprocedure if the error happens again.
Cheers
Actually there is no parameter s in my app. It's an internal .Net thing. I no longer have the trace stack, because I fixed the problem, but it seems to be some method in System.IO that's bombing out. Why, I don't know. I can't relate the error to the fix I found. Basically, I had a datareader open while trying to create a datatable. I'm surprised that's a problem, but fixing that made this problem go away...
Thanks for trying to help!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment