FIX: Error message when you display a SQL Server 2000 Reporting Services report in an ASP.NET application: "System.Net.WebException: The operation has timed-out"

Article ID: 942713 - View products that this article applies to.
Bug #: 50001824 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package
Back to the top | Give Feedback

SYMPTOMS

When you display a Microsoft SQL Server 2000 Reporting Services report in an ASP.NET application, you intermittently receive the following error message:
System.Net.WebException: The operation has timed-out.
Back to the top | Give Feedback

CAUSE

This problem occurs because a working thread is holding a loader lock. The working thread occupies much memory. Therefore, the server is under memory pressure and tries to perform a garbage collection. When the garbage collector thread requests a loader lock, a deadlock occurs.
Back to the top | Give Feedback

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.

Prerequisites

To apply this hotfix, you must have SQL Server 2000 Reporting Services Service Pack 2 (SP2) installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build. 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.reportingservices.csvrendering.dll8.0.1058.057,34407-Nov-200718:30x86
Microsoft.reportingservices.diagnostics.dll8.0.1058.0270,33607-Nov-200718:30x86
Microsoft.reportingservices.diagnostics.dll8.0.1058.0270,33607-Nov-200718:30x86
Microsoft.reportingservices.excelrendering.dll8.0.1058.0364,54407-Nov-200718:30x86
Microsoft.reportingservices.htmlrendering.dll8.0.1058.0389,12007-Nov-200718:30x86
Microsoft.reportingservices.imagerendering.dll8.0.1058.0262,14407-Nov-200718:30x86
Microsoft.reportingservices.imagerendering.resources.dll8.0.1058.05,63207-Nov-200719:29x86
Microsoft.reportingservices.processing.dll8.0.1058.01,331,20007-Nov-200718:30x86
Microsoft.reportingservices.processing.resources.dll8.0.1058.0131,07207-Nov-200719:29x86
Microsoft.reportingservices.reportpreview.resources.dll8.0.1058.0172,03207-Nov-200719:29x86
Microsoft.reportingservices.xmlrendering.resources.dll8.0.1058.05,12007-Nov-200719:29x86
Microsoft.sqlserver.wizardframework.resources.dll8.0.1058.0405,50407-Nov-200719:29x86
Reportingservicesemaildeliveryprovider.resources.dll8.0.1058.08,19207-Nov-200719:18x86
Reportingservicesemaildeliveryprovider.resources.dll8.0.1058.08,19207-Nov-200719:29x86
Reportingservicesfilesharedeliveryprovider.resources.dll8.0.1058.08,70407-Nov-200719:18x86
Reportingservicesfilesharedeliveryprovider.resources.dll8.0.1058.08,70407-Nov-200719:29x86
Reportingserviceslibrary.dll8.0.1058.0557,05607-Nov-200718:30x86
Reportingserviceslibrary.resources.dll8.0.1058.011,77607-Nov-200719:18x86
Reportingserviceslibrary.resources.dll8.0.1058.011,77607-Nov-200719:29x86
Reportingservicesnativeclient.resources.dll2000.80.1058.03,58407-Nov-200719:18x86
Reportingservicesnativeclient.resources.dll2000.80.1058.03,58407-Nov-200719:29x86
Reportingservicesnativeserver.dll2000.80.1058.048,64007-Nov-200718:30x86
Reportingservicesnulldeliveryprovider.resources.dll8.0.1058.04,09607-Nov-200719:06x86
Reportingservicesnulldeliveryprovider.resources.dll8.0.1058.04,09607-Nov-200719:18x86
Reportingservicesnulldeliveryprovider.resources.dll8.0.1058.04,09607-Nov-200719:24x86
Reportingservicesnulldeliveryprovider.resources.dll8.0.1058.04,09607-Nov-200719:29x86
Reportingserviceswebserver.dll8.0.1058.0503,80807-Nov-200718:30x86
Reportingserviceswebserver.resources.dll8.0.1058.0131,07207-Nov-200719:06x86
Reportingserviceswebserver.resources.dll8.0.1058.0135,16807-Nov-200719:12x86
Reportingserviceswebserver.resources.dll8.0.1058.0135,16807-Nov-200719:18x86
Reportingserviceswebserver.resources.dll8.0.1058.0131,07207-Nov-200719:24x86
Reportingserviceswebserver.resources.dll8.0.1058.0131,07207-Nov-200719:29x86
Reportingserviceswebuserinterface.dll8.0.1058.0770,04807-Nov-200718:30x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.077,82407-Nov-200719:01x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.077,82407-Nov-200719:06x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.081,92007-Nov-200719:12x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.073,72807-Nov-200719:18x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.069,63207-Nov-200719:24x86
Reportingserviceswebuserinterface.resources.dll8.0.1058.077,82407-Nov-200719:29x86
Rsclientprint.cabNot applicable1,095,18007-Nov-200718:30Not applicable

Back to the top | Give Feedback

WORKAROUND

To work around this problem, modify the Web.config files of the report server Web site and of the report manager Web site. Modify the files to make sure that the mixed-mode assemblies are loaded by the ASP.NET application first, before the Microsoft intermediate language (MSIL) assemblies are loaded. To modify the Web.config files, follow these steps:
  1. Locate the Web.config file of the report server Web site and the Web.config file of the report manager Web site. By default, these files are located in the following folders:
    • The Web.config file of the report server Web site is in the following folder:
      C:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer
    • The Web.config file of the report manager Web site is in the following folder:
      C:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportManager
  2. Modify the code in the Web.config files as follows:
    • Add the following code to the Web.config file of the report server Web site.
          <compilation defaultLanguage="c#" debug="false">
      <assemblies>
        <clear />
              <add assembly="ReportingServicesSQLSortWrapper" />
              <add assembly="ReportingServicesNativeServer" />
              <add assembly="ReportingServicesNativeClient" />
              <add assembly="ReportingServicesWebServer" />
        </assemblies>
    </compilation>
    • Add the following code to the Web.config file of the report manager Web site.
          <compilation defaultLanguage="c#" debug="false">
      <assemblies>
        <clear />
              <add assembly="ReportingServicesNativeClient" />
              <add assembly="ReportingServicesWebUserInterface" />
      </assemblies>
    </compilation>
Note In some cases, you may be unable to use this method to work around this problem. You may have to apply the hotfix that is described in this article.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/ )
New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 942713 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2000 Reporting Services
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB942713
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top