Skip to main content

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm:

Report Server has encountered a SharePoint error. ( rsSharePointError)
Access to this Web Site has been blocked. Please contact the administrator to resolve this problem.

This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm.

After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue.

We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this error was related to MOSS or SQL server. We checked the reporting services log files but could not find much details on this error. Finally the vendor looked up his case archives and found that this error could occur if site collections are locked or set as No Access in Quotas and Locks page in Application Management. I ran the following command to check on the lock status of site collections of each web application:

stsadm –o enumsites –url -showlocks

We found out that there were couple of sites locked in mysites web application and I unlocked these sites. Then I navigated to the Report Server Web Service URL and I did not get the error, instead I saw a list of sites. I assume these sites are the ones which have reports deployed. I checked with the vendor who was working with me on this but they could not tell me the logic behind what sort of sites were populated in that page.


Labels:

Comments

Anonymous said…
Perfect, just the solution I needed.
June 23, 2011 at 10:40 PM
Anonymous said…
Hello there! I truly delighted in reading your write-up. Hope you create even more similar to this!


my homepage - home page ()
June 10, 2013 at 12:01 PM
Anonymous said…
These are in fact fantastic ideas in on the topic of blogging.
You have touched some good factors here. Any way keep
up wrinting.

Also visit my blog post :: regular expression tool online
June 12, 2013 at 1:14 AM
Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more