Forum Discussion
Problems Refreshing on Service
- 6 years ago
Hi Anonymous
I believe below official document could be helpful:
https://docs.microsoft.com/en-us/power-bi/service-gateway-mashup-on-premises-cloud
Also, Make sure privacy levels for both cloud and on-premises data sources are set appropriately to ensure the joins are handled securely.
Could you confirm that the Gateway Server can connect to the SharePoint Folder?
Hi Gilbert,
In Gateway section i have a red x on sharepoint. so im assuming it is not connecting. Although sharpoint is showing as not connected in gateway when both data sources are not appended together, Everything refreshes without issue on service. do you know why its happening and how i can fix?
Thank you
- GilbertQ6 years ago
Super User
Hi there
What happens is when you are trying to merge 2 different data sources where one is cloud based and one is On-Prem it has to do all this via the Gateway.
So you will need to create a data source in the Power BI Service Gateway to your Sharepoint site. This will then give you the option to connect. - SidSingh6 years agoFrequent Visitor
We are also facing similar issue, in one of our projects. Dashboard was running fine since months and now the scheduled refreshes are getting failed giving same issue. It works fine if the data from 2 sources (Share-point & APIs) are not merged together in Power BI model. As soon as they are merged it refreshes successfully in Power BI desktop but fails when scheduled refreshed thru Gateways. It was working fine in past, this issue started since 18th Dec 2019. Any idea if it is because of any update in Power BI Services or Gateway versions ?
Thanks for any help around this in Advance.
- Anonymous6 years agoNot applicable
Just to update on the status of this. Still experiencing same issue. And its essential the we have this working correctly. Ticket has been created directly with mircosoft. After a few meeting with MS technical support, we could not solve the issue so log files have been provided. We are now waiting on solution. I will have to say that the MS team has been pretty responsive and eaiger to solve the issue.
Regards,