This seems to be a very basic request but it would make life much easier if the 'unhandled exception' type errors gave some meaningful information about the cause of the error. The stack trace provides low-level programming information, but that has very limited use with the average user. 

I hear complaints about vague and unhelpful error messages regularly from the users at our company and it's hard to say that's just the way it is.

In addition, if the user could more easily diagnose issues they run into because of messages that tell them where to look it would reduce the need to contact MV support, saving their time and our time.

I realize that it would be nearly impossible to document every exception possible, but it would be a great improvement if the more commonly encountered errors could contain more information.