FIX: "User cannot be found" error message in SSRS 2008 R2 or in SSRS 2012 after the logon name is changed in Active Directory

Applies to: Microsoft SQL Server 2008 R2 Service Pack 2SQL Server 2012 DeveloperSQL Server 2012 Enterprise More

Symptoms


Consider the following scenario:
  • You configure an instance of Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) or Microsoft SQL Server 2012 Reporting Services (SSRS 2012) to use the Microsoft SharePoint integrated mode.
  • You have a domain user who deploys some SSRS 2008 R2 or SSRS 2012 reports in a SharePoint website.
  • You change the logon name for the user in Active Directory, and then you add the new logon name to the SharePoint website.
  • You delete the old logon name from the SharePoint site, or you use the MigrateUser utility to synchronize the SharePoint user profiles.
  • You try to perform one of the following operations:
    • You edit the SSRS reports that you deployed by using the previous logon name in Report Builder.
    • You manage subscriptions on the SSRS reports that you deployed by using the previous logon name.
In this scenario, you receive the following error message:
User cannot be found.


Notes:
  • You can view the reports that you deployed by using the previous logon name.
  • You can deploy new reports or manage subscriptions on the reports that are deployed by other users.

Resolution


Cumulative update information

Cumulative update 6 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2728897 Cumulative update package 6 for SQL Server 2012
Note 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 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 2 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1
Note 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 SP1 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

Cumulative Update 4 for SQL Server 2008 R2 Service Pack 2 (SP2)

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
2777358 Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2
Note 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 2008 R2 Service Pack 2 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Workaround


To work around this issue, apply one of the following methods:
  • Create a new logon that has the original name of the user, and then add it to the SharePoint website.
  • Delete the reports that were deployed by using the previous logon name from the SharePoint website, and then use the new logon name to re-deploy the reports.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.