Unable to refresh Semantic Model for development workspace in Microsoft Fabric

[ritika_ritika]

After migrating from Power BI Service to Microsoft Fabric,, the reports in the environment are encountering technical errors when manually refreshing the semantic model. I have attached a screenshot for your reference. Is there a way to fix this instead of removing the report and re publishing?

[v-priyankata]

Hi @ritika_ritika 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@rohit1991 @tayloramy Thanks for the inputs.

I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.

[v-priyankata]

Hi @ritika_ritika 

Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.

[tayloramy]

Hi @ritika_ritika, 

What do you mean by migrating from Power BI Service to Fabric? Those are the same thing. 

Did you move the report to a different workspace or capacity, or a different tenant? 

The internal service error doesn't give us much to go on, so my first recommendation would be to open a ticket with Microsoft as they can use that request ID and get more backend details for what happened. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[rohit1991]

Hi @ritika_ritika 

This issue usually happens when the semantic model migrated from Power BI Service to Microsoft Fabric still points to old connections or has missing credentials.

Could you please try below steps:

1. Rebind the dataset

   • Go to Fabric Workspace >> Semantic Models.

   • Open the dataset and reconnect it to the correct Lakehouse or Warehouse instead of the old Power BI source.

2. Re-enter credentials

   • Go to Workspace >> Data Source Credentials and sign in again for each source.

   • Credentials don’t automatically migrate from Power BI Service.

3. Check refresh mode

   • Ensure the dataset is using the right mode (Direct Lake or Import) and that the workspace and Lakehouse are in the same region.

4. Retry after a few minutes

   • The error “Internal service error, transient issue” can be temporary. Wait 15–30 min and refresh again.

5. If still failing:

   • Download the .pbix >> open in Power BI Desktop >> republish to your Fabric workspace to re-establish the connection.

[ritika_ritika]

I have tried entering the credentials again, but no luck, data source is connected to sql server.

[rohit1991 · Accepted solution]

Hi @ritika_ritika 

If re-entering credentials didn’t work, the issue is likely with the SQL Server gateway connection. Could you please try below steps:

1. Check Gateway – Go to Fabric Workspace › Manage Gateways and ensure a standard gateway is online and mapped to your SQL Server.

2. Re-map Connection – In Semantic Model › Settings › Gateway connection, pick the correct gateway + data source and refresh.

3. Network Access – Confirm SQL Server firewall allows Fabric/Gateway IPs (port 1433).

4. Authentication – Make sure the auth method (Windows/Basic/OAuth) matches what’s used in Desktop.

5. Re-publish if needed – Open the .pbix in Power BI Desktop >> refresh >> publish again to Fabric.