This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 17%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Hi everyone,
SQL Server 2022 CU26 appears to break Master Data Services web application.
After patching to CU26 (16.0.4265.3), the MDS web application loads, but is completely empty.
The MDS database and data remain intact and are visible through SQL views/tables. Uninstalling CU26 does not resolve the issue because MDS web application assemblies in Master Data Services\WebApplication\bin remain at version 16.0.4265.3.
A temporary workaround is replacing the newer Version of the files in "...\WebApplication\bin" by the older version.
I'm assuming that this is an actual bug in the CU26 patch, therefore is there any possibility of including a fix in the next CUs?
Best regards,
Simon
Additional SQL Server features and topics not covered by specific categories
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 88%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hello, I am facing same issue on my side as well. I am getting MDS API call error 400 bad request while opening any of the entities in MDS website. Additionally I am not able to create any new entity or attributes in MDS. Did you find any solution for this issue?
Did you test this with CU27? According the post from Henrik Munch, this seems to be fixed in CU27. (I don't use MDS myself, so I cannot speak from my own experience.)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 72%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHM%3C/text%3E%3C/svg%3E)
We have justed installed CU27 on our other SQL2022 Environments and I can confirm that the issue has been resolved for us by this.
Nothing in the CU27 descriptions specifically states anything about MDS as far as I recall.
But after completely clearing our browsers cache, we can now see the data in a model in the Explorer.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 28.000000000000004%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPN%3C/text%3E%3C/svg%3E)
I’ve also experienced that CU27 fixes this issue. However, even after applying CU26 and CU27, it’s still not possible to create a new entity, and the attributes are not listed for an existing entity — which also means that new attributes cannot be created through the Web interface.
Master Data Services is not the hottest component in the SQL Server portfolio, and I seem to recall that it is not included with SQL 2025. But breaking and dropping it in a CU sounds overly brutal.
I would recommend you to open a support case. I think that would be the best way to make Microsoft aware of the issue.
Hi Erland,
I currently only have a support contract with MS Office and they referred me back to this Q&A. Therefore I could not open a support case in which it might be addressed.
Best,
Simon
The other alternative is to report it as a bug on https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0. However, this is more to let Microsoft know about the issue, and they will triage the issue as they see fit. On the one hand, if something is broken, they should fix it. On the other hand, MDS is a product they have abandoned. MDS is not included in SQL 2025, as I recall.
Hi Erland,
will do so. Thank you for your support!
Best,
Simon
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
It seems to be fixed in CU 27
Hi Henrik,
I patched the server last week with the CU27 (16.0.4295.3) but I needed to use the same workaround as in the CU before.
Where did you get the info of it being resolved?
Best,
Simon
Issue has been resolved after CU27 patch. I can see the data in entities after the patch.
But I have a problem in creating entities and attributes in MDS. It is throwing API 400 bad request error. Anyone else facing this issue?