Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.
Symptoms
Consider the following scenario:
-
You install Microsoft SQL Server 2008 Reporting Services (SSRS 2008) on a computer.
-
You configure SQL Server 2008 Reporting Services to run in the SharePoint Integrated mode.
-
You run an application that uses a web reference to the ReportExecutionService proxy. This application calls the ReportExecutionService.Render2 method to generate a SSRS report in a specific format. A large amount of data is queried for the report.
In this scenario, the application stops responding for 100 seconds, and then the application encounters a SoapException exception while the report is being generated. Additionally, you receive the following error message:
A first chance exception of type 'System.Web.Services.Protocols.SoapException' occurred in System.Web.Services.dllError occurred in report creation System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> The operation has timed outat System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[]parameters)
Cause
This issue occurs because the HTTPWebRequest object for the ReportExecutionService proxy times out after 100 seconds when SSRS 2008 is configured to run in the SharePoint Integrated mode.
Resolution
Cumulative update information
SQL Server 2008
The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around this issue, use one of the following methods.
-
Call the URLAccess method to create a custom HTTPWebRequest object that does not have a time-out value.
-
Wait until the report is available in the cache of SSRS, and then call the Render2 method.
Note The report may be available in the cache of SSRS after this issue occurs.
References
For more information about ReportExecutionService.Render2 method, visit the following Microsoft Developer Network (MSDN) website:
General information about the ReportExecutionService.Render2 methodFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, 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
