There are too many front-end applications with efficient, continuous database support, except SharePoint 2013, since the SQL Server always on mode has been available. From the initial unsupported, to the upgrade to SharePoint Server after SP1 support,
Many organizations like to choose this highly available group mode to escort SharePoint data. However, in the long-term use process, will inevitably encounter some problems, especially after upgrading the Service patch, rerun the SharePoint Configuration Wizard when the end of the (step 8 or Step 9 of 10), there will be an error.
But fortunately this error is very clear, it is clear that they have seen after the always-on mode caused by the.
650) this.width=650; "height=" 324 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8D/5D/wKiom1iZaoWR1IREAAJqDZ_9VIg381.png" border= "0"/>
So what do we do next? Do I need to remove this SQL AG availability group?
In fact, just need to be the error of the database from the AG to remove the.
First find the primary database of SQL Server always on high availability group, and then find this replicated database in the AG availability group.
Then remove it from the high-availability group.
650) this.width=650; "height=" 425 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8D/5D/wKiom1iZaoaQItslAAG40n3E6oI157.png" border= "0"/>
Then run the SharePoint Configuration Wizard, and the entire process runs correctly.
This article is from the "June Ma Run Space" blog, be sure to keep this source http://horse87.blog.51cto.com/2633686/1895631
SQL Server always on mode causes SharePoint configuration to be wrong