January 24, 2013 by Ruaan Harmzen
I’ve been having some fun and games with Sharepoint 2010 and SSRS. One of the most frustrating things of working with Sharepoint is the lack of consistent error handling and tracing. You are never sure where the errors are logged which can make troubleshooting tough.
My problem was related to the WCF services used by SSRS and Sharepoint. The normal error message looks something like this:
System.ServiceModel.FaultException: 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 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 3.0 SDK documentation and inspect the server trace logs.
You can change and update config files till you are blue in the face but you will not get a more detailed error message (normal WCF services will but not SSRS).
To enable a slightly more detailed error message do the following:
– Open your report server database
– Goto to ConfigurationInfo table
– Update the “EnableRemoteErrors” property