You can set the debugger to break on all exceptions (Go to Debug Menu -> Exceptions -> Common Language Runtime Exception, then select “Break into the debugger” radio button, in VS 2003), which should give you the exact exception being raised.
Apart from that, it is difficult to see what is the problem without a reproduction. Is it possible for you to send a sample application reproducing the issue to <a href=”mailto:firstname.lastname@example.org”>support</a>?
Imported from legacy forums. Posted by André (had 4959 views)