Solved

SharePoint 2007 to 2010 Upgrade - Orphaned Site Collection

Posted on 2012-04-02
5
414 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

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

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

In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

617 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