FIX: Error message when you render an SSRS report that uses the rc:Toolbar=false parameter in the URL: "An error occurred within the report server database"

Article translations Article translations
Article ID: 2739213 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 2 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 R2 Service Pack 2 fix release.
Expand all | Collapse all

Symptoms

Consider the following scenario:
  • You configure a report server to use cookieless sessions by setting the UseSessionCookies report server system property to False in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • You configure a SQL Server Reporting Services (SSRS) report to update automatically every x seconds.
  • The report uses the rc:Toolbar=false parameter in the URL.
  • You render the report.
In this scenario, the report displays correctly the first time. However, when SSRS tries to update the report automatically, you receive the following error message:

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help
Cannot insert duplicate key row in object 'dbo.SessionData' with unique index 'IDX_SessionData'. The duplicate key value is (onxrpsralint5h55w1tjfcn1). The statement has been terminated.


Resolution

Cumulative update information

Cumulative Update 2 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1
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 2012 SP1 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative Update 5 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update package 5 for SQL Server 2012
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 2012 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 R2 Service Pack 2. 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:
2754552 Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2
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 Service Pack 2 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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

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, do not use the rc:Toolbar=false parameter in the URL, and change the cascading style sheets (.css) files that define styles for the report toolbar in HTML Viewer and for Report Manager.

For more information about how to customize style sheets for HTML Viewer and Report Manager, go to the following Microsoft TechNet website:
Customizing Style Sheets for HTML Viewer and Report Manager

More information

For more information about report server system properties, go to the following Microsoft Developer Network (MSDN) website:
Report Server System Properties
For more information about URL access, go to the following MSDN website:
URL Access

Properties

Article ID: 2739213 - Last Review: January 24, 2013 - Revision: 4.0
Applies to
  • Microsoft SQL Server 2008 R2 Reporting Services
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Web
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Standard
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2739213

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com