Jamik

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.

If you like to use the taxonomy feature in SharePoint 2010 and try to create a Managed Metadata Column in a list or document library you may encounter the problem that this feature is not enabled by default:

At this time (Beta2 & RC) you have to activate this feature using PowerShell:

List all Features with the name *Tax*:

PS C:\> Get-SPFeature | where {$_.displayname -like "*tax*"}
 
DisplayName                    Id                                       Scope
-----------                    --                                       -----
TaxonomyFeatureStapler         415780bf-f710-4e2c-b7b0-b463c7992ef0     Farm
TaxonomyTimerJobs              48ac883d-e32e-4fd6-8499-3408add91b53     WebApplication
TaxonomyFieldAdded             73ef14b1-13a9-416b-a9b5-ececa2b0604c     Site
TaxonomyTenantAdmin            7d12c4c3-2321-42e8-8fb6-5295a849ed08     Web
TaxonomyTenantAdminStapler     8fb893d6-93ee-4763-a046-54f9e640368d     Farm

Activate “TaxonomyFieldAdded”

PS C:\> Enable-SPFeature -Identity 73ef14b1-13a9-416b-a9b5-ececa2b0604c -url http://betaplace

List all registered SharePoint application pools:

Get-SPIisWebServiceApplicationPool

Delete a specific Application Pool:

Remove-SPIisWebServiceApplicationPool -Identity "NAME"

UPDATE:
The release version has slightly different names for the cmdlets.

List all registered SharePoint application pools:

Get-SPServiceApplicationPool

Delete a specific Application Pool:

Remove-SPServiceApplicationPool -Identity "NAME"

 
For a full list take a look at MSDN.

Problem:
If you try to load a MOSS/WSS page you get the javascript error

Error in loading dll
Line: 1935
Char: 4
Error: Error in loading DLL
Code:0

The exact line and character numbers can diver.

Description:
This error has to do with the presence integration in MOSS/WSS.

Fix:
Try a repair installation of your MS Office.

Problem:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1} to the user DOMAIN\USERNAME SID (S-1-5-21-2949504220-1727672479-3499560203-1007).
This security permission can be modified using the Component Services administrative tool.

Fix:
Open COM administration and grant launch and activation permissions at the OSearch component to the specific service account.

SQL Server Log Entry:
Login failed for user 'NT-AUTHORTIY\SYSTEM'. [CLIENT: ]
Error: 18456, Severity: 14, State: 16.

Event Log Entry:
Event ID: 18456
Login failed for user 'NT-AUTHORTIY\SYSTEM'. [CLIENT: ]

Fix:
Open SQL Management Studio, locate the SQL Agent Jobs & deactivate/delete the corresponding “Shared_ServicesXXX_DB_Job_DeleteExpiredSessions“.

Problem:
The application-specific permission settings do not grant Local Activation permission for
the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}  to the user
DOMAIN\USERNAME SID (S-1-5-21-2949504220-1727672479-3499560203-1007).
This security permission can be modified using the Component Services administrative tool.

Fix:
Open you COM administration and grant launch and activation permissions at the IIS WAMREG admin Service component to the specific service account.

Problem:
If you’re using the “Tools and Tasks” Webpart on your Sharepoint Portal you may experience the error, that you can’t launch the url which is associated with an Taks-Entry. Instead IE shows you the error message ‘Object not found’.

Description:
The reason for this error is the corresponding ‘Javscript’ include file ‘Portal.js’ which contains the function ‘PopulateCallBackMenuItems’ and is not properly linked. This mostly occurs if the user has no rights on personal features.

FIX:
Activate Personal Features for the user (group).

“O3Spaces technology enhances OpenOffice.org and StarOffice with an integrated solution for Collaboration, Document Management and Document Retention within teams and small businesses. O3Spaces provides the OpenOffice 2.0 and StarOffice user community with a professional out-of-the-box extension for team and project collaboration, O3Spaces means an affordable and integrated alternative for MS Office Sharepoint“.

Definitely worth a try.

Problem:
If you’re trying to delete a masterpage from your Master Page and Page Layout Gallery, either with SPD or within the Settings Page you receive the following error:

"This item cannot be deleted because it is still referenced by other pages / Diese Seite kann nicht gelöscht werden da sie noch verwendet wird."

Fix 1:

• KB926812

Fix 2:

1. Create a subfolder with SPD.
2. Move the master page to the subfolder
3. Delete subfolder

Related:

• Finding all references where a master page, page layout, or other file is used in a MOSS 2007 Publishing (WCM) site
• KB926812
• Error when trying to delete a page layout in MOSS: This item cannot be deleted because it is still referenced by other pages