FIX: Report cache is not cleaned up when you use SSRS 2012 or SSRS 2014 in SharePoint integrated mode

Symptoms
Consider the following scenario:
  • You use Microsoft SQL Server 2012 Reporting Services (SSRS 2012) or SSRS 2014 in SharePoint Integrated mode.
  • You set the Data refresh options to Use cached data, and set the Cache options to On a shared schedule or On a custom schedule.
  • You configure the schedule that SSRS invalidates the cache and flushes out the cache.
In this scenario, an exception similar to the following is logged:
w3wp!schedule!e!<Date>-<Time>:: i INFO: Handling Event CacheInvalidateSchedule with data 4248182a-16b1-4c6a-b630-298cd24ae152.
w3wp!library!e!<Date>-<Time>:: i INFO: Schedule 591b959d-5754-4dc6-95b6-a988d8c4587a executed at 04/24/2014 20:30:07.
w3wp!schedule!e!<Date>-<Time>:: i INFO: Invalidating report cache for report /{59ee4a21-c7c4-49f7-b812-29f060672d08}/<Item Path>'
w3wp!library!e!<Date>-<Time>:: i INFO: Call to FlushCacheAction().
w3wp!library!e!<Date>-<Time>:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: , Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item '/{59ee4a21-c7c4-49f7-b812-29f060672d08}/<Item Path>'is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.;
w3wp!library!e!<Date>-<Time>:: e ERROR: Schedule 591b959d-5754-4dc6-95b6-a988d8c4587a failed. Error Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item '/{59ee4a21-c7c4-49f7-b812-29f060672d08}/<Item Path>' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.
After the exception occurs, the report cache is not cleaned up. This quickly increases the database size and it is never cleaned up.
Cause
The issue occurs because there is a known limitation in the product.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 4 for SQL Server 2014

Cumulative Update 2 for SQL Server 2012 SP2

Cumulative Update 11 for SQL Server 2012 SP1

About cumulative updates for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 2972463 - Last Review: 03/14/2016 07:33:00 - Revision: 4.0

SQL Server 2014 Reporting Services, Microsoft SQL Server 2012 Service Pack 1, Microsoft SQL Server 2012 Service Pack 2, SQL Server 2012 Reporting Services

  • kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2972463
Feedback