The Guide of a MOSSLover

Just had the same problem and tracked down the feature ID to the U2UCamlqueryBuilder.

Install the U2UCamlqueryBuilder, deactivate the U2U Feature and uninstall U2UCamlqueryBuilder again.

Try Pako Simeonov;s tool:
http://blog.myitechnology.com/2009/06/fixing-feature-guid-for-list-template.html

Hi


if you are using vsewss tool to deploy your solution this tool generates new feature ID for the instance feature and another ID for template feature list. In fact, while deploying your solution sometimes these two features are not synchronized (depending on the order of deployment) and the instance list will point to the feature that is already unistalled hence leading to the error seen on this blog the solution is to keep the template feature and replace the default instance feature of vsewss with feature receiver that generates the instances of the lists based on the provided templates as follows :


SPSite siteCollection = SPContext.Current.Site;
SPWeb mySite = SPContext.Current.Web;
SPListTemplateCollection listTemplates = siteCollection.GetCustomListTemplates(mySite);
SPListTemplate listTemplate = listTemplates["Custom List Template"];
mySite.Lists.Add("Custom List", "A list created from a custom list template in the list template catalog", listTemplate);

Cheers

Hi
Let’s understand what happened than the solution will be provided and it is simple one 
If you are using vsewss
{
Explanation:
When you uninstall your solution and you deploy new one vsewss generate new ID for your features. Since SharePoint works with IDs and has no semantic level to understand the features.
If you have a feature that is dependent on another feature. SharePoint will look for the dependent feature ID and will raise the error. The reality is that the feature is installed but has the old feature ID.
Solution:
1) Go to the concerned feature in the 12 or 14 hives, you must know which feature is concerned with that functionality.
2) Change the feature ID to the one raised in the error
3) stsadm -o installfeature -name <Feature> -force
Test:
Try to access the functionality it should work
}
//Note: this solution works when users are using vsewss