Tallan Blog

Tallan’s Experts Share Their Knowledge on Technology, Trends and Solutions to Business Challenges

SSRS Error After Cumulative Updates Applied


After installing windows updates, SharePoint 2013 Service Pack 1 and the March 2016 Cumulative Update some users reported a problem with SSRS reports. They were receiving the following error message.

“Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item ‘http://sharepoint/sites/SiteName/LibraryName/FileName.rdl’ cannot be found.”

The error was occurring sometimes as soon as they clicked the link to the RDL file and sometimes the report viewer would come up and the error appeared when attempting to run the report.

I reviewed the ULS Logs and found the following errors:

“Cannot find site lookup info for request Uri http://webservername:12345/{guid}/ReportExecution.svc”

“Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item ‘http://sharepoint/sites/SiteName/LibraryName/FileName.rdl’ cannot be found.;”

I did some research on the errors and found a few posts from people who had similar issues and they had success deleting and re-adding the Reporting Services Service Application. I decided I didn’t want to do that if I didn’t have to so I thought I would try to re-provision the service application first. I ran the following PowerShell.

Add-PSSnapin microsoft.sharepoint.powershell


# Review the list of Service Applications to find an appropriate DisplayName to use for matching in the next command

$rssa = Get-SPServiceApplication | ?{$_.DisplayName -match “Reporting Services”}


#You should see information about the Reporting Services Service Application. If not double check the value used in the match above.


After the Provision command completed I tested some of the RDL files again and was able to successfully run the reports without error.


Learn more about Tallan or see us in person at one of our many Events!

Share this post:

2 Comments. Leave new

You have no idea how much this post helped me. Wow, check the alternate access mappings, check privileges in SQL server, check etc\hosts, check, check, check…. NOPE: reprovision the SSRS SharePoint service, and it worked like a charm. Many thanks.

Awesome Totally Awesome, yest it’s late 2019 and we are still creating SP 2013 farms with SSRS, this worked for me! You are the Best!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>