Semantic model refresh failed after migration from Premium to Fabric capacity

[filip_ai]

[EDIT 9 Dec]: I decided to migrate the workspace to the F64 once more. Tried to refresh and the data source error was NOT reproduced. All refreshes completed successfully. The same happened when I reassigned the workspace back to the original P2 capacity. I am suspecting there was an intermittent error in the backend during the first migration test.

I have moved several of our PBI workspaces from our Premium (P2) to Fabric capacity (F64) (both are in West Europe). Overall it works seamlessly both migrating and moving back to P2). However, for one specific workspace, there are several semantic models where we encountered refresh issues, either during migration (i.e. in the F64 capacity) as well as after rollback to P2.

The error message is the same:

Data source error: The session was cancelled because it is connected to a database that no longer belongs to this PowerBI Premium capacity. This may be because of workspace migration or capacity deprovision.

This error also happen when I try to alter one of the models (adding a simple measure) from the local PBIX to the model in the service.

The sources used in the models varies, but one of the models only have two sources:

Source = Csv.Document(Web.Contents("https://....sharepoint.com/sites/ ... /ReportObjects_VisualObjects.txt"),[Delimiter=" ", Columns=9, Encoding=65001, QuoteStyle=QuoteStyle.None])

Source = AzureStorage.DataLake("https://....dfs.core.windows.net/data/ ... /"),
#"Filtered Rows" = Table.SelectRows(Source, each [Date modified] > RangeStart and [Date modified] <= RangeEnd)

Update: I removed any references to external tables used in a view in the SQL DW source in on of the models, and then the refresh worked immediately. So this kind of source seems to be an issue, at least in our case.

Anyone experienced something similar? Any ideas how to resolve this? Any link to Microsoft documentation related to this?

Thanks!

[filip_ai · Accepted solution]

See my edit in the original post. Issue resolved after a new migration and rollback. Not sure why though.

[blopez11]

Thank you for the follow up.  It will be helpful as we look to migrate the beginning of the new year.

[SaiTejaTalasila]

Hi @filip_ai ,

You can refer this article I hope it helps you with the migration process.

https://www.microsoft.com/en-us/microsoft-fabric/blog/2024/12/02/automate-your-migration-to-microsof...

Currently, the organisation which I'm working for have some more time(we need to move after mid 2025) as they have enterprise agreement.At this moment we are not planning anything.

Thanks,

Sai Teja 

[filip_ai]

Thank you @SaiTejaTalasila. Very useful information regarding migration in general. Unfortunately nothing related to the specific error I encountered.

[blopez11]

I am curious about this as we are planning on migrating workspaces from our premium capacity to a fabric capacity at the beginning of the year.