SPA Load Control Templates Failed

Update

This problem is related to your code, if you check your ascx files you have not correctly called the registration of these controls

 http://msdn.microsoft.com/en-us/library/bb964680.aspx

Please advise when you have updated your build

When I look at your control template files (ascx) that are install @ /12/Template/ControlTemplates. I dont see your register the path correctly. All the MS files use the toke "~" all your files point to "/controltemplates/"

As per guidelines

Inside the TEMPLATE directory resides a nested directory named CONTROLTEMPLATES. This directory contains many different user controls that are deployed as part of the standard Windows SharePoint Services installation.

The CONTROLTEMPLATES directory is also a place where you should deploy custom user control files. However, it's a good practice to create your own nested directory inside the CONTROLTEMPLATES directory to avoid potential file name conflicts. The CustomSitePages project creates a company-specific inner directory named Litware and copies its user controls into that directory. Each custom user control is copied to a physical path that looks like the following.

TEMPLATES/CONTROLTEMPLATES/Litware/UserControl1.ascx

Each Web application is configured with a virtual directory named _controltemplates that points to the physical CONTROLTEMPLATES directory. This makes it possible to reference any user control file by using a standard path relative to the hosting Web application. For example, one of the user controls from the CustomSitePages project can be referenced by using a virtual path that looks like the following.

~/_controltemplates/Litware/UserControl1.ascx

When deploying user controls, it's important to remember that they follow the same rules with respect to safe mode processing. If you want to place a user control on a site page that might be customized, the .ascx file must be registered as a safe control in the web.config file of the hosting Web application. Fortunately, you don’t have to worry about this if you deploy your custom user controls inside the virtual _controltemplates directory because the standard web.config file for a Web application already contains the following SafeControl entry.

Xml

Copy Code

<SafeControl  
  Src="~/_controltemplates/*"  
  IncludeSubFolders="True"  
  Safe="True"  
  AllowRemoteDesigner="True"  
/>

Now that you have seen how to create and properly deploy a user control, the final step is constructing a page template that references the .ascx file and creates an instance. Similar to constructing pages with custom controls, this is accomplished by placing a @ Register directive on the page template. However, the process is different with user controls because the @ Register directive requires an src attribute that points to the virtual path of the target .ascx file.

Xml

Copy Code

<%@ Page MasterPageFile="~masterurl/default.master"   
    meta:progid="SharePoint.WebPartPage.Document"  %> 

<%@ Register TagPrefix="luc" TagName="UserControl1"    
    src="~/_controltemplates/Litware/UserControl1.ascx" %> 

<asp:Content runat="server" ContentPlaceHolderID="PlaceHolderMain"> 
  <luc:UserControl1 ID="id1" runat="server" />   

</asp:Content>

You have now seen all of the steps involved with constructing site pages using custom controls and user controls. This provides you with a strategy to create components that are reusable and versionable, and also provides you with a technique for adding whatever custom code you want to pages that are running in safe mode.

Note that all techniques shown here for constructing pages with custom controls and user controls can be used within custom application pages in the same fashion as they are in site pages. The one major difference is that application pages do not support user customization and never run in safe mode. If you want to create a custom control or user control that is used only on application pages, you do not need to worry about registering controls as safe controls in the web.config file. 

you will need to setup a SSP and crawl using the Search Settings. We get this error everyday and get paged about it..

BTW I am using a custom masterpage, could that be it? Am I missing any register tags?

No, adding a registration tag will probably not correct this issue, but by all means give it a try if you like. This issue is related to a resource file (.resx) that can't be resolved. Here is my best guess on what is occurring and a possible solutions. The controls generating the error reside in the _controltemplates directory. This is a virtual directory that is accessible to each web application in your farm. However, when ExCM is deployed it is typically targeted toward a selected Web Application and not deployed to the entire farm. This includes the del.resx and del.en-US.resx files which contain the resource keys.

I'm guessing your content crawling service is trying to index these files on a web application in which ExCM is not deployed. When the control is accessed the resource files don't exist and you receive an error message. To correct this issue you may try one of the following methods.

1. Copy the del.resx and del.en-US.resx file to the App_GlobalResource directory of each web application. Note: older ExCM version only include the del.resx file. If the del.en-US.resx file does not exists, copy the del.resx file and rename it to del.en-US.resx.
2. Add a rule to your content crawling service so files in the _controltemplates directory are not crawled. You could take this a step further and only add an exception for the files having issues.

Please keep up posted on your progress.