In the last week we received several support cases about problems introduced with July 2024 CU for SharePoint Server 2016 and 2019.
Symptoms:
PowerShell operations to create new site collections using certain site templates and enabling specific features like Document Set and Video and Rich Media fails with errors similar to the following:
In addition Test-SPContentDatabase for content databases report a large number of missing web parts:
In some scenarios messages of missing web parts are reported when running the SharePoint configuration wizard (psconfig).
This issue has now been documented in the Known Issues section of the KB articles for July 2024 CU for SharePoint Server 2016 and 2019:
- KB 5002618 – July 2024 CU for SharePoint Server 2016
- KB 5002615 – July 2024 CU for SharePoint Server 2019
Workaround:
The approved workaround for the failing PowerShell commands is to use the web UI to perform the affected operations. The web UI is NOT affected by the issue.
The warning of the missing web parts can be safely ignored. This will not affect the SharePoint site.
Reverting the web.config change that introduced the issue should NOT be done as this change is part of a security fix.
The product group has already identified the root cause of the issue has been identified and is looking for a solution for the issue.
A fix for this issue has been released with September 2024 CU for SharePoint Server 2016 and 2019.
Permalink
Thank you so much for your efforts.
Permalink
Hello Stefan.
I also want to thank you a lot for this! But would like to ask something related.
On our on-premise ShPt 2016 production farm I have noticed that this July 2024 CU was offered within Windows Update (WU).
We have so called “Microsoft Update” (MU) switched off in WU settings.
I was aware, since year 2015, that security fixes for server products are available via MU, as you wrote years ago https://blog.stefan-gossner.com/2015/02/26/sharepoint-cus-and-windows-update-important-update/
Was there some shift of delivery strategy for updates of Office server products?
This situation was also in previous month – June 2024, in May 2024 corresponding ShPt CU was not offered through WU.
Thanks in advance for your answer.
Permalink
Hi Ladislav,
tbh. I did not notice this.
If this is a concern for you, please open a support ticket with Microsoft. This will allow us to contact the relevant teams responsible this.
Thanks,
Stefan
Permalink
We saw the same issue in our environment.
Permalink
The latest SharePoint CU release has caused failures in creating new sites through the New-SPSite PowerShell command and issues with activating the DocumentSet and VideoAndRichMedia features. The command used ($site = New-SPSite -Url $url -OwnerAlias $user -Language 1033 -Template STS#0) results in critical errors.
Permalink
Hi Daniela,
that is correct.
This is exactly the issue this article explains.
Cheers,
Stefan
Permalink
Hi all
Have you been able to find a temporary solution to the execution of site creation powershell?
Regards
Permalink
Thank you so much for this update.
Last week I was troubleshooting this step on a test migration, after we had a successful test a few months ago, I was pulling my hair out!
Permalink
Hello Stefan
Thanks for your blog. it’s amazing.
I ran into a problem; errors started appearing in the logs over the weekend. Is this related to this CU?
Sitemaster sites cannot be created.
Event ID: 6141
Event Description: The site SITEURL could not be created. The following exception occurred: Original XSLT List View Web Part not found.
Permalink
Hi Dilya,
I have not seen this flavor. To be sure I would recommend to open a support case with Microsoft to get this investigated.
Cheers,
Stefan
Permalink
Is it correct that the CU July 2024 is the reason for the “Missing server side dependencies” error message in Central Admin? It did not appear right away, but apparently after a weekly SharePoint check.
Just want to be sure we don’t have another issue.
Regards,
Ron
Permalink
Hi Ron,
I have not heard about such a problem being caused by a CU.
Usually it means that parts of a customer solution are not installed on the specific machine.
If you need assistance with this I would recommend to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Permalink
My webpart reporting PowerShell scripts are no longer working since this patch. Calls to GetLimitedWebPartManager return ErrorWebPart objects. Accessing the ErrorMessage property also returns a very helpful “This page has encountered a critical error. Contact your system administrator if this problem persists.”
I’m assuming this is likely due to the long list of MissingWebPart references inside the content databases? If anyone has any potential workarounds (other than using the web UI), I’d appreciate the input. Otherwise, I guess I’m holding out till September CU.
Permalink
Only relevant when using NINTEX
Dear community,
We’ve identified an issue with the Nintex Create Site Collection action that seems to be related. We’re currently awaiting confirmation from Nintex but wanted to share a potential workaround in the meantime.
We are experiencing issues creating site collections using Nintex when the workflow is handled by a application server/back-end (workflows with pauses or tasks). Logging shows a critical error prompting us to contact the system administrator. ULS logs don’t provide much more information.
To solve it, we made sure the action runs on the on the web-front-end, by removing the pause or placing the Create Site Collection action in a separate workflow and trigger it from the one that runs on the back-end.
Permalink
I had this isssue, with a powershell scripted deployment to GCP. My site collection creations was failing. In this case I had no option to use the GUI to create the site collection. I found that the old stsadm.exe still worked to create the site collection I needed.
Permalink
Hi,
just to be shure:
The problem has not been addressed in KB 5002630, right?
Regards,
Thoren.
Permalink
Hi Thoren,
no – a fix is planned for September 2024 CU.
Cheers,
Stefan
Permalink
Does anyone happen to know if the regressions are in the July PU as well as the July CU?
Permalink
Its in both.
Permalink
Hi Stefan,
Morning.
Is this issue fixed in Sept CU released now.
Thanks,
Anil
Permalink
Hi Anil,
Yes this was fixed. In the KB article for SP2016 and SP2019 of September CU you see this information:
“Fixes the known issue in KB 5002615 in which some SharePoint PowerShell cmdlets don’t function correctly because the Microsoft.SharePoint.ApplicationPages.SPThemes class is marked as unsafe in all Web.config files.”
Cheers,
Stefan