Trying to save change to model from TE3 while model is reprocessing will cause TE3 to hang indefinitely

[Javanite]

Experienced this issue while trying to save a new measure to the model while my coworker was in the middle of a large reprocessing action and TE3 will pop up the "Please Wait - Saving Changes..." box and will never complete which results with me having to kill TE3 with task manager.

Suggested fix is for TE3 to recognize that there is a lock on the model due to reprocessing and throw an error or offer a "cancel" option to the user in case it's taking too long.

[otykier]

This one is tricky.

1. There is (to my knowledge) no good way to detect existing (blocking) transactions on all types of Analysis Services instances (that would require access to server-admin level DMV's, which we do not have in for example Power BI Premium XMLA).
2. The TOM Model.SaveChanges method cannot be cancelled.

I'm afraid at least for now, the answer will have to be "please coordinate with your coworkers" or "don't use the same database when developing in parallel". Sorry!

[Javanite]

I can appreciate that answer, thanks. It would still be nice for TE3 to gracefully handle the timeout, however. If it tries for too long, couldn't you just throw a generic error?

[seedjay1]

Help me understand why the TOM-version of the POST /refreshes api call wouldn't suffice here? (it returns error if a processing is already happening) https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-async-refresh

[otykier]

TOM doesn’t have anything equivalent to the async refreshes API. Also, using that http endpoint is not a viable option in general, as it is only available for Azure AS (not on-premise SSAS, not Power BI XMLA). Also, the transaction could be blocked for reasons other than refresh operations.

[seedjay1]

I was afraid that would be the answer :(

Oh well, thanks much!