Hello All,
Been trying to upgrade my production farm but PSConfig keeps failing at the last part. See attached.
I’ve tried to start PSConfig via a elevated command prompt with all the flags (b2b -wait force, etc) but the last part always fails. I tried to even set a processor affinity as I read that could cause issues (worked on my dev farm but not in production). So I’ve been able to manually upgrade my content databases but the service app DBs are not upgraded. Any and all help would be appreciated!
So after banging my head on this for a while, I threw in the towel and called Microsoft. We found out that the WSS_Logging DB (since it was in a SQL AG) needed to be removed from the AG and then the PSConfig worked! After the upgrade I put the WSS_Logging DB back in the AG. I still had a weird issue with Search but had to turn back on all the Windows Services related to Search and Timer jobs and then a reboot. ALL DONE!
Could it be possible that you aren’t able to connect to the PSConfig database due to a security issue? Sometimes it’s something so simple it gets forgotten… just a suggestion.
Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=pgpf,DC=local doesn’t exist in the directory.
at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
