The product group released the October 2024 Cumulative Update for SharePoint Server Subscription Edition.
Monthly SharePoint Server Subscription edition updates are released as a single unified “uber” package containing both the language independent and language dependent fixes. Language independent and language dependent fixes will no longer be released separately. This is similar to the full server packages released for SharePoint 2013.
The KB article for October 2024 CU will be available at the following location in a couple of hours:
- KB 5002649 – October 2024 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for October 2024 CU is available through the following link:
- Download October 2024 Update for SharePoint Server Subscription Edition
This is also a security update!
It is irrelevant which language you pick on the drop down in download center. It will always download the same package.
After installing the fix you need to run the SharePoint Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint Server Subscription Edition October 2024 CU Build Number: 16.0.17928.20162
Important: To minimize the installation time for SharePoint Server Subscription Edition Fixes, please follow the guidance in the following article: Solving the extended install time for SPSE CUs
Related Links:
- Technet: 24H1 Feature Update for SharePoint Server Subscription Edition
- Technet: Updated Product Servicing Policy for SharePoint Server Subscription Edition
- Technet: FAQs for SharePoint Server Subscription Edition product servicing policy
- Blog: SharePoint Patching Best Practices
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
- Blog: Solving the extended install time for SPSE CUs
Permalink
Hello Stefan,
the installation took more time than usually. We had also several warnings in our event logs during the installation:
Event ID: 10010 RestartManager
Application ‘C:\Windows\System32\inetsrv\w3wp.exe’ (pid …) cannot be restarted – Application SID does not match Conductor SID..
But we are happy to have the script error solved!
Martina
Permalink
Does this update include the latest feature pack as well, or do I need to install that update first?
Permalink
Hi Scott,
SharePoint fixes are cumulative. So the fixes always include all changes previously released.
With other words: the latest feature update is included in October CU.
Cheers,
Stefan
Permalink
Hi,
The security update KB5002649 was pushed in with the Windows Update. When We ran the Configuration Wizard, we got the following errors. below error.
PS: We have not created any “User Defined Objects’ in our SP databases as it is not recommended. Has anyone faced the below scenario?
Failed to upgrade SharePoint Products.
This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: https://go.microsoft.com/fwlink/?LinkId=2155803
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Number of user defined objects dropped incorrectly = ‘2554’ (EventID:ajyyy)
User Defined Object [proc_GetVersion] Modified (EventID:ajyyz)
User Defined Object [proc_SetVersion] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_ALL] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_NoLock_ALL] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_Site] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_NoLock_Site] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_SiteDelTransId] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_NoLock_SiteDelTransId] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_XLock_SiteDelTransId] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_CI] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_Site] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_NoLock_Site] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_DirLeafLike] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_NoLock_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_UpdLock_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_XLock_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_RepeatableRead_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_UpdHoldLock_Url] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_Url_Level] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_NoLock_Url_Level] Modified (EventID:ajyyz)
User Defined Object [TVF_Docs_Url_LevelLT] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_Url_Level] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_DelIdDirNameEqLike_NotForDelete] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_DelIdDirNameEqLike_Value] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_XLock_DelIdDirNameEqLike_NotForDelete] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_XLock_DelIdDirNameEqLike_Value] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_DelIdPId] Modified (EventID:ajyyz)
User Defined Object [TVF_AllDocs_NoLock_DelIdPId] Modified (EventID:ajyyz)
There are additional upgrade errors that are not shown here. Open the upgrade log to view all errors.
BR,
Soni
Permalink
Will the October patch fix the issue where most of the ribbon buttons for the timeline web part have stopped working in modern browsers (set the date range, display as a bar/callout, etc)?
Permalink
Hi Manisha,
I have not heard about this issue and I also cannot see any related work item for such an issue.
Did you open a support case with Microsoft to report this issue?
Cheers,
Stefan
Permalink
Hello Stefan,
we found an interesting bug with german language. If you have a list or library view, add date columns and add any column with column formatting: the date reads 30.12.1899.
I tried it with PNP Examples Edit Button (what we usually use for easier edit like in past) and Blur from this site:
https://github.com/pnp/List-Formatting/tree/master/column-samples
The real date is still saved correctly and in classic view or modern view without column formatting is still correct.
Do you know of it? Or should we create a ticket?
Thanks for your efforts with the on premise platform
Best regards
Martin
Permalink
Hello Martin,
we are having the same problem, List items which contain a date column and have another column with JSON-formatting display a wrong date. It seems that the month and day items get exchanged, so if I enter 10th of May it displays 5th of October, but for 20th of May it displays 30th December 1899 because the month is not a valid month.
Before we installed the update everything worked fine.
Regards,
Martina
Permalink
Hello Martina,
interesting, now it makes sense why some dates are working (i.e. 11.11.2024 is working but 18.11.2024 not ), thanks for the input 😊
Did you create a Microsoft Support Ticket already?
We also have an issue with Highlighted content webpart added with pnp powershell, but there i still need to investigate more, when i have time.
Best regards
Martin
Permalink
Hello Martin,
no I haven’t opened a ticket yet. I would like to wait for the November Update and test if there is any solution provided there. I dont think it will solve the problem but lets hope. 🙂
lg, Martina
Permalink
Hello Martina,
yes, let’s hope so 😀. Something is wrong with JSON in general in this CU (we waited since May on a stable CU 😐).
The PnP Powershell problem (Add-PnPClientSideWebPart with ContentRollup) with the highlighted content, I could resolve by setting the Propertiesjson attribute of the webpart, which was not necessary in the past.
If someone has the same issue let me know.
Thanks, Martina, if I find out more about the dates, I will let you know. I hope maybe Stefan answers, else we will create a ticket.
Best regards
Martin
Permalink
Hello, was the issue with wrong dates in German language solved in November CU or do we have some fix for that issue?
Permalink
Hi Miro,
the issue has been reported to Microsoft after release of November CU. So it is technically impossible to have it fixed in November CU.
It was even after the cut-off date for December CU when the first case reporting this arrived. That means it will most likely not be in December CU either.
Cheers,
Stefan
Permalink
Hello Miro,
like Stefan said, unfortunately the november CU did not fix this issue.
We have currently a ticket open with Microsoft about this issue. I will let you know here (also for Martina) if we get any info or workaround.
Best regards
Martin
Permalink
Hello Martin & Stefan,
thanks for the information, its good to know that there will be a fix.
Regards,
Martina
Permalink
Update:
I got now an answer from microsoft that the issue can be reproduced.
But they ask how critical the issue is and what would be the problems if this issue does not get fixed / will not be supported 😒.
Now I am slightly concerned that they just drop it. Since we can still work with the detail panel without the json formatting.
Would be good if Miro or Martina, you could also create tickets. I can share with you the microsoft tracking number, if needed.
Best regards
Martin
Permalink
Hello Martin,
thanks for sharing this with us, I also opened a ticket now, so hopefully there will be a solution provided by Microsoft.
Regards,
Martina
Permalink
Hi Martina,
please send me your SR number. I will handle the escalation for Martin and if I can combine both it will definitely help.
Thanks,
Stefan
Permalink
Hi Stefan,
thanks for your help, I sent a message to you with the ticket number.
Regards,
Martina
Permalink
Hi Manisha,
Yes, October patch fixed the issues with Timeline.
/Johnny
Permalink
Hello Stefan,
We have found an issue in regards to searching and navigating in grouped listviews. When a user searches in the listview using the “Search” box in the quick menu in a listview with grouping and then clicks into a grouping heading of the search result and then presses the “Search result for …” in the breadcrumb, then the user gets an error: Something went wrong.
Best regards
Ida
Permalink
Hi Ida,
if you need this investigated in more detail, please open a support case with Microsoft.
Cheers,
Stefan