Feature not Installed in the Farm error

すべての返信

• 2009年8月5日 13:54

   

   
  

  0
  Hiii,
  
  could you please show you feature file to forum? so it may be helpful to give answers to you!!
  
  Regards,

  ---

  N i T i N
  • 返信
  • 引用

   
• 2009年8月5日 14:26

  モデレータ

   

   
  

  0
  These are both Project Server locations.
  
  Project Server questions are not supported here.
  
  See this MS post
  
  
  http://social.technet.microsoft.com/Forums/en-US/projectserver/thread/b333d85f-f43c-4815-9c30-b161615794e0
  
  Moving to Off-topic.

  ---

  WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
  Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
  • 返信
  • 引用

   
• 2010年2月12日 18:15

   

   
  

  0
  The issue he's having is the same issue I'm having, which is an issue with SHAREPOINT. Project Server was installed on this SharePoint farm but isn't any longer. Now SHAREPOINT is broken, not Project Server. Please move this thread back to the proper thread where it has a snowball's chance of being answered.
  • 返信
  • 引用

   
• 2010年2月25日 16:42

   

   
  

  0
  Hemanth / Brian,
  
  The site / subsite you are trying to reach was created with an invalid (one of the default MS Project Server) templates.
  
  The only way out of this is to create a new site / subsite and copy all content from the old location.
  
  -Okan Safi
  • 返信
  • 引用

   
• 2010年2月26日 9:47

  モデレータ

   

   
  

  0
  > The site / subsite you are trying to reach was created with an invalid (one of the default MS Project Server) templates. 

  
  

  "one of the default MS Project Server" templates"

  
  

  makes this is Project Server question as I saw from the references in the first post to PWSDOCLIBS and PWSCommitments 

  
  

  
  

  Also even you Mr Finch say that Project Server was installed on your farm. (Yes I know was *earlier* installed but clearly remnants are left)

  
  

  
  

  Abusing (mildly) the Moderator for moving a post on a different subject to those covered in the forums may get your name noticed but that isn't always a positive thing.

  ---

  FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
  Complete Book Lists (incl. foreign language) on each site.
  • 返信
  • 引用

   
