“Report cannot be displayed” Error on CRM 4.0 Reports.

Recently serveral crm implementations began reporting that their CRM 4.0 implementations started throwing a “Report cannot be displayed” error when they attemped to run reports from within CRM. (It's worth noting that navigating to the SSRS reports web interface allowed us to run any reports - and any reports displayed inside a sharepoint dashboard continued to run as before.)

Every time a user attempted to run a report from within CRM, the error log showed events indicating:

Event Type:   Error
Event Source: MSCRMReporting
Event Category:      None
Event ID:     19970
[...]
Description:
Report render failure. Error: One or more data sources is missing credentials

-AND-

Event Type:   Warning
Event Source: ASP.NET 2.0.50727.0
Event Category:      Web Event
Event ID:     1309
[...]
Exception information:
    Exception type: CrmException
    Exception message: An error occurred during report rendering.

In looking at the program updates on the SQL Server, we found that there were 3 SQL 2005 Post-SP2 security updates applied to SQL early on the morning the reports stopped working. (3AM) – It appears that they were part of automatic updates.

GDR 3068 for SQL Server Database Services 2005 ENU (KB948109)
GDR 3068 for SQL Server Reporting Services 2005 ENU (KB948109)
GDR 3068 for SQL Server Tools and Workstation Components 2005 ENU (KB948109)

According to http://support.microsoft.com/kb/946289, One of the post-SQL2005 SP2 security patches unregisters or uninstalls the CRM Data Connector for SSRS. - It seems that this security patch has become part of the GDR and applied automatically.

The resolution is simple enough. Repair or re-install the SRS Data Connector on the SQL Server and then restart IIS on the CRM webserver.

--Scott Sewell

Comments

[Simon]

Ah Scott, livesaver! Thank you.

[RobCS]

It is a possible solution to the problem, but there another one.

Go to http://«server name»/reportserver/

- Click "«company»_MSCRM"
- Show Details
- 4.0
- MSCRM_DataSource
- Credentials stored in the server, type usr and pw for SQL Server, and check "Impersonate the authenticated user after a connection has been made to the data source"

DONE!