Skip to main content

SharePoint 2013 - Can't create Publishing Site (Access Denied)

I've stumbled upon an interesting issue this past week while working for a client and wanted to share just because I almost pulled my hair out trying to figure it out. I've provisioned a site collection with about a handful of sub-sites, each with their own unique permission structure (Owners, Members, Visitors, etc). I was surprised to find out that users that were part of Owners group could not create sub sites and encountered Access Denied error each time, like the one below.


A bit baffling, especially since Owners SharePoint security group has Full Control rights. After studying the ULS log it seemed as if everyone except for the top level Site Owners (and Site Collection Administrators) did not have rights to Device Channels list. A Device Channel basically controls how content is rendered within the Publishing Infrastructure in SharePoint 2013. For more on Device Channels please go here: Intro to Device Channels

Solution

To remedy this, I added Restricted Readers group to the permission set of Device Channels list:

1. Navigate to Site Settings, Device Channels. Or if it is easier just navigate to: http://YOUR_HOST_HEADER/DeviceChannels
2. Click on List Settings in the server ribbon
3. Click on Permissions for this list under Permissions and Management
4. Select Grant Permissions in the server ribbon and add Restricted Readers group


5. Now add users to Restricted Readers group. You can be selective here and add only a group of users, I simply added All Authenticated Users.

I hope this saves some time if you run into the same issue.

Comments

  1. Steve JefferyDecember 19, 2013 at 10:16 AM

    Thanks, this helped me!

    My issue was that for a custom site template I was getting an error thrown when members group was granted permission to create sub-sites. Assigned members group read permissions to this list and all good!

    Would love to know why this was necessary though when an OOTB site template worked fine without it...

    ReplyDelete
    Replies
    1. Ismar AlikadicDecember 19, 2013 at 10:40 AM

      Glad this was helpful!
      I believe this was noted as one of the known issues in RTM and finally addressed in the CU.

      Delete
    2. Steve JefferyDecember 20, 2013 at 4:03 AM

      The issue occurs in SharePoint online so not sure if it is addressed yet I'm afraid.

      Many thanks again - saved me hours of searching!

      Delete

Post a Comment

Popular posts from this blog

SharePoint Server Search - Error Starting

Problem I recently ran into this snag at a client site while setting up the Search Service Application.  I was able to create the service application without a problem however when I attempted to start the SharePoint Server Search service (Manage services on server page) I kept getting Error Starting . After taking a peak at the logs I found the following: An attempt to start/stop instance of service SharePoint Server Search on server did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) I double/triple checked the permissions and made sure that my Farm Administrator account was a member of WSS_WPG and WSS_ADMIN_WPG groups, and that those groups had full control permissions to the C:\Windows\Tasks and C:\Windows\Temp folders. Resolution I nearly lost hope when I remembered my old lost friend called STSADM.EXE. Just like in the old da...
Post a Comment
Read more

SharePoint 2013 - Start a Site Workflow using a Custom Action

In recent travels I've encountered what seems to be either a product limitation or a bug. After digging around some it appeared that I wasn't the only one facing this challenge, and unfortunately there wasn't a concrete enough solution or workaround out there. Hence the blog post hoping to save some of you the unnecessary hair-pulling which I had to endure. My task was fairly simple; "Start a Site Workflow using a Custom Action button". The first part, creating a Custom Action, is trivial. This can be done in Visual Studio or SharePoint Designer. For the sake of simplicity I used SharePoint Designer. Create a Custom Action button Start up SharePoint Designer 2013 and connect to the desired site. From the left navigation select Lists and Libraries. I'm using a simple list called "List One". Boring name, but easy to follow. :) Click on the list name to manage list settings. From the ribbon select Custom Action button then click View Ribb...
Post a Comment
Read more

SharePoint 2013 - Simple Glossary using "HTML Form Web Part"

Introduction At some point you probably thought about incorporating glossary functionality as a part of a larger solution, or perhaps you were simply looking for providing a more intuitive way of filtering hundreds of items within a List or Library. Now there are countless web parts out there that you can either purchase or download from the SharePoint Store free of charge, and they all come with their own set of bells and whistles.  However, if you are looking at building one yourself, well look no further. To accomplish this we will need three major ingredients: SharePoint Page (either Wiki or Publishing will work) SharePoint List/Library with some content (Files/Items) HTML Form Web Part Let's Implement In this post I’m using a simple Wiki page, but you can also use a Publishing page as well.  We just need a canvas to display our glossary. I presume you already have a list or library that contains some content which is applicable to this concept....
12 comments
Read more