• 2010年3月31日 3:07

   

   
  

  0

  Sorry about the tone of my post in February. Looking back a month later, it's clear I was lashing out in frustration after banging my head against the problem for too long.

  My innapropriate outbursts aside (Again, sorry, I'm usually more polite), this page is still the top hit in Google and Bing for "Feature 'd8d8df90-7b1f-49c1-b170-6f46a94f8c3c' for list template '1104'"  Wouldn't it serve the community better for a solution to be here? (Or maybe me and Hemanth are the only two unlucky folks to have this problem?)

  I found my way back here after migrating my content databases into another farm to fix it. 1 month later I'm running into this error again while trying to use the permission reporting feature from the SharePoint toolkit.

  Would it help if I rephrased the question in a non Project Server specific way?

  How do I remove stale feature references from my content databases? Or what tools should I use to track down the list template in this Publishing portal that's referencing this old feature?

  • 返信
  • 引用

   
• 2010年3月31日 14:12

   

   
  

  0
  My new problem turned out to be caused by the WSS 3.0 ProjectTrackingWorkspace application template. I installed that template in the new farm and things work fine now.  Maybe some bad interaction between Project server and this template in the old farm? If I had the old farm up and running, I'd check this out, but my guess is that If you have this template and Project server in the same farm, and then uninstall project server it's going to break sites that use the ProjectTrackingWorkspace template. A possible fix could be redeploying the ProjectTrackingWorkspace application template.

  • 回答としてマーク Mike Walsh FINModerator 2010年7月9日 4:35
  •  
  • 返信
  • 引用

   
• 2010年7月8日 14:04

   

   
  

  0

  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

  ---

  Mohamed Hachem
  • 返信
  • 引用

   
• 2011年2月2日 5:18

   

   
  

  0

  Just to hopefully add some clarity here, the Project Tracking Workspace, or projecttrackingworkspace.wsp is NOT associated exclusively with Project Server. It was bundled as one of the FAB 40 application templates and will definitely cause you some heartache if you have sites based on this template when upgrading to 2010, regardless of whether you ever used Project Server or not.

  For instance, say you never installed Project Server, but used the Project Tracking workspace, and are attemping to do a database attach/upgrade of a SharePoint 2007 content database that has sites based on the FAB 40 projecttrackingworkspace.wsp. You might bring this site up in 2010 and not be able to access any of the sites. You might reset to site definition and delete some web parts off the main page of the site by appending ?contents=1 to the path to the site. Even so, you might still see errors in the sp log and windows event log that say:

  Feature '525dc00c-0745-47c0-8073-221c2ec22f0f' for list template '101' is not installed in this farm.  The operation could not be completed.

  And this feature id might be found in the .xml files of some pws folders in the 12Hive\templates\features folder, leading you to believe it was related to the project tracking workspace site.

  If all that were, true, you'd be right. And all of this having nothing to do with Project Server...

  • 返信
  • 引用

   
• 2012年5月3日 18:38

   

   
  

  0

  I'm running into a similar problem after recently upgrading from MOSS 2007 to Sharepoint 2010.  So far, a lot of the OOTB features such as bulk check-in, browsing for more links to add to navigation, etc produce correlation ID errors.  I removed all 18 faulty features in the farm using the feature admin tool on codeplex as well as installing the december CUs and still get an error for a missing feature.  I tried searching for the feature using get-spfeature -id "feature GUID" and it didn't find anything.  Here's what I found in the ULS logs:

  System.ArgumentException: Feature '69828593-5a05-4d29-bfc6-bc55c2739067' for list template '10100' is not installed in this farm.  The operation could not be completed.  
   at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass19.<GetFeatureRootAndListSchemaPaths>b__18()   
   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)   
   at Microsoft.SharePoint.SPFeatureManager.GetFeatureRootAndListSchemaPaths(Byte[]& userToken, Guid& tranLockerId, Int32 nZone, Guid databaseid, Guid siteid, Guid webid, Guid featid, Int32 ltid, String& sPathToFeatureRoot, String& sPathToSchemaXml)   
   at Microsoft.SharePoint.Library.SPRequestInternalClass.GetViewsSchemaXml(String bstrUrl, String bstrListName, Boolean bFullBlown, Boolean bNeedInitAllViews, ISP2DSafeArrayWriter p2DWriter, Int32& plDefaultViewIndex, Int32& plMobileDefaultViewIndex)   
   at Microsoft.SharePoint.Library.SPRequest.GetViewsSchemaXml(String bstrUrl, String bstrListName, Boolean bFullBlown, Boolean bNeedInitAllViews, ISP2DSafeArrayWriter p2DWriter, Int32& plDefaultViewIndex, Int32& plMobileDefaultViewIndex)   
   at Microsoft.SharePoint.SPViewCollection.EnsureViewSchema(Boolean fullBlownSchema, Boolean bNeedInitallViews)   
   at Microsoft.SharePoint.SPList.get_Views()   
   at Microsoft.SharePoint.Publishing.CachedList.GetMetadataNavSettingsXmlNoCache(SPList sourceList)   
   at Microsoft.Office.DocumentManagement.MetadataNavigation.MetadataNavigationSettings.GetMetadataNavSettingsXmlNoCache(SPList sourceList)   
   at Microsoft.Office.DocumentManagement.MetadataNavigation.MetadataNavigationSettings.GetMetadataNavSettingsXml(SPWeb web, Guid sourceListId, Boolean& listExists)   
   at Microsoft.Office.DocumentManagement.MetadataNavigation.MetadataNavigationSettings.GetMetadataNavigationSettings(SPWeb web, Guid sourceListId, Boolean checkWebPropHint)   
   at Microsoft.Office.DocumentManagement.MetadataNavigation.MetadataNavigationContext.GetMetadataNavigationHintsForList(SPWeb web, Guid listGuid)   
   at Microsoft.Office.DocumentManagement.MetadataNavigation.MetadataHierarchyNodeSiteObject.get_HasChildren()   
   at System.Web.UI.WebControls.TreeView.DataBindRecursive(TreeNode node, IHierarchicalEnumerable enumerable, Boolean ignorePopulateOnDemand)   
   at System.Web.UI.WebControls.TreeView.PerformDataBinding()   
   at Microsoft.SharePoint.WebControls.SPTreeView.PerformDataBinding()   
   at System.Web.UI.WebControls.HierarchicalDataBoundControl.PerformSelect()   
   at System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound()   
   at System.Web.UI.WebControls.BaseDataBoundControl.OnPreRender(EventArgs e)   
   at System.Web.UI.WebControls.TreeView.OnPreRender(EventArgs e)   
   at Microsoft.SharePoint.WebControls.SPTreeView.OnPreRender(EventArgs e)   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Control.PreRenderRecursiveInternal()   
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  • 返信
  • 引用