Hi Stefan and Henning.
This is correct. I have been reading that the workflows issue was mentioned until Feb 19 Patch.
https://www.toddklindt.com/blog/Regressions/sp2013February2019.aspx
https://www.toddklindt.com/blog/Regressions/sp2013January2019.aspx
https://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=784
I have suffered the pain in September and October and am still skeptical. However, I do not see any such information with March CU. So I just wanted to confirm.
Thanks again,
V
Hi Chander,
this is the March 2019 patch – so of course it cannot address a patch in itself.
Or are you mixing dates?
Cheers,
Stefan
Hi Stefan,
Will these be part of next CU? if yes, Can you confirm which CU?
•KB 4462208 – SharePoint Foundation 2013 (core components)
•KB 4462202 – SharePoint Server 2013 (core components)
Thanks
The PUs are alwys included in the CUs of the same month.
Cheers,
Stefan
Thanks a lot for your confirmation. We are good with that farm then.
Can you please provide any solution for missing/required status in CA. We are not able to patch with recent cumulative patches in SP2013.
To restore missed installers from bad server to good server using OPUtil.vbs , but we could not get that file. please suggest any sources for OPUtil.vbs.
Last time we have patched (re-released) Service Pack 1 [15.0.4571.1502] on old Service Pack 1 [15.0.4569.1506] And patched December 2015 CU [15.0.4779.1000].Every things in central admin was shown installed that time.
But recently, it was showing missing/required for few components for central admin server in patch status page of central admin site.
Please find the below two components one is for showing good and 2nd one is for showing missed (Showing empty space as mentioned below).It also showing missed for few of other components.
Microsoft Workflow Solutions Framework English Language Pack 15.0.4571.1502 Installed
Update for Microsoft SharePoint Enterprise Server 2013 (KB3114345) 64-Bit Edition 15.0.4779.1000 Installed
Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit Edition 15.0.4571.1502 Installed
PerformancePoint Services for SharePoint 15.0.4569.1506 Installed
showing empty space 15.0.4571.1502 Missing/Required
Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit Edition 15.0.4571.1502 Missing/Required
Tried with Get-SPProduct -Local as many times but no luck.
And with (Get-SPProduct -Local).patchableunitdisplaynames , it seems its looking for lanuguage pack but we only use English language then why we need to patch language pack for all languages.Please suggest.
Get-SPProduct -Local
ProductName Required Missing Servers
———– ——– ——- ——-
Microsoft SharePoint Server… True {}
(Get-SPProduct -Local).patchableunitdisplaynames
Microsoft SharePoint Foundation 2013 1033 Lang Pack
Microsoft Server Proof (Russian) 2013
Microsoft Server Proof (German) 2013
Microsoft Server Proof (French) 2013
Microsoft Server Proof (English) 2013
Microsoft Server Proof (Arabic) 2013
Microsoft Server Proof (Spanish) 2013
Microsoft InfoPath Forms Services
Microsoft Shared Coms English Language Pack
Microsoft SharePoint Foundation 2013 1033 SQL Express
Microsoft SharePoint Multilingual Solutions English Language Pack
Microsoft Office PowerPoint Services English Language Pack
Microsoft Education English Language Pack
Microsoft Access Services English Language Pack
Microsoft Document Lifecycle Components English Language Pack
Microsoft Slide Library English Language Pack
Microsoft Visio Services English Language Pack
Microsoft Excel Services English Language Pack
Microsoft Search Server 2013 English Language Pack
PerformancePoint Services in SharePoint 1033 Language Pack
Microsoft SharePoint Portal English Language Pack
Microsoft Workflow Solutions Framework English Language Pack
Microsoft Slide Library
Microsoft InfoPath Form Services English Language Pack
Microsoft Web Analytics English Language Pack
Microsoft Word Server English Language Pack
Microsoft Education
Microsoft Access Services Server
Microsoft Office PowerPoint Services
Microsoft SharePoint Foundation 2013 Core
Microsoft Shared Components
Microsoft Visio Services Web Front End Components
Microsoft Excel Services Components
Microsoft Document Lifecycle Components
Microsoft Search Server 2013 Core
Microsoft Workflow Solutions Framework
Microsoft User Profiles
Microsoft SharePoint Portal
PerformancePoint Services for SharePoint
Microsoft Word Server
Microsoft Web Analytics Web Front End Components
Microsoft Excel Mobile Viewer Components
Microsoft SharePoint Multilingual Solutions
Microsoft SharePoint Server 2013
You can find OPUtil here: https://gist.github.com/jwstl/0240b284ecf7049731294e53587f4bc5
Thanks!
Moment of silence for the shotdown blog – LOL
New one looks good!
Stefan, can you confirm – I installed Feb 2019 patch kb4462155 in our 2016 Development environment, then the Feb fix KB3085363 when it came out, in Dev (over the first one), Test and Production 2016 environments. Looking back at March patches I see KB4462211 listed as “important” not “critical” like the Feb patches. We generally don’t install until we get a critical patch. I also see this is a microsoft update patch. So my questions are 1) Does it not require the configuration wizard? Just unusual in my experience. and 2) Has the severity been updated since it was issued?
Hi Nicola,
I cannot talk about the classification (important vs. critical) as I don’t have background on this.
About the config wizard: all Sharepoint fixes require it – no exceptions.
Cheers,
Stefan
Is there an update on this? The April 2019 CU is out but does not mention this issue.
Hi Xamio,
the fix is still in development.
If you would like to get updates, please open a support case with Microsoft on this.
Cheers,
Stefan
Some typo on this page, https://support.microsoft.com/en-us/help/4464518/description-of-the-security-update-for-sharepoint-server-2019-april-9, it says “Applies to: Microsoft SharePoint Server 2013 Service Pack 1”
Thanks Aleksandr,
I have forwarded this Information to the correct team to get this updated.
Cheers,
Stefan
The March 2019 PU for SP 2016 addresses the issues with SQL 2017 (https://support.microsoft.com/en-us/help/4462211/description-of-the-security-update-for-sharepoint-enterprise-server). I haven’t found any further PUs or documentation otherwise indicating this has been fixed for SQL 2016. I haven’t rolled out SP 2016 yet and still had my UAT environments on the March 2017 patch. The majority of those db’s were set to 130. After installing the March 2019 PU, all db’s are now set to 110. Is it this patch that corrects the compat level issue or a different patch that’s rolled in to this one?
Hi KurtEichler,
the KB you quoted contains the relevant Information:
“Contains fixes for the following nonsecurity issues in SharePoint Server 2016:
Enforces setting the SharePoint database compatibility level to 110 to avoid high CPU use when you use Microsoft SQL Server 2017 in the SharePoint farm.”
Cheers,
Stefan
The fix is as well in November CU and in December CU.
Cheers,
Stefan
Hi Stefan, We applied the November CU already in all our farms (SP 2013,2016 & 2019). The KB’s mentioned in the below article points to the November CU only. What’s the action we need to take now ?
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1491
Hi Karthikeyan,
none. As you can read for yourself in the “Revisions” section of the CVE:
“…This is an informational change only. Customers who have successfully installed the applicable updates do not need to take any further action…”
Cheers,
Stefan
Hi Stefan,
For this CVE-2019-1491 vulnerability.
https://www.us-cert.gov/ncas/current-activity/2019/12/18/microsoft-releases-information-cve-2019-1491
If we apply SharePoint 2016 November 2019 CU (KB 4484147), then it should cover the this vulnerability
Can you confirm?
Thanks as always
Henry