Strausy's O365/SharePoint KB

Recently I needed to patch my SharePoint 2013 on-premises environment with the August 2019 Cumulative Update (CU). After the binaries were installed on my farm, I proceeded to run the SharePoint Products and Configuration Wizard (henceforth, Config Wizard) to complete the process. Inevitably, this is where most SharePoint patches fail, but it usually takes a long time to do so. But this time, the failure was almost immediately, specifically Step 2 out of 10. Symptoms and Error Messages The error message indicated  Exception: System.Data.SqlClient.SqlException (0x80131904): profile name is not valid .  and gives you the link to the error log as shown below. A review of the log didn't really provide any other details. After restarting the necessary SharePoint services, I was able to get back into Central Administration. I increased the logging level to Verbose to try and get more information about the error. Restarting Config Wizard and using a ULS Viewer  to catch the error

I was applying the August 2019 CU for SharePoint 2013 in my Test environment. After installing the binaries, I tried to go to Central Administration to view the Servers in Farm page to verify the status. Instead of loading the homepage, I got the error message Unknown server tag 'AdminControls:MigrationToolPromotionTip'. I was able to get to other pages within Central Admin by typing in the URL directly. After successfully completing the Products and Configuration Wizard (which you should do after every patch), Central Administration loaded successfully. I then noticed a new advertising banner touting their SharePoint Migration tool. Not a coincidence.

Issue: In a SharePoint Online site collection, any publishing features (and Wiki pages) will not allow you to create a new item. Pages, Site Pages, Reusable HTML and Reusable Text using the modern interface. Error: Either a blank page with the standard "500 Internal Server Error" or nothing at all in the Reusable Content libraries. Workarounds: 1) Use the Return to classic SharePoint to create these items. The errors will persist in the modern interface and you will need to manually switch each time the site is in the modern interface. 2) Change Document Library default open behavior setting. This will allow each library you set this way to behave normally. Advanced Settings > Open Documents in the Browser and set to "Open in the browser". 3) Disable the Open Documents in Client Applications by Default Site collection feature. This will prevent the issue completely. Root cause: Microsoft has confirmed a bug in a code release is causing