TMSavePoint Hotfix Available?

Just updated to Version: 2.150.1704.0 64-bit (January 2026).  Still an issue.  What's worse, now when I refresh the model I get the error and no way to work around it.  Looks like my day is done.  Thanks MS!

Hi bhalicki ,

To better understand and help with the TMSavePoint issue, could you please share a bit more information about when and how the error occurs? Specifically, it would be helpful to know the exact error message you’re seeing, the action that triggers it (for example, saving, publishing, or modifying the model), and whether this happens consistently or only in certain scenarios. Details such as the size or complexity of the model, and any recent changes made before the issue started would also help narrow down the root cause.

Thank you

Hi bhalicki ,

I wanted to check if you had the opportunity to review the requested information . Please feel free to contact us if you have any further questions.

Thank you.

Hi v-nmadadi-msft ,
When I was using November 2025 edition, the issue used to occur when creating a measure and either cancelling during creation, or fully creating and attempting to delete the measure.  It would crash with an error "TMSavePoint::VerifyProxyCreationAllowed".  I upgraded to January 2026 edition and now when I try to refresh the model, it crashes (with the same error), but often gets stuck in a loop and the only way to recover is to kill the PowerBi process (losing any work since the last save).  I would consider the model complex (it has a local model and also connects to a shared semantic model).  It seems to be an issue only for older reports when using on November 2025 and higher.  New reports created with Jan 2026 edition don't seem to exhibit the same issues, although granted I have not spent time developing a complex model to fully replicate the issue.

I have already escalated this issue to Microsoft.  This has basically prevented me from doing any further reporting work, resulting in considerable loss of income.  I hope that people take this on board when choosing a vendor for analytics (and other software).