February 2025 CU for SharePoint Server Subscription Edition is available for download

8 Comments

1. 

   Tom
   On 14. February 2025 Permalink

   Just getting onboard with SharePoint Subscription Edition patching and we find the period to install the binaries is much longer than prior SharePoint versions. Any reason for this? Anything we can do to speed it up?

   Reply
   1. 

      Stefan Goßner
      On 14. February 2025 Permalink

      Hi Tom,
      yes. Please check article highlighted above.
      Here again for your convenience:
      https://blog.stefan-gossner.com/2024/03/08/solving-the-extended-install-time-for-spse-cus/
      Cheers,
      Stefan

      Reply
2. 

   Gabriel
   On 26. February 2025 Permalink

   Hi Stefan,

   I have discovered that since the October 2024 CU for SharePoint Subscription Edition, the database role WSS_Content_Application_Pools is not granted Execute permissions to stored procedures when setting up a new farm/config database with the patch slipstreamed into the installation media, or installed before configuring the farm with the Product Configuration Wizard.

   Notably, SharePoint Caching Service cannot start as service account due not being able to execute proc_insertCacheConfigEntry. This is logged with event id 5214: The EXECUTE permission was denied on the object ‘proc_insertCacheConfigEntry’, database ‘RIG_Config’, schema ‘dbo’.

   I have an (for now) open support ticket but they are not able to reproduce their scenario in their lab and they are getting push back from the Product Group, who does not plan on investigating this. No real explaination is given.

   The issue is still present in February 2025 CU.

   Is this something that you can shed some light on?

   Kind regards,
   Gabriel

   Reply
   1. 

      Stefan Goßner
      On 1. March 2025 Permalink

      Hi Gabriel,
      I’m not familiar with this problem.
      Cheers,
      Stefan

      Reply
      1. 

         Gabriel
         On 3. March 2025 Permalink

         Hi Stefan,

         Thank you for reply. At least some colleague may find this thread and see that they are not alone and not going mad.

         Support is able to reproduce the issue in their lab, but so far the Product Group is, according to support, not willing to confirm or deny whether is change to stored procedure permissions in the config database is intentional or not.

         Cheers,
         Gabriel

         Reply
3. 

   Andy
   On 27. February 2025 Permalink

   Hi Stefan

   We encountered an issue on two separate new SPSE farms regarding the farm property “WebPartSupportedSimplePropertyNames”. Our solution requires to add the following exclusion, which usually always worked on other farms:

   $f=get-spfarm
   $f.AddGenericAllowedListValue(“WebPartSupportedSimplePropertyNames”,”data-gitqueryparam”)
   $f.update()

   The two individual farms with CU Feb 25 face the same issue:

   Exception calling “AddGenericAllowedListValue” with “2” argument(s): “An object of the type Microsoft.SharePoint.Administration.AllowedList named
   “WebPartSupportedSimplePropertyNames” already exists under the parent Microsoft.SharePoint.Administration.SPFarm named “_Config”. Rename your
   object or delete the existing object.”
   At line:2 char:1
   + $f.AddGenericAllowedListValue(“WebPartSupportedSimplePropertyNames”,” …
   + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
   + FullyQualifiedErrorId : SPDuplicateObjectException

   Any idea what could cause this issue would be much appreciated.

   Best regards
   Andy

   Reply
   1. 

      Stefan Goßner
      On 27. February 2025 Permalink

      Hi Andy,
      seems there is already a value configured with the same name.
      I would suggest to evaluate what values are already set using: $f.GetGenericAllowedListValues(“WebPartSupportedSimplePropertyNames”)
      Cheers,
      Stefan

      Reply
      1. 

         Andy Steiner
         On 27. February 2025 Permalink

         Hi Stefan
         Many thanks for your quick reply!

         I’ve tried that already but it is empty. What I’ve also tried is to remove the content with the following PS line:
         $f.RemoveGenericAllowedListValue(“WebPartSupportedSimplePropertyNames”,””)
         $f.update()
         This does not run into an error. However, I’m still not able to add the parameter afterwards, even after iisreset, server reboot, psconfig wizard)

         Meanwhile, I’ve found a post to exact the same issue and an MS Support case got opened for it: https://learn.microsoft.com/en-us/answers/questions/1372987/the-control-type-system-web-ui-htmlcontrols-htmlan

         The recommended solution is to remove the security controls completely..! Well, it would solve that particular issue… 😛

         I’m not confident to get this solved if we invest the time to upen another support case… 🙁

         Reply