Fix Orphan D


Sometimes back, I headed up with an issue while I was trying  to attach one content database in the new environment. There was one site collection containing the managed path and the restore operation was throwing the following error:
“The attach operation cannot continue because another object in this farm already contains the same ID. Each object in a farm must have a unique ID. In order to proceed with the attach operation you must assign a new ID to this database. To attach this database with a new ID, use the Mount-SPContentDatabase command with the -AssignNewDatabaseId parameter. Note that if this new database and an existing database contain the same site collections, attaching this database will likely result in orphaned site collections due to conflicts between the two databases.”

My guess was to make sure no existing similar url be presence in the new environment where I’m going to restore the operation. So, I did clean up the manage path, and even check other site collection url. However, the error persists. Moved forward to take care of the orphan records there and ran the step1. It displayed me what we had inside there.
Step1
                  $OrphanDB = Get-SPDatabase | Where {$_.Name -eq "SP_xxxxxxxxx_Test"}
                  Write $OrphanDB
                 
                  Id               : ec73eabf-d801-432b-9ab6-390883217b6a
                  Name             : SP_xxxxxxxxx_Test
                  WebApplication   : SPWebApplication Name=Sharexxxx-Test
                  Server           : Testspsql_sys
                  CurrentSiteCount : 1
                 
Next step was to dismount this content database. Executed the step2 and confirmed ‘Y’ in the PowerShell window.
                  Step2
                  Get-SPContentDatabase -Identity ' SP_xxxxxxxxx_Test ' | Dismount-SPContentDatabase




At step3, removed the content database to ensure no presence of it on the environment DB where it is going to be restore again.
                  Step3
                  $pcmsdb = Get-SPContentDatabase -ConnectAsUnattachedDatabase -DatabaseServer "Testsp_sys" -DatabaseName SP_xxxxxxxxx_Test
                  Remove-SPContentDatabase -Identity $pcmsdb -force


Now, while executed the attached the content database again, it worked. Sometimes it is necessary to go a step back and clean up your mess (because we do repeatedly the same process on weekly/bi weekly manner) before process to next level.
Hopes it may help you!

Comments

Post a Comment

Popular posts from this blog

SharePoint Framework Reference Guide

SPFx stands for SharePoint Framework -  https://learn.microsoft.com/en-us/javascript/api/overview/sharepoint?view=sp-typescript-latest   Below are the packages of SPFx and we are using them while using SPFx framework for development in our day-to-day activities. .'@microsoft/decorators' - https://learn.microsoft.com/en-us/javascript/api/decorators?view=sp-typescript-latest '@microsoft/sp-core-library' - https://learn.microsoft.com/en-us/javascript/api/sp-core-library?view=sp-typescript-latest '@microsoft/sp-component-base package' - https://learn.microsoft.com/en-us/javascript/api/sp-component-base?view=sp-typescript-latest '@microsoft/sp-application-base package' - https://learn.microsoft.com/en-us/javascript/api/sp-application-base?view=sp-typescript-latest '@microsoft/sp-dynamic-data package' - https://learn.microsoft.com/en-us/javascript/api/sp-dynamic-data?view=sp-typescript-latest '@microsoft/sp-extension-base package' - http...
Read more

How to fix Azure DevOps error MSB4126

Image
Setting up build and release pipeline always tedious and we face many build related issues. Here is one common error I face couple of times while setting app Web or windows apps in Azure DevOps After placing the code in repos, and creating the build pipeline and run it, you can face the following error ##[error]D:\a\8\s\<your solution file>.sln.metaproj(0,0): Error MSB4126: The specified solution configuration "release|$(BuildPlatform)" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. To understand what is target platform defined in your project you need to visit or open the solution(.sln) file and review the following sections. In my case, this has been defined as x86 as target platform.         ...
Read more

SharePoint Admin Center

Image
 SharePoint Admin Center allows you to view your organization's SharePoint site including communication sites, channel sites, and sites that belong to Microsoft 365 group. This is same like Site Admin in earlier days of SharePoint versions. You can search organizational site, sort them or filter sites the way you want. Easy way to find and apply/change site settings. Under Policies, click on Sharing - This will allow you to create rules/ set control sharing at the organization level in SharePoint and OneDrive Here, in this page, you can apply settings to restrict how users are allowed to access content in SharePoint and OneDrive. Term store, the word getting populated from SharePoint 2010. You can feed metadata of metadata information of your organization level, program level, project level in Term store. helps your organization's knowledge better.  AI soon will play a vital role here and using AI, you can acyually find collect and process and finally yoour organization's d...
Read more