FeatureInfo... Failed SiteOrphan... Failed in SharePoint 2007 SP2 migration test

All Replies

• Thursday, August 26, 2010 11:47 AM

   

   
  

  1

  Sign In to Vote

  Go to the <12 Hive>\LOGS folder and check the log files.  The migration log file should tell you what about the sites and Features need to be cleaned up.  It's usually Features that you need to deactivate on the site collection before migration, that causes a problem.  These are almost always custom Features.  In addition, it seems you may have an orphaned site somewhere.  It needs to be identified and either restored or deleted.

   

  ---

  I trust that answers your question...
  
  Thanks
  C
  http://www.cjvandyk.com/blog
  • Reply
  • Quote

   
• Wednesday, September 01, 2010 5:54 AM

   

   
  

  0

  Sign In to Vote

  ok, how to remove the feature or site that i no longer need ?

  thanks man.

  ---

  /* Infrastructure Support Engineer */
  • Reply
  • Quote

   
• Thursday, September 02, 2010 8:20 AM

  Moderator

   

   
  

  1

  Sign In to Vote

  You can deactivate feature in those pages depending on the scope of your feature(http://weblogs.asp.net/soever/archive/2007/05/03/sharepoint-features-elements-scope-and-other-info.aspx):

  • Site Settings-> Site Features,
  • Site Settings->Site Collection Features
  • Central Administration->Operation->Manage Farm Feature
  • Central Administration->Application Management->Manage Web Application Feature

  You can retract solution in Central Administration->Operations->Solution Management. Please read this for more about solution management: http://blogs.technet.com/b/wbaer/archive/2007/03/29/building-solutions-for-microsoft-office-sharepoint-server-2007-windows-sharepoint-services-3-0.aspx

   

  • Reply
  • Quote

   
• Thursday, September 02, 2010 8:28 AM

  Moderator

   

   
  

  1

  Sign In to Vote

   FeatureInfo... Failed SiteOrphan... Failed
  

  Please read this for Orphans: http://blogs.technet.com/b/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx

  • Reply
  • Quote

   
• Thursday, September 02, 2010 2:21 PM

   

   
  

  0

  Sign In to Vote

  here's the update about what I've done so far:

  I tried to remove it manually using STSADM.exe
  C:\>stsadm -o uninstallfeature -id bc59afa4-5412-4148-8a23-1e7e6d122d7f
  Failed to find the XML file at location '12\Template\Features\BatchSiteManagerLinks\feature.xml'
  
  C:\>stsadm -o uninstallfeature -id 20e9ecab-2d22-41eb-892d-933afc32793e
  Feature with Id '20e9ecab-2d22-41eb-892d-933afc32793e' is not installed in this farm. The feature was not uninstalled.
  
  but still no joy. I've got more than one of the missing item, see below, does these items need / must be cleaned first before migrating ?
  
  

  
  Name = [Unknown], Feature id = [20e9ecab-2d22-41eb-892d-933afc32793e], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [07c1480f-43f8-4302-b218-9e53eee7c1c8], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [fd045e37-39d5-4f24-9e09-543a98b36674], Reference count = [5], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [89ab5aa0-28d1-4700-9db7-bb8a9c672131], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [873443d3-5355-45f9-ae47-9c4e40589d9e], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [e4d1f30d-faef-4939-97ae-c384bea71530], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [3716b2c8-022f-4e0d-a02b-5389b90b182b], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [1b8e70bb-534f-4934-8f3f-d432470022b3], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [50e31660-5eaa-4691-9f44-04552b127ad5], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [62f2dc87-f1a4-463f-bc21-2a82f3562598], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [ad072ddb-edc3-41b3-b1aa-bb44d7a8c6ea], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [81a0b6a1-3baf-4cd4-af2c-091e3b144809], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [619fa8e1-f97d-4eb8-b569-08586352ff0f], Reference count = [6], Scope = [Web], Status = [Missing]
  Name = [Unknown], Feature id = [b9a12829-19b1-4274-8c18-63d6cdd10378], Reference count = [6], Scope = [Web], Status = [Missing]

  ---

  /* Infrastructure Support Engineer */
  • Reply
  • Quote

   
• Thursday, September 02, 2010 2:22 PM

   

   
  

  0

  Sign In to Vote

  The only thing that i'm interested to know how to remove it is that the broken / old site collection below how to remove it from the database ?

  Failed : Orphaned site collections  
  An orphaned site collection is a site collection exists in the content database, but it is not in the configruation site map. 
  
  Such site collections is not accessible and will not be upgraded properly.The follow orphaned site collections where found:
  /sites/PMO(Data Source=MOSSDEV01\MOSSDB;Initial Catalog=MySite_ContentDB;Integrated Security=True;Enlist=False;Connect Timeout=15)

  ---

  /* Infrastructure Support Engineer */
  • Reply
  • Quote