Solved

SharePoint 2007 to 2010 Upgrade - Orphaned Site Collection

Posted on 2012-04-02
5
410 Views
Last Modified: 2012-06-27
The pre-upgrade check discovered one orphaned site collection that I cannot resolve…

/personal/site_name (Data Source=PR-DB-004;Initial Catalog=MySite_Content;Integrated Security=True;Enlist=False;Connect Timeout=45)

We have successfully deleted the SiteID using the stsadm -o deletesite method making the enumallwebs report clean without any InSiteMap="False” records.  The pre-upgrade check still has the orphaned site collection so we executed the databaserepair command but the results are zero orphaned records.  The only discrepancy that I can find is the pre-upgrade check message references one content database “MySite_Content” and central admin site collection list references another content “MySiteContent”.

Any ideas?

Thanks in advance.
0
Comment
Question by:libertytax
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 37797388
You could look at the objects table in the config database, and remove it from there.  This isn't supported by Microsoft though.
0
 
LVL 1

Author Comment

by:libertytax
ID: 37798026
I queried the object table in the Config database and the only reference to the site was a valid reference.  Used the below query…

SELECT [Id]
      ,[ClassId]
      ,[ParentId]
      ,[Name]
      ,[Status]
      ,[Version]
      ,[Properties]
  FROM [SharePointSites_Config].[dbo].[Objects] (NOLOCK)
  WHERE [Name] LIKE '%/personal/<site_name>%'
      OR [Properties] LIKE '%/personal/<site_name>%'

I still do not understand why the site collection list would display a different content database then the pre-check upgrade message.   Both the content databases are valid and tied to the web application.

Any other thoughts?

Thanks again.
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 37798876
I would look for an object in the config db with the name of the bogus content db.

Either way, this won't stop your upgrade.
0
 
LVL 1

Accepted Solution

by:
libertytax earned 0 total points
ID: 37807453
We resolved the issue by emptying the recycle bin on all the web applications and rerunning the pre-upgrade checker.
0
 
LVL 1

Author Closing Comment

by:libertytax
ID: 37822738
Average
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Sharepoint Max date with criteria 2 108
Masterpage unexpected error 7 40
sharepoint list help 2 44
REST call Failing 1 7
Work Over Net is a new and very powerful collaboration product. With its new easy interface it is becoming very competitive to other similar products like webex and office interactive. WON 2010 have the standard business tools needed for multi-offic…
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administr…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question