As I received some feedback that I should also add the Urls to the KB articles of the different security fixes I added this information to my blog post.
SharePoint 2010 Suite:
SharePoint 2013 Suite:
- KB 4462215 – Excel Service 2013
- KB 4484122 – SharePoint Foundation 2013 (core component)
- KB 4475608 – SharePoint Server 2013 (core components)
SharePoint 2016 Suite:
- KB 4484111 – SharePoint Server 2016 (language independent)
SharePoint 2019 Suite:
- KB 4484110 – SharePoint Server 2019 (language independent)
Office Online Server:
- KB 4475595 – Office Online Server
See the Security Update Guide below for more details about the relevant fixes:
More information:
Permalink
Hello Stefan. Would not be added to SharePoint 2019 Suite also KB 4484109 (language dependent) reference?
Permalink
Hi Ladislav,
4484109 is not a security fix.
This article focues only on security fixes.
Complete CU info for SP2019 is in this blog post:
https://blog.stefan-gossner.com/2019/10/08/october-2019-cu-for-sharepoint-server-2019-is-available-for-download/
Cheers,
Stefan
Permalink
On mentioned page there is your wording “This is also a security update!”. On download page of this update there is info that this update provides the latest fixes to Microsoft SharePoint Server 2019 Language Pack, additionally, this update contains stability and performance improvements.”. No word about security. So what should be stated about this wssloc? For me, it is some confussion.
Permalink
Hi Ladislav, this was a copy&paste error. I removed the security fix info from the KB article but forgot to remove it from the download link.
Permalink
Sorry Stefan, I didn’t mean to be so meticulous and annoy you with wording, but I like accuracy, maybe too much.
Permalink
Hi Stefan, i’ve a problem with KB4484111. After installed this update, in the design manager page, when i click a master page to preview, it throws an error.
For two days, i’m struggling with this. Today i install a fresh sp 2016 without updates, this page works perfectly. But after the installing the update it gives error again. And cannot uninstall the update 🙂
http://sp/_layouts/15/previewwithstatus.aspx?Url=%2F%5Fcatalogs%2Fmasterpage%2Fseattle%2Ehtml
ULS Message
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest()
at Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
http://sp/_layouts/15/preview.aspx?OverrideMasterPageUrl=/_catalogs/masterpage/seattle.master&PagePreview=true
Permalink
Hi Hasan,
if you would like this investigated you need to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Permalink
I have the same issue as Hasan
Permalink
Hi Hasan,
a fix for this is in the works. Current plan is to release it with December CU.
Cheers,
Stefan
Permalink
Hi Stefan,
Thanks for the update. Is there any site you know of which lists known issues with updates reported by the community which we could check out ahead of installation?
Pete
Permalink
Hello everyone,
I am having the same problem with SP 2019, when I try to preview a master page on the Designer Manager page, I get the error below.
Were you able to find what was wrong?
We have installed the december update.
Server Error in ‘/’ Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest() +174
Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e) +339
System.Web.UI.Control.OnLoad(EventArgs e) +85
System.Web.UI.Control.LoadRecursive() +128
System.Web.UI.Control.LoadRecursive() +225
System.Web.UI.Control.LoadRecursive() +225
System.Web.UI.Control.LoadRecursive() +225
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3711
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3190.0
Permalink
Hi Carla,
it is impossible that you installed December CU because this CU is planned to be released next week.
It should include the fix.
Cheers,
Stefan
Permalink
Oh, ok, sorry! That’s what I was told by my team 😉
Thank you very much!