FIX: Error message when you use Report Manager in SQL Server 2005 Reporting Services to view a report: "The request failed with an empty response" (918555)



The information in this article applies to:

  • Microsoft SQL Server 2005 Reporting Services

Bug #: 689 (SQL Hotfix)
Bug #: 596 (SQL Hotfix)
Bug #: 435436 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you use Report Manager in SQL Server 2005 Reporting Services to view a report, you may receive an error message from the Web browser that resembles the following:
"The request failed with an empty response"
When this problem occurs, other management functions of Report Manager work as expected.

CAUSE

This problem occurs because Report Manager does not pass the specified custom cookie to the report execution endpoint.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

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 replacement information

This hotfix replaces the file ReportingServicesWebUserInterface.dll version 9.00.2047.0.

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 of 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.SQL Server 2005 hotfix, 32-bit
File nameFile versionFile sizeDateTimePlatform
Dundaswebchart.dll9.0.2175.0752,41621-Jul-200602:29Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200602:26Not Applicable
Microsoft.sqlserver.sqlenum9.0.2175.0908,06421-Jul-200602:29Not Applicable
Ms.as.deployengine.dll9.0.2175.0138,01621-Jul-200602:26Not Applicable
Ms.as.modeling.dll9.0.2175.0564,00021-Jul-200602:26Not Applicable
Ms.rs.processingcore.dll9.0.2175.01,669,92021-Jul-200602:30Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2175.075,55221-Jul-200602:25Not Applicable
Msadomdx.dll9.0.2175.0502,56021-Jul-200602:26Not Applicable
Msmdlocal.dll9.0.2175.015,701,79221-Jul-200602:31Not Applicable
Msmgdsrv.dll9.0.2175.05,971,74421-Jul-200602:31Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200602:26Not Applicable
Reportbuilder.exe9.0.2175.05,389,08821-Jul-200602:31Not Applicable
Reportingservices.dataextensions9.0.2175.0154,40021-Jul-200602:27Not Applicable
Reportingservices.diagnostics.dll9.0.2175.0604,96021-Jul-200602:27Not Applicable
Reportingservices.diagnostics.dll9.0.2175.0604,96021-Jul-200602:27Not Applicable
Reportingservices.htmlrendering.dll9.0.2175.0301,85621-Jul-200602:25Not Applicable
Reportingserviceslibrary.dll9.0.2175.01,030,94421-Jul-200602:29Not Applicable
Reportingservicesservice.exe9.0.2175.014,62421-Jul-200602:22Not Applicable
Reportingserviceswebserver.dll9.0.2175.01,325,85621-Jul-200602:30Not Applicable
Rs.excelrendering.dll9.0.2175.0330,52821-Jul-200602:25Not Applicable
Rswebuserinterface.dll9.0.2175.01,239,84021-Jul-200602:30Not Applicable
SQL Server 2005 hotfix, 64-bit
File nameFile versionFile sizeDateTimePlatform
Dundaswebchart.dll9.0.2175.0752,41621-Jul-200609:02Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200609:02Not Applicable
Microsoft.analysisservices9.0.2175.01,215,26421-Jul-200602:30Not Applicable
Microsoft.sqlserver.sqlenum9.0.2175.0875,29621-Jul-200609:01Not Applicable
Ms.as.deployengine.dll9.0.2175.0138,01621-Jul-200602:26Not Applicable
Ms.as.modeling.dll9.0.2175.0564,00021-Jul-200609:02Not Applicable
Ms.rs.processingcore.dll9.0.2175.01,669,92021-Jul-200609:01Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2175.075,55221-Jul-200602:25Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2175.091,42421-Jul-200609:00Not Applicable
Msadomdx.dll9.0.2175.0502,56021-Jul-200602:26Not Applicable
Msmdlocal.dll9.0.2175.030,233,88821-Jul-200609:01Not Applicable
Msmgdsrv.dll9.0.2175.08,964,89621-Jul-200609:01Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200609:02Not Applicable
Reportbuilder.exe9.0.2175.05,389,08821-Jul-200602:31Not Applicable
Reportingservices.dataextensions9.0.2175.0154,40021-Jul-200609:00Not Applicable
Reportingservices.diagnostics.dll9.0.2175.0604,96021-Jul-200609:02Not Applicable
Reportingservices.diagnostics.dll9.0.2175.0604,96021-Jul-200609:02Not Applicable
Reportingservices.htmlrendering.dll9.0.2175.0301,85621-Jul-200609:01Not Applicable
Reportingserviceslibrary.dll9.0.2175.01,030,94421-Jul-200609:01Not Applicable
Reportingservicesservice.exe9.0.2175.014,62421-Jul-200609:01Not Applicable
Reportingserviceswebserver.dll9.0.2175.01,325,85621-Jul-200609:01Not Applicable
Rs.excelrendering.dll9.0.2175.0330,52821-Jul-200609:01Not Applicable
Rswebuserinterface.dll9.0.2175.01,239,84021-Jul-200609:01Not Applicable
SQL Server 2005 hotfix, 64-bit for Itanium processors
File nameFile versionFile sizeDateTimePlatform
Dundaswebchart.dll9.0.2175.0752,41621-Jul-200604:01Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200604:00Not Applicable
Microsoft.analysisservices9.0.2175.01,215,26421-Jul-200602:30Not Applicable
Microsoft.sqlserver.sqlenum9.0.2175.0875,29621-Jul-200604:01Not Applicable
Ms.as.deployengine.dll9.0.2175.0138,01621-Jul-200602:26Not Applicable
Ms.as.modeling.dll9.0.2175.0564,00021-Jul-200604:00Not Applicable
Ms.rs.processingcore.dll9.0.2175.01,669,92021-Jul-200604:01Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2175.075,55221-Jul-200602:25Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2175.0163,10421-Jul-200603:59Not Applicable
Msadomdx.dll9.0.2175.0502,56021-Jul-200602:26Not Applicable
Msmdlocal.dll9.0.2175.048,828,70421-Jul-200604:02Not Applicable
Msmgdsrv.dll9.0.2175.012,908,32021-Jul-200604:02Not Applicable
Adomdclient.dll9.0.2175.0543,52021-Jul-200602:26Not Applicable
Reportbuilder.exe9.0.2175.05,389,08821-Jul-200602:31Not Applicable
Reportingservices.dataextensions9.0.2175.0154,40021-Jul-200603:59Not Applicable
Reportingservices.diagnostics.dll9.0.2175.0604,96021-Jul-200604:00Not Applicable
Reportingservices.htmlrendering.dll9.0.2175.0301,85621-Jul-200604:00Not Applicable
Reportingserviceslibrary.dll9.0.2175.01,030,94421-Jul-200604:01Not Applicable
Reportingservicesservice.exe9.0.2175.014,62421-Jul-200603:59Not Applicable
Reportingserviceswebserver.dll9.0.2175.01,325,85621-Jul-200604:01Not Applicable
Rs.excelrendering.dll9.0.2175.0330,52821-Jul-200604:00Not Applicable
Rswebuserinterface.dll9.0.2175.01,239,84021-Jul-200604:01Not Applicable

