This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 48%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESH%3C/text%3E%3C/svg%3E)
Hi there,
I ran into a problem is my SharePoint_Config is missing. because I deleted it Inadvertently and no backup. As far as know, when the SharePoint_config does not exist in the database, if I perform the SharePoint configuration wizard we could choose, "disconnect from this server farm" then we could rebuild the server farm once again. currently my problem is I choose the "disconnect from this server farm" my WFE always tell me it cannot find SharePoint_Config DB or cannot login.
my environment,
Is it possible to handle this trouble??? any ideas??? ...
Thanks
Hi both,
I solve it out by using the following command:
Disconnect-SPConfigurationDatabase -Confirm:$true
Thanks for sharing. Glad to know that your problem is solved.
You can accept it as the Answer if you confirm it to be the solution.
It will help others who meet similar questions in this forum. Thank you for your understanding.
Hi @SHUO .H , I’m checking on how things are going on with this thread. Please remember to accept the Answer to this thread if you have it solved.
Thank you for your understanding.
You will need to build new SharePoint servers and create a new farm. You won't be able to disconnect the existing SharePoint servers or uninstall SharePoint Server as they cannot reach the Config db.
I cannot uninstall SharePoint???
Not while the server believes it is joined to the farm.
Thanks for your reply. I suppose there is a sql connection in the registry so that sharepoint think it is joined the farm. because I found out the other servers is joined the same configuration database, but it can be disconnected. I am not sure whether or not it can work well. but following the logic, if we remove the registry, it should work. I guess. Another thing is I remember when the configuration database was removed, sharepoint should be disconnected automatically when we use the configuration tool (PSConfig). no idea, maybe need to test it on 2019.
anyway, tmr i will give it a shot and post the result in here.
That wouldn't be a supported option for removal.
It is generally quicker to build a new VM...
The current farm is not possible to recover with the Configuration database deleted with no backup.
As Trevor suggests, you will have to start over and build a new farm instead.
If an Answer is helpful, please click "Accept Answer" and upvote it.
**Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. **
@ChelseaWu
so As mentioned from @Trevor Seward , I cannot Uninstall SharePoint???
I assume what Trevor means is that you cannot remove the SharePoint Servers from the farm and then rebuild, since you are not on a single-server farm.
Of course, you can just delete the SharePoint product via Control Panel > Uninstall a program, but that would not delete the whole farm for you.
See the reference here: Uninstall SharePoint Servers 2016 or 2019.
I try to uninstall the SharePoint 2019 but I ran into a problem. the message shows up "One or more required office components failed to complete successfully error during uninstallation of SharePoint 2019"
Please check out this post with the same error for troubleshooting: One or more required office components failed to complete successfully error during uninstallation of SharePoint 2016.
yup, I user the same way to uninstall SharePoint 2019. unfortunately, cannot work well. :(
It seems that the uninstallation program will need to access the configuration database anyway.
As Trevor suggests, consider building a new farm directly in a new VMAS instead.