Hi all,
I have a client who has upgraded their SharePoint farm from 2007 to 2010 and then from 2010 to 2013. The upgrade to 2010 was successful but the upgrade to 2013 has recorded to failures in the upgrade history but the 2013 functionality is available to users!
The content database contains three site collections although only one is visible via the UI or Powershell. After searching for a solution, the client dettached and reattached the content database.
Following the reattach, the content that is visible in the farm has reverted to one of the other site collections, rather than the one that was previously in use.
Does anyone know of a way to remove the site collections from the failed upgrades?
@Jaspit – The detach/reattach process failed to remove the orphaned site collections and actually changed the active site collection to one that has not been used for several months (the client ran the upgrades six months ago)
As a result the VMs that the farm is on were reverted back to a snapshot taken prior to the detach/reattach process being carried out.
Try detaching the DB in 2010 and re-attaching there – this should clear orphaned sites and then bring the DB over to 2013.
@Thuan – I have tried with get-spsite and it returns a single site collection not the three that are evident in the database.
As for Get-SPDeletedSite, that returns no site collections that are flagged as deleted and I did try crudely updating the deleted site flag in the DB but that also failed to return the site as deleted.
Try with Get-SPSite first and then Get-SPDeletedSite (this is to see if there is any sites that still reside in the content database)