WORKAROUND

To work around this problem, do not use Report Manager to view a report. Instead, use a URL request to directly access the report server.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

When the problem occurs, you may find the following call stack information in the Report Manager trace log:
w3wp!ui!d!3/17/2006-15:58:10:: e ERROR: The request failed with an empty response.
w3wp!ui!d!3/17/2006-15:58:10:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The request failed with an empty response.

   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()

   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)

   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.ValidateConnection()

   at Microsoft.Reporting.WebForms.ServerReport.GetServerVersion()

   at Microsoft.ReportingServices.UI.ViewReport.Control_Init(Object sender, EventArgs args)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.AddedControl(Control control, Int32 index)

   at System.Web.UI.ControlCollection.Add(Control child)

   at Microsoft.ReportingServices.UI.SharedArea.Control_Init(Object sender, EventArgs args)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Control.AddedControl(Control control, Int32 index)

   at System.Web.UI.ControlCollection.Add(Control child)

   at Microsoft.ReportingServices.UI.ReportWrapperPage.Page_Init(Object sender, EventArgs e)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Web.UI.Control.OnInit(EventArgs e)

   at System.Web.UI.Page.OnInit(EventArgs e)

   at System.Web.UI.Control.InitRecursive(Control namingContainer)

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Modification Type:MajorLast Reviewed:8/29/2006
Keywords:kbsql2005sp1fix kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB918555 kbAudITPRO kbAudDeveloper