After installing the March 2025 CU (or any subsequent update) for SharePoint Server Subscription Edition, certain search administration pages include incorrect ASP.NET tags leading to the following or similar error message:
An error occurred during the processing of /_admin/search/listmanagedproperties.aspx. The server tag is not well formed. System.Web.HttpException (0x80004005): The server tag is not well formed. at System.Web.UI.TemplateParser.ProcessError(String message) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() ...
June 2025 CU for SharePoint Server Subscription Edition includes a fix for this issue:
Permalink
Hi Stefan,
Hope you’re doing great! 🙂
After installing the June Cumulative Updates, we’ve observed the following:
Query Logging: Running successfully post-update.
User Profile Language Synchronization Job: Still failing. From the ULS logs, we’re seeing the following exception:
Could you please confirm if this is still related to the patch issue? We’re currently awaiting your input to proceed.
Thanks In Advance.
Permalink
We have the same problem, but at least the other problems seem to be solved.
Permalink
Yea we seem to have the same problem as well…. They will probably fix this in the July patch. I am going to guess/hope.
Permalink
Hi Chandu,
this issue is currently being investigated by the product group.
Cheers,
Stefan
Permalink
Hi Stefan,
Thanks for the update!
We’ll await the outcome of the product group’s investigation.
Best regards,
Chandu
Permalink
Hi Stefan,
Thank you for the update regarding the Language Synchronization Job issue. We’ll await further input from the product group on that front.
In the meantime, we’ve encountered a recurring issue with the Query Logging job, which is failing daily. Upon reviewing the logs, we found the following error:
As a temporary measure, we’ve been restarting both the Search and SPTimer services to stabilize functionality.
Could you please advise if this issue is also related to the recent updates or if there’s a recommended long-term resolution we should consider?
Appreciate your insights as always.
Thanks,
Chandu
Permalink
Hello all,
Does the issue “User Profile Language Synchronization Job: Still failing” only occur in SharePoint SE or also in other versions (SP 2016/2019)? And what impact does this problem have on the system?
Thanks,
Tom
Permalink
To my knowledge the problem only exists in SharePoint SE, I did not observe it in SharePoint 2016/2019. BTW the problem can also be observed in the User Profile Database with the Table [PropertyListLoc] being empty. Impact is the timer job above failing and the localization of the SharePoint User Profile properties missing (e.g. “SPS-JobTitle” instead of “Job Title”).
Permalink
Hello Martin,
Thank you very much for your information. 🙂
Tom