Forum Discussion
OnPremiseServiceException
- 2 months ago
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.
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-tools
I 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-files
Best 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.