SharePoint 2010 >> Taxonomy Picker.ascx Failed Error


On SharePoint 2010 you will run into the following error :

Log Name        :  Application
Source             :  Microsoft-SharePoint Products-SharePoint Foundation
Date                : 
Event ID          :  7043
Task Category  :  Web Controls
Level                :  Error
Keywords         :
User                 : 
Computer         : 
Description       : 

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


Here’s how it looks it in the Application logs






The file drive:\Program Files\Common Files\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\TaxonomyPicker.ascx is badly formed and  doesn’t compile.



You can change the bad syntax of the file as follows

  • Navigate to /14/ControlTemplates/TaxonomyPicker.ascx user control
  • Open the user control in a text editor and locate the first line
  • Find the character string , and replace with a comma ‘,’ (without quotes).
  • Save the user control.






Sometimes, the error does not go away even after following the steps listed above. In such cases, the fix is to rename the ‘TaxonomyPicker.ascx’ to  something like ‘TaxonomyPicker.ascx_broken‘ so that we do not try to recompile it each time the AppPool is started. The user control is never used  within SharePoint and therefore serves no real purpose.

Comments (3)

  1. Sol Alogaga @ Content and Code says:

    Actually this should be classified as an SharePoint RTM deployment error because the file should not be in SharePoint RTM because like you rightly said it is not used. I investigated why even when the fix is implemented the error still returns, I was able to establish by use of Reflector that the assembly dll Microsoft.SharePoint.Portal does not actually contain within it a class Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker. Probably because this was depreciated in RTM but used in RC and Beta.

    In my opinion the real fix is to rename the file as stated in the update section simply because you are calling a class that does not exist. As of posting this I do not know if a hotfix has been released to fix this.

  2. Ray Letts of Arbutus says:

    Hi guys followed the above but even renaming the file does not work. I then got two errors, one for each file. It appears to traverse all ASCX files in that directory. So have moved them to a 'bad' folder therein.


  3. Drew says:

    So NONE? of those files are needed? Does renaming "CONTROLTEMPLATES" directory work?