Troubleshooting reporting in Microsoft Dynamics CRM 3.0

There are several possible reasons why data you expect to be on a report does not appear:

Most reports, on Microsoft Dynamics CRM systems with typical amounts of data, return results within thirty seconds to a minute. Some reports might take longer if the report includes a large number of records, or if the system usage is high.

If you are a user, try editing the filter before you run the report to select fewer records. If you need to run a summary report for a large number of records, such as the Account Distribution report, expect it to take a while to run and try to run it when system usage is low.

If you are a system administrator, you have several options:

This error will occur if the Enable Integrated Windows Authentication check box is not selected in Microsoft Internet Explorer.

To fix this problem:

This problem may occur if you use too many related record-types to filter the report. Try reducing the number of filter criteria for the report, and running the report again. If you are running the report from a view that uses several record-types in the view criteria, try running it from a simpler view instead.

If you are writing a new Reporting Services report, you may get this error if you have too many joins in the SELECT statement in your report. Try reducing the number of joins.

This problem may occur if you use too many parameters to filter the report or select too many individual records to run a report on. This is due to a limit in Microsoft SQL Server 2000 Reporting Services: only 2048 characters can be included in the URL string.

Try reducing the number of filter criteria for the report or selecting fewer records, and running the report again.

This problem does not occur with Microsoft SQL Server 2005 Reporting Services.

This security warning occurs the first time you try to print a Microsoft SQL Server Reporting Services report from either Microsoft Dynamics CRM or Microsoft Dynamics CRM 3.0 client for Microsoft Office Outlook.

To print reports, you need a Reporting Services ActiveX control. To install the required control, click Install.

This error occurs the first time you try to print a report from either Microsoft Dynamics CRM or Microsoft Dynamics CRM client for Outlook if you are not in the local administrators group on your computer. You need an ActiveX control that is required for printing reports, but do not have permission to install ActiveX controls on your computer.

To fix this problem:

This error might occur if the ActiveX control used for printing reports is an old version or is not installed correctly. To fix this problem:

Export the report a second time, and the chart will be displayed.

This error occurs if you are accessing Microsoft Dynamics CRM from a different domain than the domain that Microsoft Dynamics CRM is installed on.

To export a list of records to a dynamic Microsoft Office Excel worksheet (a file that refreshes data from the Microsoft Dynamics CRM database each time it is opened) or PivotTable, your computer must be on the same domain as the domain of the Microsoft Dynamics CRM server. If you are on a different domain, you can export a worksheet static (a file that does not change when data changes in Microsoft Dynamics CRM).

To access Reporting Services Report Manager, in your Web browser enter the URL for Report Manager, which by default is: http://<Reporting_Services_Report_Server>/Reports, and browse to the folder for Microsoft Dynamics CRM reports.

Users who do not have permission to see the top-level folder in Report Manager will see an empty screen, and cannot browse to the folder for Microsoft Dynamics CRM reports. By default, only users with the local Administrator role on the report server can access the top-level folder.

Other users need to open the URL for the Microsoft Dynamics CRM reports folder, http://<Reporting_Services_Report_Server>/Reports/Organization_name. For example, if your organization name is "Adventure Works", you would open: http://<Reporting_Services_Report_Server>/Reports/Pages/Folder.aspx?ItemPath=/Adventure+Works_MSCRM.

In order to download a report from Microsoft Dynamics CRM, you must have:

To download a report, log in as a user with the necessary roles. For more information about security roles in Reporting Services, see Reporting Services Books Online.

This error can occur if you are trying to upload a file that is larger than 10 MB. Reports larger than 10 MB cannot be uploaded, because they will degrade performance for your users.

This error occurs if Microsoft Dynamics CRM and Reporting Services are installed on the same server, the server is running Windows Server 2003 or is a Microsoft Windows Small Business Server 2003, and Domain user was specified on the Specify Security Account page when Microsoft Dynamics CRM was installed.

To add the necessary permissions, make the following change in Reporting Services Report Manager.

There are two ways to access Microsoft Dynamics CRM reports over the Internet:

SBS 2003 R2 includes Microsoft SQL Server 2005 Workgroup Edition. Microsoft Dynamics CRM works in this environment, although several reporting features are not available. You cannot use Reporting Services Report Manager, or the optional Microsoft Dynamics CRM Report Scheduling Wizard, to schedule reports, or export reports to DHTML, comma-separated value, or XML formats.

When you install Microsoft Dynamics CRM, you can install SQL Server 2000 Reporting Services or connect to an existing instance of Reporting Services.

If you have Microsoft Dynamics CRM install Reporting Services, you must have Microsoft SQL Server 2000 installed on the server on which you install Reporting Services. SQL Server 2000 Reporting Services does not work with Microsoft SQL Server 2005.

If you connect to an existing instance of Reporting Services, you can connect to either SQL Server 2005 Reporting Services, which requires SQL Server 2005, or SQL Server 2000 Reporting Services, which requires SQL Server 2000.

