This week, I found out a very interesting fact: there is a limit to the number of Web Parts a page can have in SharePoint 2013. I know what you are thinking: How on Earth did someone find out there was a limit to Web Parts on a page in SharePoint. Or if you were me, it was, "Holy smokes that is crazy, but interesting!" A user came to us and reported that they were seeing the following error:
This error can stem from a few reasons:
- Users are adding too many web parts to the page. This is what I saw when my customer came across the issue.
- Users are creating too many personal views. Mr. Andrew Toh reported that this caused the issue for him. You can review his blog here: http://www.mysharepointadventures.com/2012/09/557.
There are a few ways to solve this issue.
- Be sure to communicate to your users that there is a limit. This is the best and easiest solution. The default limit is 50 web parts per page, so try to keep it under that number.
- Andrew mentioned in his blog (link above) that if you have users with too many personal views then they can hit this limit. Personal views act as web parts on the page, but they are just hidden. You can potentially remove the person's access to the site and then grant them access again, but they will lose all of their personal views.
- I think the best solution for both situations is to set the limit to a higher number. To do this, the following steps need to be completed (Please note that you will be doing an IISReset and may want to wait until after hours to not impact your users):
- First, log in to all the Web Front End (WFE) servers.
- On each WFE, open your IIS Manager
- In the left navigation bar, expand your server
- Expand your Sites folder
- Highlight the site (web application) that contains the problem site page
- On the right-hand navigation bar, click on Explore
- Open the web.config file with Notepad
- Do a CTRL+F or Find for the following phrase: <WebPartLimits MaxZoneParts="50" PropertySize="1048576"/>
- Change the value for MaxZoneParts from 50 to 100
- Save the file
- Open a command prompt as Administrator
- Type in "iisreset" and hit Enter.
- Repeat for the remaining Web Front End servers
Please note take note of the following:
- It is not the best idea to go in and manually edit the web.config file. For something as simple as this, it can be fine, however, the suggested route is using the API via Powershell for changes needing to be made.
- The Microsoft recommended maximum number of web parts per page is 100. Anything above this can cause performance issues. Feel free to review the details of the limitations at the following: https://technet.microsoft.com/en-us/library/cc287743.aspx
The main takeaway from this situation is that there are always limits to items in SharePoint. Be sure to remember that, as a user, your personal view count and existing web part count will make up the total number of web parts per page. You can experience this issue while others may not because of too many personal views. Be sure to keep in mind the effects of increasing the maximum allowed web parts as well. The higher the number, the more potential you have of negatively impacting your performance.
Thanks so much for stopping by. Go forth and conquer!