Hi,
This is my first post here and unfortunately I’m reaching out for help rather then contributing in a more beneficial way.
As title says we have a site collection where only SCA can create subsites (or change the design of the site for that matter), we are running SharePoint 2013 SP1.
Site Owners can not create sub sites.
Top level site is a portal site, subsites are team sites etc..
We upgraded from 2010 to 2013 however I’m not sure when users became unable to create subsite, I suspect it may have been when we move mysites from our sharepoint-80 web app to its own web app. We don’t use custom master pages or web parts however we run nintex.
I’ve tried the following:
- Create custom Permission levels with manage permissions. create subsite, manage website, enumerate subsite in addition to adding users to the site owner group.
- Ensured that users have read permission on the master page gallery
- Disable and re-enable publishing feature (This was recommended to me but did nothing)
If i create a new web app and site collection its fine however the site collection in question is the main intranet site.
When a user clicks to create a new site they receive the _layouts/15/newsbweb.aspx page no problem when they click on create they receive: “Sorry, you don’t have access to this page ” message.
ULS logs contain:
1st error
Failed to create modules from onet.xml when provisioning site at url “http://sharepoint/testsite“ with site definition “(null)”.
2nd error
Leaving Monitored Scope (Creating Web testsite). Execution Time=1900.1595
3rd error:
SPRequest.CreateWeb: UserPrincipalName=i:0).w|s-1-5-21-2047479520-744375764-1042822891-2048, AppPrincipalName= ,bstrUrl=http://sharepoint/testsite ,bstrTitle=testsite ,bstrDescription=<null> ,nLCID=1033 ,bCreateUniqueWeb=False ,bstrAppWebDomainId=<null> ,bConvertIfThere=False ,bCreateSystemCatalogs=True
If any one could point me in the right direction on how to resolve this it would be greatly appreciated.
Cheers
Ryan
Thanks for the suggestion. I had that in the back of my mind, but I one thing that I try to avoid is having to tell the users that they will not have access to their stuff temporarily because that really fires them up.
I’ve been working with Microsoft (great engineer) and we actually been collectin ULS logs and he’s been scrubbing them. Believe it or not, this is what resolve 99% of my issue, http://shipoint.com/tag/hidden-taxonomy-list/. The other 1% is i can’t create a site using the Community site template with Unique permission. Every other templates work with Inheritance and Unitque, except for the Community template. I’ll let you know more as we resolve the 1%.
Cheers!
No problem hope i can help or atleast point you on the right path.
I also had mysites on a different webapp however at one point it was on the same webapp as the problematic site collection.
If your experiencing the symptoms where users can create some subsites but not those based on teamsite or project site templates my advice would be to back up current mysites and perform the technet resolution then restore your mysites to the new webapp.
Thanks for the reply. I’m hesitant to delete the Mysites host because it is already on its own web application and we have live data from the users.
I will explore it a little bit more and see if I can avoid the fix from the technet article.
Thanks again.
Yeah mate worked it out my resolution is in this technet solution here:
Any luck with this issue? I’m experiencing the same thing and I’ve had a case open with Microsoft for at least 4 months and still no resolution.
