Recently I came into a problem when I accidentally added a user to CRM that caused the entire CRM instance to no longer be usable. What happened is the user shared I added to an instance was the user that created the CRM instance. That cause the whole instance to throw an error any time anyone would load it up.
The other day while working on a Silverlight application I received the following error:
“Parser internal error: Object writer ‘xClassNotDerivedFromElement’. [Line: N Position: N]
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)”
When calling the InitializeComponent() internal method on a custom user control.
So I did what I did best and searched Google for the answer, and while I didn’t end up finding my solution there I did find more about what can cause this error to occur.
With the implementation of MVC there is a lot more room for unhanded global exceptions because in MVC you are encouraged to write more in line code to accompany the back end code. So what happens when an exception is thrown within the front end code? Well you’ll have an exception that will bubble up to the global application class which if you don’t handle it there it will continue to bubble and be displayed to the user as specified in the web configuration file. This doesn’t do you much good, sure the user will know that there is an error, and you can squelch the amount of information that is displayed to your ordinary users, but if working through trouble shooting the issue this basic information does you no good.