Dynamics CRM Portal Errors And Tracing

I received this very generic looking message (below) when trying to run a Dynamics CRM portal. After a little experimenting I found the problem to be that my credentials pointed to a user that had not yet been added to the target CRM organization (but did exist in Active Directory).

Yet another reminder to check the basics when faced with strange errors.

The interesting thing here is that the error message I received might lead you to believe that tracing needs to be enabled for your portal (in order to gather more error details). However, this error is actually being delivered from the Dynamics CRM server, and is not reflective of the tracing settings for your portal.

If you are operating Dynamics CRM on premise, and would like it to include these additional exceptional details with its faults (so you can possibly see the reason behind the fault), instructions on how to do so can be found here.

Here’s my original error message:

Server Error in '/' Application.

The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.