This hotfix also applies to Microsoft SQL Server 2012 Reporting Services.
Symptoms
Consider the following scenario:
-
You are running an instance of Microsoft SQL Server 2008 R2 Reporting Service (SSRS 2008 R2) or SQL Server 2012 Reporting Service (SSRS 2012) in Microsoft SharePoint integrated mode.
-
You have a report or subscription that was authored by a user who no longer has permissions on the SharePoint site collection.
-
A user who has the appropriate permissions on the SharePoint site collection tries to open the report or subscription.
In this scenario, the user cannot open the report or subscription. Additionally, the user receives the following error message:
Report Server has encountered a SharePoint error. (rsSharePointError)
Object reference not set to an instance of an object.Additionally, the following exception is logged in the report server log file:
Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.SharePoint.Objects.RSSPImpUser.get_LoginName() at Microsoft.ReportingServices.SharePoint.Utilities.CatalogItemUtilities.GetListItemUserLoginName(RSSPListItem item, String fieldName) at Microsoft.ReportingServices.SharePoint.Utilities.CatalogItemUtilities.CreateCatalogItem(RSSPFolder folder) at Microsoft.ReportingServices.SharePoint.Server.SharePointDBInterface.GetParentsForFolderOrFileRecursive(RSSPWeb web, RSSPFolder folder, RSSPDocumentLibrary docLib, Security secMgr, CatalogItemList parents) at Microsoft.ReportingServices.SharePoint.Server.SharePointDBInterface.GetParentsForFolderOrFileRecursive(RSSPWeb web, RSSPFolder folder, RSSPDocumentLibrary docLib, Security secMgr, CatalogItemList parents) at Microsoft.ReportingServices.SharePoint.Server.SharePointDBInterface.FindParents(ExternalItemPath objectName, CatalogItemList& parents, Security secMgr, IPathTranslator pathTranslator)Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 8 for SQL Server 2012 SP1 /en-us/help/2917531
Cumulative Update 11 for SQL Server 2012 /en-us/help/2908007
Cumulative update 9 for SQL Server 2008 R2 SP2 /en-us/help/2887606
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.