FIX: "The specified user DOMAIN\Username could not be found" error when you create SharePoint document library subscriptions in SSRS 2012
This hotfix applies to Microsoft SQL Server 2012 Reporting Services (SSRS 2012).
Assume that you have a SharePoint web application that is configured to use Security Assertion Markup Language (SAML)-based claims authentication in SSRS 2012. You try to create SharePoint document library subscriptions on the web application. In this situation, creation of the subscriptions fail, and you receive an error message that resembles the following:
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension parameters is not valid for the following reason: Failed to validate the delivery setting PATH. The specified user DOMAIN\Username could not be found.
This issue occurs because SSRS 2012 passes a classic authentication encoded logon name to the SharePoint web application instead of a logon name that is SAML claims encoded. Additionally, a SAML claims-enabled SharePoint web application calls the EnsureUser method to pass a classic authentication logon name.
Cumulative update information
Cumulative update 5 for SQL Server 2012 Service Pack 1The 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 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2861107 Cumulative update package 5 for SQL Server 2012 Service Pack 1Note 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 Service Pack 1 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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2866504 - Last Review: 07/15/2013 16:04:00 - Revision: 1.0
Microsoft SQL Server 2012 Service Pack 1
- kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2866504