cancel
Showing results for 
Search instead for 
Did you mean: 
Warehousing & Analytics
Engage in discussions on data warehousing, analytics, and BI solutions within the Databricks Community. Share insights, tips, and best practices for leveraging data for informed decision-making.
cancel
Showing results for 
Search instead for 
Did you mean: 

refresh power BI without premium, fabric instead

carlos_tasayco
Contributor

I have a job where I am refreshing my power bi semantic model, now my commpany change the workspace from Premium to Fabric, I am receiving this error message:

Run failed with error message System error occurred during execution of task Power BI Task: Semantic model update succeeded but refresh failed with error: This operation is not allowed, as the database '331d9e06-c39c-4f9d-864b-26fa2ec2469d' is in a blocked state. 

Genie is telling me the error is the following:

Why this happened:

  • PPU → XMLA Read/Write is ON by default → Databricks API refresh works ✓
  • Fabric Trial → XMLA Read/Write is OFF or Read Only by default → API refresh blocked ✗

Once XMLA is set to Read/Write, re-run the job and it will succeed. If you switch back to PPU temporarily, it will also work immediately.

Do you know if this is true? I am not an admin of power bi workspaces in my organization.

1 ACCEPTED SOLUTION

Accepted Solutions

szymon_dybczak
Esteemed Contributor III

Hi @carlos_tasayco ,

 According to docs:

“Any workspace migrated from a PPU environment to a non-PPU environment (such as Premium or shared environments) must have its datasets refreshed before use. Reports opened after such migrations without being refreshed will fail with an error like: This operation isn't allowed, as the database 'database name' is in a blocked state. You might need to do a full refresh through SSMS to fix this.” 

Also following LinkedIn post confirms this behavior: 

18How to fix the “Database is in a blocked state” Semantic Model error message after migrating to a Fabric capacity
https://www.linkedin.com/pulse/how-fix-database-blocked-state-semantic-model-error-message-cantu-r3e...

Solution 

After migration you need to perform full refresh. So, either ask your admin to do that for your or if you have enough permission on workspace you can try to do it yourself. 

If my answer was helpful please consider marking it as accepted solution

View solution in original post

1 REPLY 1

szymon_dybczak
Esteemed Contributor III

Hi @carlos_tasayco ,

 According to docs:

“Any workspace migrated from a PPU environment to a non-PPU environment (such as Premium or shared environments) must have its datasets refreshed before use. Reports opened after such migrations without being refreshed will fail with an error like: This operation isn't allowed, as the database 'database name' is in a blocked state. You might need to do a full refresh through SSMS to fix this.” 

Also following LinkedIn post confirms this behavior: 

18How to fix the “Database is in a blocked state” Semantic Model error message after migrating to a Fabric capacity
https://www.linkedin.com/pulse/how-fix-database-blocked-state-semantic-model-error-message-cantu-r3e...

Solution 

After migration you need to perform full refresh. So, either ask your admin to do that for your or if you have enough permission on workspace you can try to do it yourself. 

If my answer was helpful please consider marking it as accepted solution