MS CRM 4.0 Reports Fail to Display

PROBLEM:
  • Reports fail to display in MS CRM 4.0, with the following error shown "Reporting Error. The report cannot be displayed". 
  • If you have DevErrors turned on - which you should - (use CRM diagnostics tool on the server or modify the Web.Config file directly), the user might see one of the following errors under the Full Stack section: "[MissingParameterException: The 'CRM_Full_Name' parameter is missing a value]" or "[MissingParameterException: The 'CRM_CalendarType' parameter is missing a value]" or even "[ReportServerException: The permissions granted to user '<user>' are insufficient for performing this operation." 
  • This can happen when using either the web client or the Outlook 2007 client. 
  • None of the rollups fix the problem. 
  • Server is running Windows 2003 family, including SBS2003. 


SOLUTION THAT WORKED FOR ME:

This can occur when the Domain Logon Name field in CRM does not match the user's actual domain account name. It might be because the name in CRM has been misspelled or the domain account name was changed on the server but not updated or fails to propagate correctly in CRM.

Check that the Domain Logon Name in CRM matches the user's domain account name exactly. If it already does, change it to another user's name then back to the original user's logon name.

If you can't change the name in CRM because it throws the following error: "You are attempting to create a user with a domain logon that is already used by another user. Select another domain logon and try again.", change the Domain Logon Name field to another user who is not currently a CRM user. If you have none, create a temporary user on the server, change the Domain Logon Name to this user, then change back to the original user. This tip comes from http://navintmicrosoftcrm.blogspot.com/2008/12/how-to-correct-microsoft-dynamics-crm.html

A user should theoretically be blocked from accessing CRM if their Domain Logon Name does not match their actual domain name however Microsoft CRM seems to be the reason the word "theoretically" was conceived. Users can sometimes access CRM when the domain names don’t match but any reports would fail because reporting services produces the reports, not CRM.



OTHER POSSIBLE SOLUTIONS:
  • Check the authentication mode in the datasource for the report(s) and in IIS. It should be set to Windows Integrated Authentication. 
  • Check the affected users have been assigned a security role in CRM. 
  • Try installing the latest rollup. Information on all the latest hotfixes and rollups is located here http://support.microsoft.com/kb/949256/en-us
If none of these work, call Microsoft Support, as it could be some hitherto unknown thing that will commit you to an insane asylum if you try to figure it out alone.

Labels: ,