Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you run a report in Microsoft Dynamics CRM 4.0: "Reporting Error. The report cannot be displayed"

Error message when you run a report in Microsoft Dynamics CRM 4.0: "Reporting Error. The report cannot be displayed"

View products that this article applies to.

Symptoms

When you run a report in Microsoft Dynamics CRM 4.0, you receive the following error message:
Reporting Error. The report cannot be displayed.
Additionally, the following event is logged in the report server log file:
w3wp!processing!5!12/10/2007-15:06:18:: e ERROR: Throwing

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'.
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed.
Login failed for user <Placeholder for authenticating account>.

↑ Back to the top

Cause

This problem occurs because the account that the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services is using to authenticate does not have permissions to the Microsoft CRM databases.

↑ Back to the top

Resolution

To resolve this problem, grant the appropriate account permission to access the Microsoft Dynamics CRM databases. To do this, follow these steps:
  1. Identify the account that is used by the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server that authenticates to Microsoft SQL Server.

    For Microsoft SQL Reporting Services 2005

    If the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services is installed on a SQL Reporting Services 2005 instance, the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services will authenticate to SQL Server as the identity of the Internet Information Services (IIS) application pool used by SQL Reporting Services. To determine the identity of the IIS application pool used by SQL Reporting Services, follow these steps:
    1. On the Microsoft SQL Reporting Services server, click theStart button, and thenpoint to All Programs, click
      Microsoft SQL Server 2005, click Configuration Tools, and then click Reporting Services Configuration.
    2. In the Report Server Installation Instance Selection, select the SQL Reporting Services instance where the Microsoft CRM Data Connector for Microsoft SQL Server Reporting Services is installed, and then click Connect.
    3. Click Web Service Identify. Note the value for ASP.NET Service Account. This value indicates which account is used for the IIS application pool used by SQL Reporting Services which is also the account that is used by the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services when it authenticates to SQL Server.

    For SQL Reporting Services 2008

    If the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services is installed on a SQL Reporting Services 2008 instance, it will authenticate to SQL Server as the account running the SQL Server Reporting Services Windows service. To determine the account running the SQL Server Reporting Services Windows service, follow these steps:
    1. On the Microsoft SQL Reporting Services server, click the Start button, and thenpoint to Administrative Tools, and then click Services.
    2. Locate the SQL Server Reporting Services service and note the value that is listed in the Log On As column.
  2. Grant the appropriate account permission to access the Microsoft Dynamics CRM databases.
    If SQL Reporting Services and the SQL Server databases are installed on the same server and the account identified in step 1 is Network Service, follow these steps:
    1. Start SQL Server Management Studio. To do this, click the
      Start button, and then point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    2. Expand Security, expand
      logins, right-click NT AUTHORITY\NETWORK SERVICE, and then click Properties.
    3. Click User Mappings.
    4. Click to select the
      Organization_name_MSCRM check box, and then click to select the public check box and the
      CRMReaderRole check box.

      Note The Organization_name placeholder is a placeholder for the actual organization name.
    5. Click to select the MSCRM_Config check box, and then click to select the public check box and the
      CRMReaderRole check box.
    6. Click OK.


    If SQL Reporting Services and the SQL databases are installed on the same server and the account identified in step 1 is Local System, follow these steps:
    1. Start SQL Server Management Studio. To do this, click on the Start button, and then point to All Programs, point to
      Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    2. Expand Security, expand
      logins, right-click NT AUTHORITY\SYSTEM, and then click Properties.
    3. Click User Mappings.
    4. Click to select the
      Organization_name_MSCRM check box, and then click to select the public check box and the
      CRMReaderRole check box.

      Note The Organization_name placeholder is a placeholder for the actual organization name.
    5. Click to select the MSCRM_Config check box, and then click to select the public check box and the
      CRMReaderRole check box.
    6. Click OK.


    If SQL Reporting Services and the SQL Server databases are installed on separate servers and the account identified in step 1 is Network Service or Local System, follow these steps:
    1. a. Open Active Directory Users and Computers and verify that the SQL Reporting Services computer account is a member of the SQLAccessGroup that was created by the installation of Microsoft Dynamics CRM.
    2. Start SQL Server Management Studio. To do this, click on theStart button, and then point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    3. Expand Security, expand
      logins, right-click SQLAccessGroup, and then click Properties.
    4. Click User Mappings.
    5. Click to select the
      Organization_name_MSCRM check box, and then click to select the public check box and the
      CRMReaderRole check box.

      Note The Organization_name placeholder is a placeholder for the actual organization name.
    6. Click to select the MSCRM_Config check box, and then click to select the public check box and the
      CRMReaderRole check box.
    7. Click OK.


    Complete the following steps if SQL Reporting Services is running as a domain user account:
    1. Open Active Directory Users and Computers and verify that the user account identified in Step 1 is a member of the SQLAccessGroup that was created by the installation of Microsoft Dynamics CRM.
    2. Start SQL Server Management Studio. To do this, click
      Start, point to All Programs, point to
      Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    3. Expand Security, expand
      logins, right-click SQLAccessGroup, and then click Properties.
    4. Click User Mappings.
    5. Click to select the
      Organization_name_MSCRM check box, and then click to select the public check box and the
      CRMReaderRole check box.

      Note The Organization_name placeholder is a placeholder for the actual organization name.
    6. Click to select the MSCRM_Config check box, and then click to select the public check box and the
      CRMReaderRole check box.
    7. Click OK.

↑ Back to the top

References

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
946289 Error message when you run a report in Microsoft Dynamics CRM 4.0: "The report cannot be displayed"

↑ Back to the top

Keywords: kbmbsreports, kberrmsg, kbexpertisebeginner, kbtshoot, kbmbsmigrate, kbprb, kbexpertiseinter, kbmbspilot, kb

↑ Back to the top

Article Info
Article ID : 946585
Revision : 1
Created on : 1/7/2017
Published on : 9/12/2011
Exists online : False
Views : 493