Wednesday, April 17, 2019

Edit page issues with Full control permissions

Hi All,

I was struggling with an issue where the user couldn't able to edit the home page of the site despite having full control permissions to the site via. Owners group. For the meanwhile, I've added user to Site Collection Admin group. But that is not a proper solution to the issue.

I deep dive through internet to identify the root cause. After lot of research, I got to know that if there are no permissions for 'Master Pages and Page Layouts' library then other than site collection administrator no one can edit the pages.

I checked the same to the site and observed that there are unique permissions for 'Master Pages and Page Layouts' library and no one other than site collection administrator can see its content. I made the library inherit permissions from parent and removed the user from site collection admin group as I did earlier. Luckily, it worked and user can able to edit the page without having herself to get added in site collection administrator's group. :)

Thanks,
Kunal Basu

Tuesday, April 2, 2019

Your account is in a bad state - issue

Hi All,

I was facing couple of issues in my project. Here are the following-


  1. User is unable to open the SharePoint Online site in SharePoint Designer. The moment user is trying with his credentials, he received the error message - "Your account is in bad state".
  2. User is trying to update in InfoPath list form by making changes in template.xsn file for that list. He made the changes but when he's trying to publish the form - he get's the error: "Your account is in bad state".

While analyzing the issue, I got to know that legacy authentication is disabled for SharePoint online sites. Hence, modern authentication is enabled. While SharePoint Designer wasn’t natively designed to work with Modern Authentication (ADAL) there are updates available that allow it to work.Most Office 2013 applications will be able to successfully use modern authentication once the EnableADAL=1 registry key has been set. See the below link for the article.



You can refer to the below link for InfoPath related issue as the root cause is same for both SPD and InfoPath Designer.



Thanks,
Kunal