If you use SQL Server 2005, and Microsoft Dynamics CRM and SQL Server are on the same computer, after you install Microsoft Dynamics CRM, verify that the Microsoft Dynamics CRM Web site uses Microsoft ASP.NET version 1.1. SQL Server 2005 uses Microsoft ASP.NET version 2.0.

In most cases, yes. You can upgrade Microsoft SQL Server 2000 to Microsoft SQL Server 2005 on the server with the Microsoft Dynamics CRM databases, as well as on the reporting server. Reports written in Microsoft SQL Server 2000 Reporting Services work on Microsoft SQL Server 2005.

If you upgrade your Reporting Services server, any snapshots that you created by using the Report Scheduling Wizard will be lost. To make sure that you do not lose this important data, before you upgrade, open each snapshot, and save it as a .pdf file.

However, if you are using the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP, and the Microsoft Dynamics CRM databases and the Integration server are on the same computer that is running SQL Server, you cannot upgrade to SQL Server 2005. The Microsoft Dynamics CRM Connector for Microsoft Dynamics GP uses Microsoft BizTalk Server 2004, which does not support SQL Server 2005.

Yes. Using a product from the Microsoft Visual Studio .NET 2003 family, you can write reports using Reporting Services 2000, and then publish these reports to a Microsoft Dynamics CRM installation that uses SQL Server 2005 for its reporting server.

No.

To use SQL Server 2000 Reporting Services, you must use a product from the Microsoft Visual Studio .NET 2003 family.

To use SQL Server 2005 Reporting Services, you can use a product from the Visual Studio .NET 2005 family or you can use SQL Server 2005 Report Builder without using Visual Studio. You cannot use Visual Studio .NET 2003 with SQL Services 2005 Reporting Services.

If reports don’t work after installing Microsoft Dynamics CRM, use the following questions to determine what the problem might be. If the suggestions below don’t help, include the answers to the questions when you contact support to help them solve the problem more quickly.

For details on additional steps, download the article Additional Setup Tasks Required if Reporting Services Is Installed on Different Server.

If changes you make and save in the System Settings dialog box aren't saved when you return to that dialog box, you may have an error in your Reporting Services Report Manager installation. This error occurs when all of the following conditions are met:

To add the necessary permissions, make the following change in Reporting Services Report Manager.

Microsoft CRM 1.2 uses the UserGroup group in Microsoft Active Directory to determine who has access to reports. Microsoft Dynamics CRM 3.0 uses the ReportingGroup group in Active Directory. Sometimes the upgrade process does not transfer the members of UserGroup group to the ReportingGroup group. To solve this problem, manually add your Microsoft Dynamics CRM users to the ReportingGroup in Active Directory.

See Knowledge Base article 913518, Error message when you try to install Microsoft Dynamics CRM 3.0: “The Web site for installing SQL Reporting Services was not found”.

This problem can occur when Microsoft Dynamics CRM and Microsoft SQL Server 2000 Reporting Services are installed on the same server, and when that server is running either Microsoft Windows Small Business Server 2003 or Window Server 2003.

If you installed using a domain user account, to add the necessary permissions, make the following change in Reporting Services Report Manager.

If reports don't display, but you don't get an error when you open the Reports area, the reports probably weren't published to the Report server. Run PublishReports.exe, as documented in Chapter 24 of the Microsoft CRM 3.0 Implementation Guide.

If the reports display in Reporting Services Report Manager, but don't display in Microsoft Dynamics CRM, and you used PublishReports.exe to publish them manually, you may have incorrectly specified the folder for the reports. The folder name must be the organization name you used when you installed Microsoft Dynamics CRM, with _MSCRM appended. For example, if you installed Microsoft Dynamics CRM using the organization name Adventure Works Cycle, the folder for Reporting Services must be Adventure Works Cycle_MSCRM.

Host headers cannot be used on the Reporting Services Web site. Remove the host headers and any identities, such as the loopback address. For more information, see Knowledge Base article 896861, You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6.

This error may occur when one or more of the following conditions are true:

For information about how to resolve this problem, see Microsoft Knowledge Base article 907487, You receive a "The request failed with HTTP status 401: Unauthorized" error message when you try to view reports in Microsoft CRM 3.0.

If you receive this error on a custom report you uploaded, see Microsoft Knowledge Base article 921546, Error message when you try to run a report or upload a report in Microsoft Dynamics CRM 3.0: "The request failed with HTTP status 401: Unauthorized" or "Server Error in ‘/’ Application".

This problem occurs because the security account for the CRMAppPool application pool does not have the Publisher for Microsoft Dynamics CRM security role in Report Manager.

For information about how to resolve this problem, see Microsoft Knowledge Base article 921546, Error message when you try to run a report or upload a report in Microsoft Dynamics CRM 3.0: "The request failed with HTTP status 401: Unauthorized" or "Server Error in ‘/’ Application".