SharePoint 2010 Error TaxonomyPicker.ascx

I love having a Development Environment I can simply return to a known snapshotted point, but it seems so long between new set ups that you forget some of the gotcha’s that you fixed when you initially set it up. This is one of those really frustrating ones that seems to appear on a lot of servers in the wild and one I’d completely forgotten about until today when I had to fix it again.

I got the following critical error :-

Web Controls Critical 7043 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’.

The fix for this is simple, open the TaxonomyPicker.ascx control which is in the hive under ControlTemplates (the full path is usually C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES) and take a look at the top of this file:-

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

Highlighted in this snippet is the , which is the html encoding for a comma (,), by adding an actual comma and a space after it this issue is fixed, so this line should look as below:-

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

Thats it fixed, the error is gone, if only all critical errors that appeared were that easy to fix.

MOSS on Server 2003 SP2 with SQL 2000

It appears that SQL 2000, MOSS and Windows Server 2003 Service Pack 2 don’t play too nicely together. During the config the MOSS Shared Service provider there are Authentication issue’s in SQL. The good news is by dropping Windows Server 2003 Service Pack 1 appears to be tolerant in this configuration with a couple of caveats.

  1. Make all the MOSS Service Accounts Administrators on the SQL Box. These privileges should be able to pruned at a later date, but there does seem to be issues with the installation and configuration of MOSS.
  2. The MOSS configuration tool that is usually run from Start Menu will not complete the installation. To get around this run the tool from the command line using “psconfig.exe” located under the “%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin” folder.
  3. After running the MOSS Hotfixes following re-run the config tool after each upgrades completes, using the “psconfig.exe” command line tool. Again the Start Menu Option will not work. Here are the hotfixes :-
    • Windows SharePoint Services 3.0 hotfix package: May 8, 2007 – KB936867
    • SharePoint Server 2007 hotfix package for SharePoint Server 2007 and for SharePoint Server
      2007 for Search: May 8, 2007 – KB936877
    • SharePoint Server 2007 hotfix package: May 15, 2007 – KB937207

I’d be interested to work out what in SP2 actually stops SQL 2000 from working with MOSS, but then again I’m not in a rush to do another MOSS job with SQL 2000.