I came up with this error when I manually created a ‘Pages’ library and was trying to create New page in the library.

The site is not valid. The ‘Pages’ document library is missing.   at Microsoft.SharePoint.Publishing.PublishingWeb.get_PagesList()
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.BaseP….

…agesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The issue is that the ‘Pages’ library is created automagically by a Team Site template but not with a Blank Site template. My quickie solution was to recreate the new site that I was just starting and use the Team Site template instead of the Blank template and just remove the other components that I did not need.

I am sure there is a better way but I’ll look for it later. Expedience is, as always, the driver.

This is really a part of a longer story but I wanted to get this bit documented before I lost track of which error occurred when.

I was following this blog reference in order to fix something else but had another error occur mid-process.

Basically the instructions are:

1. Disable Publishing in the site
2. Disable Publishing in the site collection
3. Enable Publishing in the site collection
4. Enable Publishing in the site.

The error occurred when trying step #3 to re-enable the publishing.

The EXECUTE permission was denied on the object ‘proc_putObject’, database ”, schema ‘dbo’.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Bool…..

…..lingJobDefinitions(SPSite site)

It appears that the Disable option is not permission controlled while the enable option is. What I discovered was that while the service account had permissions on most of the sharepoint db’s it was not dbo_owner on the config DB. I found this using SQL Management tools and made the appropriate change to add db_owner permissions.

I could then re-enable the Publishing service.

The issue that I had was managing the menu’s at the top level of a Sharepoint site (site collection) and one of the sites within that collection.

The top level home page menu contained sites and then within the drop down option the subsites of those sites.

The issue was to hide a particular item from that drop down menu.

Editing the navigation options is the correct location. There are two ways to get to this

which leads to the Site Settings page where you select Navigation from the Look and Feel column

Alternatively just use the shortcut from the Site Actions ->Site Settings menu ->Modify Navigation

Once on this page there is a list of the navigation for the current site collection and you can hide or move items around.

The trick is with the option for Global Navigation

There are two options:

Display the same navigation items as the parent site
or
Display the navigation items below the current site.

The first option leaves the modification control only within the scope of the local site, while the second option adds the Global Navigation to the list for modification and allows for hiding or moving the global menu for this site.

I think, given my current limited Sharepoint knowledge, that this is due to the relationships within a site collection. The sites I am working with are within a single site collection. The top level menu takes up all the sites within it as the first menu level and sub-sites as the second level menu.  The options above are to either accept that the Global (site collection) Menu will display all the site/subsites or to have control passed to the site level and have the Global Navigation modified at site control level.