Forum Discussion
OnPremiseServiceException
Hi Everyone,
One of my Power BI dashboard uses direct query and rest of all other dashboards uses Import Query. After our Gateway upgrade all reports that uses the Import Query are refreshing properly but the one with the Direct Query is getting error "An exception occured due to an on premise service issue"
Can anyone confirm whether any issue with the Microsoft Gateway or anything else??
Hello PBIUser34 !
This is one of those cases where it's difficult to pinpoint the exact root cause from the error alone.
The OnPremiseServiceException is fairly generic gateway error and usually indicates issue somewhere between Power BI Service -> Gateway -> Data Source.
Since Import works but DirectQuery fails, it typically points more towards a runtime/connectivity issue(not refresh).
To narrow it down, a few useful checks:
- Are you using a gateway cluster or single node?
- Do other DirectQuery report face the same issue, or just this one?
Quick things tro try:
- If you have a cluster, switch to another gateway node
- Rebind the dataset to the gateway
- Re-enter credentials
For more troubleshooting:
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-tshoot#troubleshooting-toolsI recommend checking out the logs for more information to find the root cause through the Query Execution Logs, you can find the logs:
\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\Report or \Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\Report.
Also check the GatewayInfo.log, GatewayErrors.log, and GatewayNetwork.log.
Useful links for the logs:
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-performance
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-log-filesBest regards,
Solutions Architect · Microsoft Fabric Specialist · @Parchitect💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.
6 Replies
Hi PBIUser34
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.Hello PBIUser34 !
This is one of those cases where it's difficult to pinpoint the exact root cause from the error alone.
The OnPremiseServiceException is fairly generic gateway error and usually indicates issue somewhere between Power BI Service -> Gateway -> Data Source.
Since Import works but DirectQuery fails, it typically points more towards a runtime/connectivity issue(not refresh).
To narrow it down, a few useful checks:
- Are you using a gateway cluster or single node?
- Do other DirectQuery report face the same issue, or just this one?
Quick things tro try:
- If you have a cluster, switch to another gateway node
- Rebind the dataset to the gateway
- Re-enter credentials
For more troubleshooting:
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-tshoot#troubleshooting-toolsI recommend checking out the logs for more information to find the root cause through the Query Execution Logs, you can find the logs:
\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\Report or \Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\Report.
Also check the GatewayInfo.log, GatewayErrors.log, and GatewayNetwork.log.
Useful links for the logs:
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-performance
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-log-filesBest regards,
Solutions Architect · Microsoft Fabric Specialist · @Parchitect💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.Since Import mode reports are refreshing fine, the issue is likely specific to the DirectQuery connection. Check the gateway data source, credentials, and connection settings after the upgrade. Reviewing gateway logs should show the exact cause.
DirectQuery still hits the gateway’s data‑source mapping at runtime. Import doesn’t go through that path, so if the upgrade caused any mismatch, it shows up only on the DirectQuery side.
Gateway issue, not your report. DirectQuery hits the gateway live on every query, so the upgrade broke that path while Import only uses it at refresh.
Fix: re-enter the data source credentials in the gateway settings. Upgrades often drop them.Hi PBIUser34
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
