SharePoint Server 2016 updates
Build Number: 16.0.4393.1000
KB 3115181 – SharePoint Server CU (global*)
KB 3115184 – SharePoint Server CU (localized/language dependent*)
After installing the CU, we still need to run the SharePoint 2016 Products Configuration Wizard.
If you want to use the command line with psconfig.exe please read first “Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE”
Not sure which Build version actually is yet running? Try this: SharePoint Server 2016 Patch Build Numbers Powershell Module
* global means: fix will apply to all languages;
You need to install always both fixes even if no language packs are used, because the base product also comes with a language which needs the language dependent fix.
SharePoint related security fixes:
- What is the difference between a PU, a CU and a COD?
- SharePoint Server 2016 Patch Build Numbers Powershell Module
- SharePoint Server 2016 Zero-Downtime Patching Demystified
- April 2016 CU for SharePoint Server 2016
- May 2016 CU for SharePoint 2016
Other SharePoint Builds and version tables:
2 thoughts on “SharePoint 2016 June CU”
I have installed this and then ran the PSConfigUI, but SP is providing the SQL instance in quotes and it will not connect to SQL server because of that. Do you know how I can change the string to allow the removal of the quotes? SharePoint is running, so it can clearly connect but for whatever reason when I run PSConfigUI is gives the following error and I believe it’s because of those quotes.
Failed to initiate the upgrade sequence.
This is a critical task. You have to fix the failures before you can continue.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 – Connection string is not valid)
the PSConfig tool pulls the data out of the config DB so it looks like your SQL DB string is stored there with the “quotes” which might be the cause.
So you should raise this as a support ticket since no manual modifications to the databases are supported, hence you need support engineering to help you fixing this.