SharePoint Secrets

Ran into an odd little issue this morning where users in a publishing site could not create new pages. The reason they couldn’t create a new page turned out to be because they did not have read rights on the masterpage gallery. The symptoms are basically access denied pages when any user with full control or design rights chooses to create a page in a publishing site. When they create the page they get the typical “Error: Access Denied” page and can either sign in as another user or request access. I resolved it by going to Site Actions -> Site Settings -> Modify All Site Settings . Select the option Page layouts and site templates and then select the option to Reset all subsites to inherit these preferred subsite template settings for both subsites and page layouts. This is sort of related to the publishing the default master page; an obvious permission issue.

Windows XP has a feature called "My Network Places" where you could very easily make a website folder (SharePoint folders) or FTP folders available in Windows Explorer. Windows 7 also has the feature, but it is somewhat hidden. Here’s how to make it work in Windows 7. 1. Using Internet Explorer browse to the location that you’d like to make available in Windows Explorer. 2. In SharePoint click the ‘Action’ button, and select ‘Open in Windows Explorer’ 3. A new explorer window will open. 4. Right-Click the folder that you would like to make available in Windows Explorer and select ‘Copy address as text’. 5. Right-click Computer, and click "Add a network location". 5. Click Next. 6. Select ‘Choose a custom network location’. 7. Paste in the URL copied in step 4. And, click ‘Next’. 8. Give the location a name: 9. Click ‘Finish’ 10. This new location will now be available in windows explorer by the name provided.

Problem Users report the following error when attempting to access a document library in SharePoint. An error occurred during the processing of /site/SharedDocuments/Forms/AllItems.aspx. Code blocks are not allowed in this file. Explanation Ever so often I have clients contact me with a SharePoint library fully corrupted reporting an error such as “Code blocks are not allowed in this file”. The error is, in fact, limited to a specific view but it’s usually the default view, therefore the error makes the library appear like it is completely inaccessible. The root cause of the error is simple – a user replaced a view file from the /forms/ folder of the document library, typically “AllItems.aspx” such as the screenshot below suggests. Typically this occurs when the user is using explorer view but I’ve heard of manifest presentations of this error as well. Solution – Option 1 1) Open site that contains the library 2) Click on “Site Actions” >> “Site Settings” to view the site sett...

Recently we noticed that one of our site collection's site actions menu items has no Create menu. The site actions menu has only View all site content, View Reports and Manage and Content Structure. This site collection has enabled publishing features. We found that even Farm admin/Site collection admin are not able to see "Create" menu. When we try to the URL "../_layouts/create.aspx" got access denied error message for every one including Farm admins. After we did several investigation, we found that the site collection was locked and it was in Read-Only mode. Solution: Go to Central Administration > Application Management > Site Collection Quotas and Locks Select the Site Collection and chose the correct option to unlock the site as below. Lock status for this site: Not locked Adding content prevented for Read-only (blocks additions, updates, and deletions) No access We selected the Option called "Not-Locked" after that it start...