SharePoint 2007 to 2010 Upgrade - Orphaned Site Collection

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.
LVL 1
libertytaxAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Justin SmithSr. System EngineerCommented:
You could look at the objects table in the config database, and remove it from there.  This isn't supported by Microsoft though.
0
libertytaxAuthor Commented:
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
Justin SmithSr. System EngineerCommented:
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
libertytaxAuthor Commented:
We resolved the issue by emptying the recycle bin on all the web applications and rerunning the pre-upgrade checker.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
libertytaxAuthor Commented:
Average
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.