How can I resolve my issues with Reporting Services and SharePoint 2010 Integration?
Posted on 2011-03-25
I have built a SharePoint 2010 Farm with an application server, 2 web front end servers, and two SQL servers, (one for the main SharePoint Data, and one for Reporting Services). I am able to configure the Reporting Services Integration and I beleive I can add a Report Server to the Integration as it accepts my server name and instance. The problem is when I click on the next section to Set Server Defaults, or if I go to Site Settings and click on any of the links for Reporting Services, I get the following error:
The request failed with HTTP status 401: Unauthorized.
I looked at the correlation ID in the ULS Logs and get the following:
Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
I looked around the Internet for similar issues and many people were mentioning Kerberos being misconfigured. I spent some time going over my SPN configurations and everything seemed to be setup. I am by no mean an expert when it comes to Kerberos so I could be mistaken though.
As a final test to try and rule out Kerberos as a culprit, I changed the configuration in the Reporting Services Integration from using the URL with the FQDN of the Reporting Server, to the URL with the IP address of the Reporting Server as I understand that would use NTLM to authenticate. Once I made the changes and click on the links, I was still getting the same error on the screen and in the ULS logs.
I can successfully access the Web Service URL listed in Reporting Services Configuration Manager, and when I enter that URL into the Reporting Integration section of Central Admin everything checks out okay.
So far, the only way I have been able to get reporting to load without the errors is to change the configuration in the Reporting Services Integration area to use a Trusted Account instead of Windows Authentication.
Does anyone have any ideas as to what I may have done wrong, or not done that might fix this issue?