Forum Discussion

NAOS's avatar
NAOS
Advocate III
6 years ago
Solved

Cannot refresh or save dataflow - Cannot acquire lock for model

Hi all,

Just coming back from holidays (Happy new year to you all!) and various dataflows have sttoped working while I was away which is not good...

I try to refresh on schedule or manually and they don't refresh. There isnt an obvious error since all error files say all entities refreshed correctly, while the dataflow failed to refresh, giving no error message at all.

If I try to edit the dataflow and then save, a window like the following appears:

 

Any ideas on how to fix this?

 

Thanks,

Dataflow
Need Help
  • PaulKn's avatar
    PaulKn
    6 years ago

    NAOS I'm experiencing something similar with one particular dataflow that has two entities connecting to an Azure SQL Database without using a gateway. It started failing on Thursday 02/01. The dataflow refresh status shows as "Failed" but the Entity refresh status for both entities shows as "Completed". There is no error message in the "Error" column. It fails on the scheduled refresh and a manual refresh.

     

    When I try to modify the dataflow and save the changes I get the "cannot acquire lock for model" error message.

     

    If I export the JSON and create a new replica dataflow in the same workspace by importing the JSON it works fine.

     

    I will be interested to know if you find a solution!

  • PaulKn's avatar
    PaulKn
    6 years ago

    NAOSRather than restart the whole capacity (which we would need to be done out of hours to minimise disruption) I went into Admin Portal >> Capacity Settings and under Workloads >> Dataflows increased the Max Memory by 1%, applied the change and then changed it back to its original setting and applied the change again. This only took a few seconds. The theory was that this would force the dataflow workload to restart which might clear the problem.

     

    It appears to have worked as I am now able to refresh the dataflow ok, so this might be something worth suggesting to your IT Department as being less disruptive than restarting the whole capacity.

11 Replies

    • NAOS's avatar
      NAOS
      Advocate III
      6 years ago

      Hi v-eachen-msft ,

       

      Thanks for your answer. Unfortunately, that doesn't work for me. The users in that thread actually mention that even restarting the premium capacity several times it wouldn't fix that bug.

      If you check the answer given to that post, you'll notice it isn't actually the solution nor it fixes the problem.

       

      I've raised a ticket to support and will wait to see what they can add to it.

       

      If you could in the meantime try to find out more about the issue with the team it would be much appreciated since more than a few of our dataflows are presenting this problem...

       

      Thanks

      • venal's avatar
        venal
        Memorable Member
        6 years ago

        NAOS 

        Thanks for the confirmation that you already submitted a support ticket.

        Can you please share the support ticket for quick traction on it.

         

        If you have any queries, please let us know.

         

        If this post helps, then please consider Accept it as the solution to help the other members find it more
        If this post was helpful may I ask you to mark it as solution and click on thumb symbol?

         

        Best Regards,

        Venal.