• eLogic

Dynamics CRM Tech Tip – Suppressing CRM Application Error Messages

“Microsoft Dynamics CRM has encountered an error.”

Most Microsoft Dynamics CRM administrators are painfully familiar with this error text. It’s basically a catch-all that appears to users when the web application encounters any sort of issue, and asks them for permission to report the error to Microsoft.

The error itself however is rarely indicative of any actual problem on the page that will prevent your users from completing their work. It may be due to a JavaScript error, a browser incompatibility, an improperly set time-out value, or any number of other variables that you’re likely never going to be able to, or care to, track down.

Since these errors are almost always “soft errors” (errors that don’t interfere with normal application usage), most administrators would prefer their users were never bothered by them.

Luckily for us, Microsoft makes removing these nuisance errors possible through a setting within the application.

From within Settings, select Administration.

Select Privacy Preferences.

On the Error Reporting tab of the Privacy Preferences panel, you will see the option to set the Web application error notification preferences on behalf of the user.

By selecting the “Specify the Web application error notification preferences on behalf of users” checkbox and then selecting either “Automatically send an error report to Microsoft without asking the user for permission” or “Never send an error report to Microsoft”, the user will no longer be prompted for permission on these types of errors.

Note that this setting will not impact any validation error messages, any custom logic errors or any errors in general that prevent a user from continuing with their work. These will still need to be resolved on a case-by-case basis either through record remediation or administrative changes.

However, through a simple change of this slightly obscured setting baked right into CRM, you may be able to significantly improve your users’ CRM experience while at the same time reducing the number of support tickets received for non-critical, non-specific application errors.