FIX: Report Builder 3.0 stops responding if SSRS 2008 R2 uses forms authentication

When Microsoft SQL Server 2008 R2 Report Builder 3.0 connects to an instance of Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2), Report Builder 3.0 might stop responding if SSRS 2008 R2 uses forms authentication. Additionally, Report Builder 3.0 does not return control in this situation.

Note To recover from this issue, manually stop the MSReportBuilder.exe process.

This issue occurs because a limit for the number of connections that are between Report Builder and the instance of SSRS 2008 R2 is reached.

When Report Builder 3.0 sends web requests to the report server, Report Builder 3.0 does not drop an underlying connection.

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in cumulative update package 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:Note 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 R2 fix release. We recommend 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:

To work around this issue, increase the value for the connection limit that is reached. To do this, follow these steps.

Important We recommend that you back up the MSReportBuilder.exe.config file before you follow these steps.

1. Add the following sectionGroup element to the <configSections> section of the MSReportBuilder.exe.config file for Report Builder 3.0:

   <sectionGroup name="system.net" type="System.Net.Configuration.NetSectionGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
   <section name="connectionManagement" type="System.Net.Configuration.ConnectionManagementSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
   </sectionGroup>

2. Add the following system.net element to the <configuration> section of the MSReportBuilder.exe.config file for Report Builder 3.0:

   <system.net>
   <connectionManagement>
   <add address="*" maxconnection="100"/>
   </connectionManagement>
   </system.net>

   Note When the maxconnection setting is set to 100, a limit of 100 queries that use separate connections is set. You might have to increase this value to work around the issue.

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

For more information about SQL Server 2008 R2 Report Builder 3.0, visit the following Microsoft website: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: