You may receive an error message when you try to upload a customized report to Microsoft Dynamics CRM 3.0 or to SQL Server Reporting Services or when you try to modify the report in Visual Studio Report Designer

Symptom 1

Consider the following scenario in Microsoft Dynamics CRM 3.0. You download a customized report that contains Microsoft Dynamics CRM Pre-Filtering code. Then, you try to upload the report to Microsoft Dynamics CRM 3.0. In this scenario, you receive the following error message:This problem occurs if you use Microsoft SQL Server 2005 Reporting Services (SSRS) in Microsoft Dynamics CRM.

Symptom 2

Consider the following scenario in Microsoft Dynamics CRM 3.0. You download a customized report that contains Microsoft Dynamics CRM Pre-Filtering code. Then, you try to upload the report directly to Reporting Services or you try to modify the report in Microsoft Visual Studio Report Designer. In this scenario, you receive the following error message:

This problem occurs because the downloaded report was formatted incorrectly. The report contains the appended Microsoft Dynamics CRM Pre-Filtering code for the SQL Server 2003 Reporting Services schema or for the SQL Server 2000 Reporting Services schema. The SQL Server 2003 Reporting Services schema and the SQL Server 2000 Reporting Services schema use the <Custom> tag for pre-filtering. The SQL 2005 Reporting Services schema contains new schema definitions. The new schema definitions do not use the <Custom> tag when you re-upload the report. Therefore, Microsoft Dynamics CRM cannot validate the XML code in the report.

This problem was corrected in Microsoft Dynamics CRM 3.0 Update Rollup 3.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this problem, modify the report to use the correct format. To do this, use the appropriate method:

• If the server was not restarted, you are in the original environment. Use Method 1 to resolve this problem.
• If the server was restarted, you are not in the original environment. Therefore, you cannot apply the hotfix that is mentioned in Method 1. In this case, if you must upload the report to the new environment, use Method 2 to resolve this problem.
  
  Note For example, you exported the report as part of a backup plan. Later, the computer that is running Reporting Services crashed. After the computer that is running Reporting Services is re-created, you are no longer in the original environment. Therefore, you cannot apply the hotfix. You must modify the report to use the Report Definition Language (RDL) 2005 tags.

Method 1

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft Dynamics CRM 3.0 serverMicrosoft Dynamics CRM 3.0 laptop client for Microsoft Office Outlook Compatibility UpdateMicrosoft Dynamics CRM 3.0 laptop client for Microsoft Office OutlookAfter you apply the hotfix to Microsoft Dynamics CRM, the report will be formatted correctly.

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM 3.0 server and the Microsoft Dynamics CRM 3.0 client for Microsoft Office Outlook.

Prerequisites

You must have the Microsoft Dynamics CRM 3.0 server and the Microsoft Dynamics CRM 3.0 client for Microsoft Office Outlook installed to apply this hotfix.

Restart requirement

If you are prompted, restart the computer after you apply the hotfix.

Removal information

To remove this hotfix from a computer that is running Windows Server 2003, Windows XP, or Microsoft Windows 2000, use Add or Remove Programs in Control Panel. System administrators can use the Spuninst.exe tool to remove this hotfix from a computer that is running Windows Server 2003, Windows XP, or Microsoft Windows 2000.

The Spuninst.exe tool is located in the %Windir%\$NTUninstallKB939867$\Spuninst folder.

Method 2

To resolve this problem, modify the report to use the RDL 2005 tags instead of the RDL 2003 tags in XML. To do this, follow these steps:

1. Open the report by using Notepad or by using a rich text XML editor.
2. Locate the CRM Pre-Filtering section in the report. Replace the existing code with the replacement code as follows.
   
   Existing code

   <Custom>
   <MSCRM xmlns="mscrm"><ReportFilter><ReportEntity paramname="P1"><
   fetch version="1.0" output-format="xml-platform" mapping="logical" 
   distinct="false"><entity name="account"><all-attributes /><
   filter type="and"><condition attribute="modifiedon" operator="last-x-days" 
   value="30" /></filter></entity></fetch></ReportEntity></ReportFilter></MSCRM>
   </Custom>  
   
   

   Replacement code

   <CustomProperties> 
   <CustomProperty> 
   <Name></Name> 
   <Value></Value> 
   <MSCRM xmlns="mscrm"><ReportFilter><ReportEntity paramname="P1"><
   fetch version="1.0" output-format="xml-platform" mapping="logical" 
   distinct="false"><entity name="account"><all-attributes /><
   filter type="and"><condition attribute="modifiedon" operator="last-x-days" 
   value="30" /></filter></entity></fetch></ReportEntity></ReportFilter></MSCRM>
   </CustomProperty> 
   </CustomProperties> 
   

   Notes
   • In this code, the following tags are added. SQL Server 2005 Reporting Services requires these tags.

     <Name></Name>
     <Value></Value>
     

   • In this code, the following SQL Server 2003 Reporting Services tags are modified to be SQL Server 2005 Reporting Services tags.

     <Custom>
     ...
     </Custom> 

For more information about software update terminology, click the following article numbers to view the articles in the Microsoft Knowledge Base: