Geeks With Blogs

About Me:
I am a Female SharePoint Developer (a platinum unicorn). I have been working with SharePoint since I attended the Portal University in 2005. I hold a BA in Computer Science from the University of Missouri - Kansas City. I love playing Rockband, organizing user group meetings, working with code, attending events as a speaker or organizer, and having bizarre conversations about geek things with cool people. If you have any comments or questions fill out the contact form and I will try my best to help.

The Guide of a MOSSLover Becky Isserman's Blog
Today I was playing with the test environment re-installing all those 20 wsp templates from the Fantastic 40.  I notice that the "Content and Structure" area is not working on Production and Test.  This is what I am seeing: Feature 'df31abb1-d432-4fa5-bdb1-25a2a5dd7e86' for list template '7655' is not installed in this farm.  The operation could not be completed.
So I google around and look at the MSDN SharePoint Forums and some guy suggests to search the log files.  Well here is what I see in the log files:
Failed to determine the setup path of the list schema for feature {DF31ABB1-D432-4FA5-BDB1-25A2A5DD7E86}, list template 7655.
SMObjectList.Handle_RowDataBound: ObjectList 'ObjectList1' could not add ECB menu to row '14' because of 'Feature 'df31abb1-d432-4fa5-bdb1-25a2a5dd7e86' for list template '7655' is not installed in this farm.  The operation could not be completed.'

I googled most of these errors and found absolutely nothing of value so far.  I can't find the list anywhere.  I can't find the feature anywhere.  It is almost as if there is some type of residual left over from the death of this custom list or feature.  It looks like something happened on February 24th around 5:45 pm, because the log files with the entries start around that time.  I really have no idea what happened that day, because no one was really in the office and messing with Feature Files or List Templates as far as I can tell.  If anyone has an Proton Pack ready to get rid of the ghost I'm ready to send it away. Posted on Thursday, February 28, 2008 10:50 AM MOSS | Back to top

Comments on this post: Is there a Ghost in SharePoint?

# re: Is there a Ghost in SharePoint?
Requesting Gravatar...
Just had the same problem and tracked down the feature ID to the U2UCamlqueryBuilder.
Left by Kyle on Aug 13, 2008 11:21 PM

# re: Is there a Ghost in SharePoint?
Requesting Gravatar...
Install the U2UCamlqueryBuilder, deactivate the U2U Feature and uninstall U2UCamlqueryBuilder again.
Left by Alexey Varlamov on Sep 08, 2008 11:28 AM

# re: Is there a Ghost in SharePoint?
Requesting Gravatar...
Try Pako Simeonov;s tool:
Left by sptpkt on Jun 18, 2009 10:04 AM

# re: Is there a Ghost in SharePoint?
Requesting Gravatar...

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);

Left by Mohamed Hachem on Jul 08, 2010 10:19 AM

# re: Is there a Ghost in SharePoint?
Requesting Gravatar...
Let’s understand what happened than the solution will be provided and it is simple one 
If you are using vsewss
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.
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
Try to access the functionality it should work
//Note: this solution works when users are using vsewss
Left by Mohamed Hachem on Aug 30, 2010 2:22 PM

Your comment:
 (will show your gravatar)

Copyright © MOSSLover | Powered by: