When 'Create Subsites' permission level removed from Web Application, error activation/deactivating features
All, in a related post, I looked for a way to disallow users to create there own subsites. Everything was working as planned, but we found that when 'Create Subsites' Permission level is unchecked, we get an access denied everytime we try to activate / deactivate a Site/Web Feature in the Manage Feature Page. Anybody have the key to this puzzle? Why would subsites creation have any relation to activating features? Description of Create Subsites -Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites. Jonathan Herschel
May 12th, 2011 1:36pm

Jonathan, This is a known issue and is by design. Quote from the article. http://www.euri.com/Blog/tabid/85/EntryId/46/MOSS-2007-Create-Subsite-permission-blocks-feature-activation.aspx "The “create subsite” right has a slightly expanded meaning than its literal interpretation. Not only does it allow/disallow the creation of subsites…but in its expanded form, it also allows/disallows site provisioning. Activating/deactivating a feature in essence provisions/deploys site-wide objects. In other words, activating a feature is a form of site provisioning which requires the right to provision sites which is expressed as the “create subsites” right in the UI. A few other nuggets of information/suggestions were given which might be helpful to you as you look to work around this issue: 1) Only features that deploy modules are affected by this issue. As such, users should be able to activate features [that don’t provision modules] without the “create subsite” right. 2) Allocate a farm-wide admin to do the activation whenever there is such failure in activating a feature. 3) Create a small application that leverages the object model to activate a feature with ‘CreateSite’ permissions although the site collection admin doesn’t have this permission." Sorry! V
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2011 2:41pm

Thanks. I tried #2, adding myself to have Farm Admin Group, but still doesn't work. I guess I will have to go with #3.Jonathan Herschel
May 12th, 2011 2:44pm

Farm admin does throw an access denied error. Let us know if #3 works. Will try it out too. V
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2011 2:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics