Deadlocks on Reporting Service Database due to unsync data sources. RRS feed

  • Question

  • We have a SharePoint farm with 3 web front end servers and 2 app servers. DBs are setup in AlwaysON.

    Recently we had an issue that SharePoint SSRS Reports started to behave abnormally - slow in performance and sometimes no result at all. After looking at log files for reporting services we found that reports were getting timed out due and it was pointing towards DB server with Disk issue or connection issue "An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database". We found the problem was locking on Reporting Service Database. And the reason for that is explained here:


    We fortunately found the data source and just renamed it so that it get synced. It immediately solve the issue. But we are wondering why the sync fails for data sources at first place and what is the permanent solution. The article above is just a work around.

    I found another article which talks about the SSRS cache cleanup issue. Not sure if that is the case here. The solution there suggested is to apply CU 11 for SQL 2012 SP1.

    It will be great if someone can help us with permanent solution. Should I go for CU 11 or first SQL SP 2 and then CU 4 as explained here: https://support.microsoft.com/en-us/kb/2972463

    Note: We have SQL Server 2012 SP1 CU 6.


    Kunal Abrol


    Friday, January 1, 2016 6:00 AM


  • Is Document Library Versioning enabled where your RDL or RSDS files reside? Versioning can cause this issue, and is not supported with SSRS containing report file types.

    Trevor Seward


    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, January 1, 2016 6:20 PM