To resolve this problem, use Notepad to open the Web.config file that is in the root directory, and then add the following script between the <Configuration> tag and the </Configuration> tag.
Note The location path must be one of the Microsoft SQL Server Reporting Services (SSRS) virtual directories. By default, the SSRS virtual directories are named "ReportServer" and "Reports."
<location path="ReportServer">
<system.web>
<pages enableSessionState="true" validateRequest="false" enableViewState="true" />
</system.web>
</location>
<location path="Reports">
<system.web>
<pages enableSessionState="true" validateRequest="false" enableViewState="true" />
</system.web>
</location>
You may have to update the Web.config file of the Microsoft Dynamics CRM 3.0 Web site if the following conditions are true:
- The SSRS virtual directories are installed on the Microsoft Dynamics CRM 3.0 Web site.
- The SSRS virtual directories do not use default SSRS virtual directory names.
For example, the following script represents the default SSRS support in the Microsoft Dynamics CRM 3.0 Web.config file:
<!--
Support for SQL Reporting services
-->
<location path="Reports">
<system.web>
<compilation defaultLanguage="C#" debug="true">
<assemblies>
<remove assembly="Microsoft.Crm, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Entities, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.ManagedInterop, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.MetadataHelper, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.MetadataService, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.NativeInteropProxy, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.ObjectModel, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Platform.ComProxy, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Platform.Proxy, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Platform.Server, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Platform.Sdk, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Platform.Types, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Scheduling, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<remove assembly="Microsoft.Crm.Tools.ImportExportPublish, Version=3.0.5300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</assemblies>
</compilation>
<pages enableSessionState="true" validateRequest="false" enableViewState="true" />
</system.web>
</location>
<location path="ReportServer">
<system.web>
<pages enableSessionState="true" validateRequest="false" enableViewState="true" />
</system.web>
</location>
You may have to change the location path in the script from
ReportServer to the actual URL of the report server that you use. Additionally, you may have to change the location path in the script from
Reports to the actual URL of the reports that you use.