Server Error: Access Denied in SharePoint Designer 2013 - sharepoint

I am trying to add custom pages by using using SharePoint Designer 2013, but it throws Server Error: Access Denied when I try to add a new aspx page or edit aspx page.
I am site owner and have SharePoint admin access, still I couldn't figure out what went wrong and struggling with this issue for a long time.
When I check permissions with my user name.
Deny | Add and Customize Pages | Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Microsoft SharePoint Foundation-compatible editor.
I have tried with below command in Sharepoint management shell, not helpful.
Set-SPOSite -Identity https://.sharepoint.com -DenyAddAndCustomizePages $false

Have you resolved this issue?
If not, please check which site template you used for your site, and check the user's permissions on the pages library that is used to store the new pages or existing pages.
Then check the best practices about how to install SharePoint Designer 2013 for SharePoint Online, make sure you have followed it to install the CUs.
After that, please try again, compare the result.

Related

Cloned SharePoint Environment on Test Server - Pages Appear in Document Libraries but SharePoint Says They are Deleted

I have created a test SharePoint server to be as close to our production server as possible. Production SharePoint databases were backed up and restored to our test server. The three main web.configs (Central Admin, main site, Security Token Service Application) were modified to include our custom app settings.
The site comes up fine, logging in using both AD and our custom FBA membership provider works as well.
Certain pages are visible in the Site Libraries through View All Site Content and using SharePoint Designer but SharePoint says that the page(s) are not found if you try to view them or check them in. Not all pages are not available. If I delete a bad page and replace it with a copy from our production application, it displays fine.
I've already found and tried possible solutions such as restarting the Search Query and Site Settings Service and checking the Alternate Access Mapping. I also found a possible solution that has you go to Component Services and modify security relative to an OSearch14 property. I was not able to modify this since right clicking on the property did not pop up any menu options. I will continue to look into this.
Any Ideas? I appreciate any help.
Thanks.

team foundation server sharepoint web site access permissions

Please help.
Am newbie and have hit a snag with TFS and Sharepoint combo. Come from old school where in IIS you right click and set permissions of Web Site, and now I can't find the sharepoint sites in IIS 7 to actually give myself permissions.
When opening the localhost/ sites/ project in IE, i get an Error: Access Denied.
This is the sharepoint site that was set up by TFS when I added a project in Visual Studio 2010 to my TFS ProjectCollection.
How do I get access to the web site?
Regards
Permission is not give to the SP sites directly from IIS.
If you are or you know the SP Site collection administrator, ask them to give you the appropriate access to the SP site you are requesting. Otherwise, if there are no site collection administrators then go a level higher to the SP farm administrator, ask the farm admin to grant make you the site collection administrator for the SP Site collection you are trying to access. The team project site is located under a site collection.
From there you can give other users access to the appropriate SP resources using Site Actions > Site Permissions.
You should be given the permissions inside SharePoint by site collection administrator.
Site collection admin should navigate to localhost/sites/{tfscollection}/{tfsproject}, click Site settings and then People and groups link.
From there, you need to be added to the site and given the appropriate permissions.
There's a really nice utility that makes it easy to view/edit permissions on TFS, SharePoint and Report Server at the same time.
http://tfsadmin.codeplex.com/

Sharepoint secured folder visible by direct url

I have a folder in a Sharepoint Foundation 2010 document library with unique permissions so only a specific group of users can access.
The folder is created only in some cases and it's important that other users can't know when the folder exists or not.
But if a user with no access permissions types the direct url doesn't get an error, but a page showing an empty folder.
It's good that he can't see the content, but it's not good that he can know that the folder is there.
Is it a Sharepoint security bug?
[EDIT]
I made a test on Sharepoint 2007. Users with no access on a folder get a Access Denied Error if they type the direct url.
I think the behavior on Sharepoint 2010 is a real bug.
No, it's not a bug. This is how it has always worked.

Why can't users in the "Visitors" group access my SharePoint 2010 publishing site. It works when i promote them to the "Members" group

When I place a test AD account in the Visitors group they are unable to view any pages on my new intranet site. The users receives the "Error access denied" sharepoint screen and indicates that the account was able to authenticate, but that some authorisation rule is permitting it from viewing the page.
When i remove then and place them in the Members or Owners groups they are able to view the pages as well as perform the expected functions like editing content and creating subsites.
Interesting, while in only the Visitors group, users can view the "All Site Content" page that is located here: /_layouts/viewlsts.aspx but not /pages/default.aspx.
Has anyone experienced this before?
Environment info:
1 Web application, 1 Site collection using the Publishing Portal template. A few custom master pages, lots of custom page layouts and user controls. All deployed via features.
Sharepoint 2010 Standard edition, 64bit running on Windows Server 2008 against SqlServer 2008 Enterprise Edition. Authentication is against AD, not any other forms auth providers etc.
One likely reason for such behavior is that it tries to access a resource on a page which might not have been published to a major version. For example, if versioning was turned on on images library and an image's version is 0.1, if that image was used on version 1.0 (published) of the page, the server would deny access to the visitor and ask for credentials.
Make sure following:
At least one major version of the page exists (page was published at least once)
All resources (images, movie files etc) used on the page are published (to major version)
You can use "Draft Check" button on Page Tab of the Page's ribbon to check the unpublished resources that are used by the page.
I had the same issue and I've finaly found out how to do this:
If you check OOB group access, you can find that Visitors group has limited number of pages where it has granted access.
Navigate to /yourweb/_catalogs/masterpage. Here you'll find many
.aspx files (including default.master).
Open this default.master`s permissions and you see it inherits from
Master Page Gallery.
Click this permissions inheritance and you can see that Master Page
Gallery permissions are not inherited from site collection
permissions.
Give here the Contribute permissions to Style Resource Readers (or
modify it as you'd like) and all users will have access to this web
with no permissions to edit etc..
I had a similar issue and the thing I noted in your Environmental comments was the custom master pages. Go to your Site Settings and ensure that your custom master pages have been published. If you need to publish them also check the corresponding html pages after they have been published as they may need to be republished also.
This worked for me.

Cannot save layout page in Moss

I am trying to update a layout page in Sharepoint Designer but when I click Save I receive an Access Denied error. I can see that the layout page is created by the system account. I am in the site owners group so I think I should be able to make modifications to the page.
Any help?
The page could be checked out by the System Account or never had a published version, also, site owners have limited permissions in the site collection (where the page layouts reside)

Resources