Published Dashboard not showing visuals when measures are applied

[JackWPT]

Hi Everyone,

I have a published dashboard that is loading my visuals except for the Tables that have measures applied to them. The error is posted below.

             Underlying Error: OnPremiseServiceException
             Activity ID: 71221d6a-2f84-423a-b6f3-dcf66b6ab121
             Correlation ID: 6b4d7989-7372-e5a3-970f-4ea7ad94bd2b
             Request ID: 2c1d25c2-623c-42ca-bf15-1bffbea04dc2
             Time: Tue Oct 07 2025 18:09:00 GMT-0500 (Central Daylight Time)
             Service version: 13.0.26816.31
             Client version: 2509.5.26176-train
             Cluster URI: https://wabi-west-us-d-primary-redirect.analysis.windows.net/

My semantic model is importing two excel files from SharePoint and is also Direct Queried into another semantic model that uses a standard gateway to connect to an SQL server. For context, I originally imported data from the SQL server straight into my main semantic model through a standard gateway, and all tables worked perfectly; but the automatic refresh was failing and moving the SQL data into a seperate sematic model was a work around.

I'm aware this is a very niche issue, but any help is welcome!

[v-nmadadi-msft]

Hi @JackWPT 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @JackWPT 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft]

Hi @JackWPT  ,
Thanks for reaching out to the Microsoft fabric community forum.

Please re verify your gateway configuration, go to Power BI Service -> Manage Connections and Gateways and ensure that the gateway used by your secondary semantic model (the one connected to SQL Server) is online and shows a green status. Check that the data source mapping exactly matches the server and database names used in your SQL connection string, as even small differences (like spacing or case) can cause failures. Also, confirm that the user credentials are correct by re-entering them and testing the connection. If the test connection fails, resolve the gateway setup issue first, as the problem will likely lie there rather than in your main model.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[tayloramy · Accepted solution]

Hi @JackWPT,

OnPremiseServiceException in the Service almost always points to a gateway path or permissions issue rather than a DAX/visual problem. In your setup, visuals that don’t hit the chained DirectQuery model render, but any table that evaluates a measure likely triggers a query that traverses the downstream semantic model -> its on-prem SQL via the gateway, and that’s where it fails.

Why measures fail but “plain” tables work:

In composite models, adding a measure often forces a query to the DirectQuery source (your chained dataset), which then fans out to the on-prem SQL through the gateway. Pure imported columns (from SharePoint Excel) can render without touching the gateway. Background: DirectQuery fundamentals & limitations, Composite models behavior.

Troubleshooting steps:

1. Prove the downstream model works by itself. Open a new report on the separate semantic model (the one that connects to SQL via the standard gateway) and interact with visuals in the Service. If anything fails there, fix gateway/credentials first. Gateway issues & mapping checks: Troubleshoot on-premises data gateways and the general gateway guide: Gateway troubleshooting.
2. Confirm tenant/admin settings for DQ-over-models. Make sure “Allow DirectQuery connections to Power BI semantic models/AAS” is enabled in Tenant settings and your capacity has XMLA endpoint enabled (Read or Read/Write): Composite models, Tenant setting.
3. Check permissions to the downstream semantic model. The viewer of your top report (and the account used by the report/app) must have Build permission on the downstream model: Build permission.
4. Re-enter data source credentials (all hops). In the Service, go to the downstream model’s Gateway connection > Data source credentials and re-enter/validate the SQL credentials. Ensure server/database values in the gateway data source exactly match the model. Mismatches (IP vs hostname, etc.) break binding: Gateway binding tips.
5. Align privacy levels (don’t rely on “Ignore Privacy” in Desktop-it doesn’t exist in Service). If your Desktop file used “Always ignore privacy level settings,” re-set appropriate privacy levels, republish, and update creds in Service: Privacy setting caveat.

Hope this helps!

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