error message

[esmat]

When I tried to refresh my report after using a semanitic model I got the following error message 

"Underlying Error: OnPremiseServiceException
Activity ID: d7667345-8896-4d63-9f79-98de321e7dbb
Correlation ID: 323c54ce-1aba-ba9c-34c1-8f685eae1aee
Request ID: c6e69a6a-a81d-9d42-6d5c-045616d838d6
Time: Fri Apr 10 2026 20:09:37 GMT+0200 (Eastern European Standard Time)
Service version: 13.0.28090.50
Client version: 2603.5.28661-train
Cluster URI: https://wabi-us-east2-redirect.analysis.windows.net/"

how to fix it?

[v-pnaroju-msft]

Hi esmat,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @collinq, @lbendlin, @krishnakanth240 and @Nasif_Azam for your responses.

Hi esmat,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @collinq, @lbendlin, @krishnakanth240 and @Nasif_Azam to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[Nasif_Azam]

Hey @esmat,

That OnPremiseServiceException is not actually a semantic model problem. it is Power BI Service telling you it could not reach your data source through the On-Premises Data Gateway. The Activity/Correlation/Request IDs are only useful if you end up opening a Microsoft support ticket, so do not spend time on them yet. Try the following fixes:

1. Is the gateway actually online?

Go to Power BI Service → Settings → Manage connections and gateways. Find your gateway cluster and check the status. If it shows offline, RDP into the gateway host and confirm the "On-premises data gateway service" Windows service is running.

2. Is the gateway version still supported?

Microsoft only supports the last 6 monthly releases. The latest is the March 2026 release (version 3000.310). Anything older than September/October 2025 is out of support and Microsoft will actively block refreshes on it. Check Gateway app → About for the version, and if it is old, update it.

3. Are the data source credentials still valid?

In the semantic model's Settings → Data source credentials, click Edit credentials for each source and re-enter them even if they look fine. Service account password rotations, expired OAuth tokens, and SPNs that fell out of sync are extremely common triggers. 

4. Is the semantic model bound to the right gateway, and does every source have a matching data source definition?

In the model's Settings → Gateway and cloud connections, make sure a gateway is selected (not just "personal") and that every on-prem source in the model has a green checkmark next to a data source entry on that gateway. If you added a new table/source recently in Desktop, you may have published a model that references a source the gateway does not know about yet that throws this exact error.

5. If you mash up on-prem + cloud sources, is "Allow the user's cloud data sources to refresh through this gateway cluster" turned ON?

Manage gateways → your cluster → Settings. This one bites people after they add a cloud source (SharePoint, Azure SQL, etc.) into what used to be an on-prem-only model.

Best Regards,
Nasif Azam

[krishnakanth240]

Hi @esmat 

Error during refresh typically indicates a connectivity issue between the Power BI Service and on-premises data source. Since the semantic model is in the cloud and needs to reach on-premises data, start by checking the gateway is online and running the latest version on its host machine.
Navigate to the semantic model settings in Power BI Service, go to Gateway connection and confirm the correct gateway is selected and the data source credentials are still valid.
Also, ensure user account has at least Contributor access to the workspace and is listed as a user for the data source within the gateway configuration.
If working with a composite model that uses Direct Query to other semantic models then make sure all datasets are included in the identity scope.

[lbendlin]

identity issue?

Solved: Underlying Error: OnPremiseServiceException - Microsoft Fabric Community

[collinq]

Hi @esmat ,

Since this is indicating a permissions error please confirm that the userid you are signed into is the correct userid for the tenant that you are in?  And, if this is a gateway connection you should check your settings there - look at the settings and then the Gateway connection and make sure the right gateway is selected.  Also, make sure that there is no "Data Credentials" issue while you are in settings.

Also, is there RLS set and you are not in the right group?  In the Workspace, are you more than a "Viewer" access?

Other item could be that you are in an older version of Desktop and the Service is a new version.  You should update your desktop as well to this month's version and then publish again and see if that resolves this issue.