cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted

Can't save dataflow, cannot acquire lock for model

Can anyone provide any insight into this error?

2019-10-15_10h52_55.png

I get it sparadically, when editing existing dataflows and trying to add new entities, or even creating new dataflows.  I don't have any other tabs open when the dataflow being edited, no other users are using it.

 

Edit1:

Hmmm I cancelled out, waited a few minutes, and went to make my changes again--however the changes are there.

 

So the save went through even with the model lock error...I wonder if it was trying to save twice behind the scenes?  The first save went through and the second failed because of the first pending, throwing the message?

 

Edit2:

I restarted my premium capacity and everything saves now.

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Can't save dataflow, cannot acquire lock for model

Hmmm I cancelled out, waited a few minutes, and went to make my changes again--however the changes are there.

 

So the save went through even with the model lock error...I wonder if it was trying to save twice behind the scenes?  The first save went through and the second failed because of the first pending, throwing the message?

View solution in original post

Re: Can't save dataflow, cannot acquire lock for model

This is what I've observed.

 

I have a few dataflows at work here.

 

For each entity, I have:

  • Ingest
  • Cleanse
  • Final

 

So I have

  • Customers_1-Ingest
  • Customers_2-Cleanse
  • Customers_3-Final
  • Orders_1-Ingest
  • Orders_2-Cleanse
  • Orders_3-Final

 

Each previous dataflow is a linked entity in the following one ("Customers_1-Ingest" is a linked entity in "Customers_2-Cleanse").  So refreshing the "1-Ingest" dataflows will refresh the downstream dataflows.

 

This also puts a lock on them.

 

All my "Final" queries are added as linked entities in "For Consumption_Customers and Orders".  Since they're linked, this dataflow gets locked when something upstream is refreshing.

 

What I've noticed is:

  • I can't refresh more than one "1-Ingest" at a time, because the first one puts on a lock on "For Consumption" so the second "1-Ingest" I try to run is unable to get the lock and fails with "MWC client failed with user or caller error".

 

 

View solution in original post

4 REPLIES 4

Re: Can't save dataflow, cannot acquire lock for model

Hmmm I cancelled out, waited a few minutes, and went to make my changes again--however the changes are there.

 

So the save went through even with the model lock error...I wonder if it was trying to save twice behind the scenes?  The first save went through and the second failed because of the first pending, throwing the message?

View solution in original post

Community Support Team
Community Support Team

Re: Can't save dataflow, cannot acquire lock for model

Hi @jeffshieldsdev ,

 

I saw you can do "save" action currently. Is your problem solved? If it is solved, you can accept your own answer.

 

Community Support Team _ Eads
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Can't save dataflow, cannot acquire lock for model

This is what I've observed.

 

I have a few dataflows at work here.

 

For each entity, I have:

  • Ingest
  • Cleanse
  • Final

 

So I have

  • Customers_1-Ingest
  • Customers_2-Cleanse
  • Customers_3-Final
  • Orders_1-Ingest
  • Orders_2-Cleanse
  • Orders_3-Final

 

Each previous dataflow is a linked entity in the following one ("Customers_1-Ingest" is a linked entity in "Customers_2-Cleanse").  So refreshing the "1-Ingest" dataflows will refresh the downstream dataflows.

 

This also puts a lock on them.

 

All my "Final" queries are added as linked entities in "For Consumption_Customers and Orders".  Since they're linked, this dataflow gets locked when something upstream is refreshing.

 

What I've noticed is:

  • I can't refresh more than one "1-Ingest" at a time, because the first one puts on a lock on "For Consumption" so the second "1-Ingest" I try to run is unable to get the lock and fails with "MWC client failed with user or caller error".

 

 

View solution in original post

chrisakatrace Frequent Visitor
Frequent Visitor

Re: Can't save dataflow, cannot acquire lock for model

I get this all the time. The only time I can get it to work is if I start updating in the morning, before I open any Power BI files or edit any files that the dataflow links to.

Helpful resources

Announcements
Ask Amanda Anything Q&A

Ask Amanda Anything Q&A

Learn the answers to some of the questions asked during the Amanda Triple A event.

October 2019 Community Highlights

October 2019 Community Highlights

October was a busy month in the community. Read the recap article to learn about some of the events and content.

New Solution Badges

New Solution Badges

Two waves of brand new solution badges are coming! Read the article for more information on our new community badges.

Analytics in Azure virtual event

Analytics in Azure virtual event

Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.

Top Kudoed Authors
Users Online
Currently online: 195 members 2,682 guests
Please welcome our newest community members: