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

The product group released the March 2025 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 March 2025 CU will be available at the following location in a couple of hours:

  • KB 5002698 – March 2025 Update for SharePoint Server Subscription Edition

The download for March 2025 CU is available through the following link:

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 March 2025 CU Build Number: 16.0.18526.20080
 
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:

11 Comments


  1. Hi

    In improvements and fixes, we see below fix as fixed. is this issue is reported on applying any SE patch? which fixed in this March 2025 patch?

    Fixes an issue in which a SharePoint 2013 workflow cannot be run successfully.

    Thanks
    Praveen

    Reply

    1. Hi Praveen,
      this is not related to a regression introduced with an earlier fix if this is what you are looking for.
      Cheers,
      Stefan

      Reply

      1. Thanks Stefan. But how can we know what it fixed in that ?

        Reply

        1. Hi Praveen,
          if you do not have problems when running the SP2013 workflows you will not benefit from this fix.
          Cheers,
          Stefan

          Reply

  2. After installation of binary, the PSConfig fails with error:

    Failed to detect if this server is joined to a server farm, Possible reasons for the failure could be that you no longer have the appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessable or the server has been removed from the server farm. Following error was found in he PSCDiagnostics log:

    An exception of type Microsoft.Data.SqlClient.SqlException was thrown. Additional exception information: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The target principal name is incorrect.) Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The target principal name is incorrect.) —> System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
    at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource
    1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
    at Microsoft.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource
    1 retry)
    at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry, SqlConnectionOverrides overrides)
    at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
    at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection()
    at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
    at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)
    at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)
    at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(SPDatabase database, Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence)
    at Microsoft.SharePoint.Administration.SPDatabase.get_BuildVersion()
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_StoredProceduresSchemaVersion()
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_SupportsConfigCollectionCache()
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.FetchNewObjectsFromDatabase(Int64 lastRefreshed, RefreshCacheFlags refreshCacheFlags, SqlParameter& returnValue)
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RefreshCache(Int64 currentVersionOverride, RefreshCacheFlags refreshCacheFlags, List
    1& newObjects, List`1& deletedObjects, Int64& newestObjectVersion)
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RefreshCache()
    at Microsoft.SharePoint.Upgrade.SPManager.UpgradeDatabaseObject()
    at Microsoft.SharePoint.PostSetupConfiguration.Farm.TryIsJoinedToFarm(TaskBase task, Boolean& isJoined, Boolean& tryIsJoinedSucceeded, Boolean reload)
    ClientConnectionId:2e84eee2-b1b6-4072-a9b2-4a3a1ecc0df5
    Error Number:-2146893022,State:0,Class:20

    Reply

  3. Hi Stefan,

    We have hybrid search service between SharePoint Online & Onprem (SPSE) environment. I can see the (Download the Onboard-CloudHybridSearch-SPOONS.ps1 script) powershell script uploaded and available to download at below microsoft page.

    https://support.microsoft.com/en-us/topic/march-11-2025-update-for-sharepoint-server-subscription-edition-kb5002698-d2f72cdc-deae-4cd1-b5ef-a0381c1c4342

    Question : Do we need to run this script in onprem environment post installing March 2025 update for sharepoint server subscription server?

    Cheers,
    Ganesh P.

    Reply

  4. Hi Stefan,

    After installing March 2025 update for sharepoint server subscription server, SQL instance got disconnected.
    We have AG setup. Unable to run the configuration wizard. Could you please let us know why? Is there any bug, issue in KB?

    Regards,
    Ganesh P.

    Reply

  5. Hi all,

    I had the same issue (SQL) after installing 2025 March CU.

    I’ve set Force encryption to No and SharePoint is working again.

    Best Regards,

    Zoltán Németh

    Reply

  6. Hi Stefan,

    after installing the CU March 2025, we receive the following error message when we click on the Search Schema link in the Search Service Application to display the Managed Properties.

    “Sorry, something went wrong
    An error occurred during the processing of /_admin/search/listmanagedproperties.aspx. The server tag is not well formed.”

    Do you also get this error?

    Reply

    1. The HTML tags in the following application pages looks very strange.

      /_admin/search/category.aspx
      /_admin/search/crawledproperty.aspx
      /_admin/search/listcategories.apsx
      /_admin/search/managedproperty.aspx
      /_admin/search/listcrawledproperties.aspx
      /_admin/search/listmanagedproperties.aspx

      The tags look like (additional spaces in the tags):
      <asp : label
      <wssawc : SPGridView

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.