Jamik

Problem:
Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources...

Fix:
stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\ACCOUNT -url http://URL

The Superuseraccount should have “Full Control” permission but should not operate as system user.
Corresponding permissions should be set as “User Policy” of the Web application.

Update:

Due popular demand here are the steps you have to complete to get rid off these warning message(s):

1. Create two service accounts
   1. a superreader account
   2. a superuser account
      Both serviceaccounts should not be member of your webapplication(s) nor should be application pool accounts or farm admins. Two simple serviceaccounts with no rights will do the job.
2. Go to “Manage Webapplications” and select the desired web application
3. Create two user policies
   1. Add the superuser service account and grant him “Full Control” permissions
   2. Add the superreader service account and grant him “Full Read” permissions
4. Set the superuser and superreaderaccount either by stsadm or powershell
   1. stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue DOMAIN\ACCOUNT -url http://URL
   2. stsadm -o setproperty -propertyname portalsuperreaderaccount -propertyvalue DOMAIN\ACCOUNT -url http://URL

Note: If you are using claims authentication use the claims naming format instead of the DOMAIN\ACCOUNT format. Otherwise your webapp may become inaccessible.

Problem:
Numerous errors in the event log of a SharePoint 2010 server with the following error event descriptions:

Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.

and

Load control template file /_controltemplates/ScenarioNavigation.ascx failed: The 'wssuc:ButtonSection' tag has already been registered.

Fix 1:
Locate the file “TaxonomyPicker.ascx” in the Controltemplates directory of the 14 Hive, search for the following line

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker&#44;Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

and replace ‘,’ with ‘,’.

The correct line should look like

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Fix 2:
Locate the file “ScenarioNavigation.ascx” in the Controltemplates directory of the 14 Hive, search for a duplicate line of

<%@ Register TagPrefix="wssuc" TagName="ButtonSection" Src="/_controltemplates/ButtonSection.ascx" %>

and delete the second one.

Update:

The second problem seems to be fixed in the RTM version. The “TaxonomyPicker.ascx”-Problem still persists.

Update2:

Fix 1 (“TaxonomyPicker.ascx”) doesn’t apply to the RTM Version anymore as the “TaxonomyPicker” Class seems to be obsolete.
If you want to fix this error simply rename the “TaxonomyPicker.ascx” to something like “TaxonomyPicker.ascxBACKUP” to prevent recompilation by the CLI and the error is gone.