Select the product you need help with

You receive an error message when you try to browse directly to the SSRS 2008 R2 report server after you create a SharePoint claim site

Article ID: 981588 - View products that this article applies to.

SYMPTOMS

Consider the following scenario:

You have a computer that is running Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) in SharePoint Integrated mode together with a SharePoint 2010 farm.
You create a SharePoint 2010 Web application that consists of one or more sites and that uses a claims-based authentication provider.
In Windows Internet Explorer, you try to browse directly to the report server by typing the following URL:
http://<host name>/reportserver

In this scenario, you receive the following error message:

Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> Microsoft.SharePoint.SPException: The specified user <user name> could not be found.

Back to the top | Give Feedback

RESOLUTION

Service pack information for SQL Server 2008 R2

To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2527041

(http://support.microsoft.com/kb/2527041/ )

How to obtain the latest service pack for SQL Server 2008 R2

Back to the top | Give Feedback

MORE INFORMATION

Browsing directly to the report server is not supported in SSRS 2008 R2. Therefore, do not browse to the report server directly. Instead, use the report server proxy on the SharePoint Web site that uses the appropriate authentication provider. The following is an example of a URL that lets you access the report server by using the report server proxy on the SharePoint Web site:

http://<SharePoint_site>/_vti_bin/ReportServer

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in SQL Server 2008 R2 Service Pack 1.

Back to the top | Give Feedback