If you want to save a site collection as a site template you can go to site settings and select "Save site as template" from the Site Actions section.  However, if you go to site settings from a subsite, the option doesn't exist.  Is all hope lost?!  Not at all!  Just append "/_layouts/savetmpl.aspx" to the site URL.  So, if you want to create a site template from http://myportal/mysubsite, enter http://myportal/mysubsite/_layouts/savetmpl.aspx into your browser's address bar and you'll get the site export page.


A recent SharePoint 2007 to 2010 migration went well, but not without it's expected little problems. One interesting problem that I ran into today had to deal with SharePoint Server Publishing. A site collection had the feature enabled and I wanted to disable it. So, Site Settings -> Site Features -> SharePoint Server Publishing -> Deactivate. Simple enough, but rather than deactivating the feature, I was presented with the following error message:

“One or more field types are not installed properly. Go to the list settings page to delete these fields.”

Well, sweet.  To resolve this issue:

IMPORTANT: You have to navigate to the "Relationships List" in a browser because it will not show up in "all site content" or SharePoint Designer!

I was then able to deactivate the site level SharePoint Server Publishing feature.

Perusing your event logs, you notice the following SharePoint Foundation error message:

Log Name: Application
Source: SharePoint Foundation
Event ID: 3760
Level: Critical
User: Shared Services Account
Task Category: Database

SQL Database <some_content_database> on SQL Server instance <SQL_Server> not found.  Additional error information from SQL Server is included below.  Cannot open database <some_content_database> requested by the login.  The login failed.  Login failed for user <domain\shared_services_account>.

This error occurs because the Office Web Applications and Access, Excel, Visio and PerformancePoint Service Applications require access to the content database(s) and do not have it.  When using PowerShell to deploy a farm, content database access is granted to the account running the commands/script and the service account tied to the web application.  This also appears to be the case when performing a database attach using content databases from a different portal such as a 2007 -> 2010 migration.

The fix is straightforward, although finding it was painful!  Open the SharePoint 2010 Management Shell and issue the following commands:

$wa = Get-SPWebApplication
foreach ($web in $wa) {$web.GrantAccessToProcessIdentity("DOMAIN\shared_services_account")}


Copyright 2011 - 2021 The Lazy SharePoint Admin | All Rights Reserved
menu-circlecross-circle linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram