SharePoint Online (SPO) List Items Read-only

Issue: I came across a situation where certain items in a SPO List was read only and that too for just one user and this user is also a Site Owner with Full Control on the List and Site.

It was a strange situation as other users were able to edit those List items - the affected user tried Data Grid option as well but couldn't edit. This was similar to item level permission set on the List but in this case it wasn't set.

Resolution:

After some external support it was found that this was caused by List Sync, once the sync was stopped the items were editable. Here are the steps:

1. Go to their List home page (App menu in the upper right of SharePoint -> All Apps -> Lists).

2. Find the list you'd like to stop syncing.

3. Click the ... button pictured below.

4. If the list is syncing, there will be a menu option for "Stop Syncing". Click on stop syncing to stop the syncing.

If you want to disable sync for all users for a particular List then:

Navigate to List Settings - Advanced Settings - set Offline Client Availability to No.

It was a simple fix at the end but took a while to figure out.

Comments

"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.

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:

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 er

My IT Experiences

Search This Blog