Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > SharePoint 2010 Forums > SharePoint 2010 - Setup, Upgrade, Administration and Operation > Delete orphaned lists from sharepoint site in MOSS

Answered Delete orphaned lists from sharepoint site in MOSS

    •  
      Wednesday, March 23, 2011 9:03 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Before migrating from SharePoint 2007 to 2010, I have ran the preupgradecheck from stsadm command. I received the failed message for Orphaned objects.

      When I run the databaserepair operation through stsadm, I received the below list.

      <OrphanedObjects Count="6">

        <Orphan Type="SPList" Id="{787A6375-ABA3-4475-AE64-230853EB4448}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

        <Orphan Type="SPList" Id="{AFB52A40-C6F7-47D3-A5A1-517E47256AC8}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

        <Orphan Type="SPList" Id="{8A28CCEF-6AEC-4B10-B00B-67CC063FC2E4}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

        <Orphan Type="SPList" Id="{5889326B-09E5-451A-B16E-71B9FE93E900}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

        <Orphan Type="SPList" Id="{1F90BB81-1955-460E-8F46-85655BEFB306}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

        <Orphan Type="SPList" Id="{242F47AD-29F2-4536-AD3D-B5D3C0308050}" SiteId="{13AB0F9E-386B-4128-916C-E70BFC6A45F3}" />

      </OrphanedObjects>

      I have ran the databaserepair with deletecorruption option, but still it is not deleted and showing the report as above, no matter how many times I run the databaserepair command.

      I tried from SQl Server side to write T-SQL and delete the references, but didn't success. Can someone help me where the reference or relation between list and site. I searched in all tables in the content database and didn't get any clue.

      Any help will be greatly appreciated.

       

      ASP.NET and SharePoint developer
      Company: http://www.rampgroup.com/
      Blog: http://praveenbattula.blogspot.com
       

    Answers

    • Wednesday, March 23, 2011 5:48 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Open this Site collection in share-point Designer and then check about the list if its their remove it. and their is another codeplex tool may be helpful

      http://splistinstancefix.codeplex.com/

      http://www.eggheadcafe.com/community/aspnet/69/10072761/list-does-not-exist-error-on-adding-links-webpart-to-master-page.aspx

      hope this help

      thanks

      -ws

      SharePoint administrator, MCTS,MCITP
       

    All Replies

    • Wednesday, March 23, 2011 5:48 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Open this Site collection in share-point Designer and then check about the list if its their remove it. and their is another codeplex tool may be helpful

      http://splistinstancefix.codeplex.com/

      http://www.eggheadcafe.com/community/aspnet/69/10072761/list-does-not-exist-error-on-adding-links-webpart-to-master-page.aspx

      hope this help

      thanks

      -ws

      SharePoint administrator, MCTS,MCITP
       
    • Friday, April 01, 2011 9:32 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi there,

      thanks for the reply. But, it didn't help me. The codeplex tool shows the list instances which has no template associated. But, in my case I have the lists in database which are not associated with any of the web or site.

      After spent 2 days, only on the SharePoint content database I found the solution. Now, with the query I have used I am able to find all the places/references of the lists or libraries in the whole site collection. I found 40 records which are linked to the web but which isn't there in the SharePoint when I browsed from browser. 

       

      Query used:

      select * from userdata where tp_ListId in ('787A6375-ABA3-4475-AE64-230853EB4448',

      'AFB52A40-C6F7-47D3-A5A1-517E47256AC8', '8A28CCEF-6AEC-4B10-B00B-67CC063FC2E4',

      '5889326B-09E5-451A-B16E-71B9FE93E900','1F90BB81-1955-460E-8F46-85655BEFB306',

      '242F47AD-29F2-4536-AD3D-B5D3C0308050')

      All the GUID's used in query are the list ids which I got from the databaserepair command of STSADM.

      Now, I am free of orphaned objects and ready to migrate to SharePoint 2010. Woo hoo..........

       

      ASP.NET and SharePoint developer
      Company: http://www.rampgroup.com/
      Blog: http://praveenbattula.blogspot.com
       
    • Thursday, August 04, 2011 8:23 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      With the select statement described above I also found over 80 records. But what I have to do now? e.g. the referencing tp_DirName doesn't exist any more because of an old object. So I only have the tp_GUIDs. How can I discover which object references to the orphaned object?

      Any help would be appreciated.

      cheers

      -ck


       
    • Monday, April 02, 2012 5:52 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      How did you remove them?