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

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

Page layout HTML changes not reflected in associated aspx

I had this issue for quite sometime with a SharePoint Online project I was working on. I use Design Manager to create a new layout page and add snippets to the html layout. I would create webpart zones, add my webpart snippets on to the html, save and publish but the resulting aspx page wouldn't have any of my webparts in it. I checked it from SPD 2013 and everything looks perfect, I can see all the code snippets in there. It was really strange and I had no clues. I had some content search webparts in the layout and one content editor webpart with a link to a text file with some css in it. After countless hours on the internet I read about few other people having similar issues when they had custom css on the layout pages to hide quick launch. I tried removing my content editor webpart and everything seems to be normal. A new page created using the layout had all the webparts in it and even the layout preview was displaying fine. I needed this css somewhere on the page and ...
Post a Comment
Read more

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more