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

4 Comments

1. 

   Guy Amir
   On 19. May 2025 Permalink

   Hello Stefan,
   After applying this CU to my farm, Search schema page (and other search configuration pages) still has the error “The server tag is not well formed” that was introduced in the March 2025 CU (extra white spaces in the html).
   Back in March you mentioned it was planned to get fixed with the May 2025 CU.
   Do you know about a delay for a solution for this issue?

   Thanks
   Guy

   Reply
   1. 

      Stefan Reinike
      On 21. May 2025 Permalink

      I’m not sure why my comment from yesterday is no longer visible – here it is again:

      After contacting Microsoft Support, I received confirmation that, unfortunately, the fix that was planned to be released with the May 2025 CU has been delayed to the June 2025 CU release.

      Reply
   2. 

      Stefan Goßner
      On 21. May 2025 Permalink

      Hi Guy,
      the fix has been postponed to June. Please follow this blog post for updates:
      https://blog.stefan-gossner.com/2025/04/02/trending-issue-spse-the-server-tag-is-not-well-formed-on-certain-search-administration-pages-after-march-2025-cu/
      Cheers,
      Stefan

      Reply
2. 

   Zdenek Vinduska
   On 10. June 2025 Permalink

   Hello, our last patch before this was February 2025 (so no the new March update with PU).
   After installing on DEV environment it immediately started to have problems with connecting to SQL server even SHP Config Wizzard didnot started (with loading Config DB)
   Servers are on WS 2019. We do not have configured certificate on SQL connection.

   06/06/2025 14:53:00 1 ERR A failure occurred when trying to see if this machine was joined to a farm
   06/06/2025 14:53:00 1 INF Entering function Common.BuildExceptionInformation
   06/06/2025 14:53:00 1 INF Entering function Common.BuildExceptionMessage
   06/06/2025 14:53:00 1 INF Entering function StringResourceManager.GetResourceString
   06/06/2025 14:53:00 1 INF Resource id to be retrieved is ExceptionInfo for language English (United States)
   06/06/2025 14:53:00 1 INF Resource retrieved id ExceptionInfo is An exception of type {0} was thrown. Additional exception information: {1}
   06/06/2025 14:53:00 1 INF Leaving function StringResourceManager.GetResourceString
   06/06/2025 14:53:00 1 INF Leaving function Common.BuildExceptionMessage
   06/06/2025 14:53:00 1 INF Leaving function Common.BuildExceptionInformation
   06/06/2025 14:53:00 1 ERR 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, TaskCompletionSource1 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(TaskCompletionSource1 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, List1& 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)

   I read and I thought it is okay and the certificate is not required – you can set it as optional, but it does not working.

   Can you help me? Should we set the certificate on SQL connection or is there any other setting?

   Thank you for help

   Reply