Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
We sometimes get the error "Your data gateway is offline or couldn't be reached.".
The gateway is installed as a service on a A3 Azure server. (In the past, we tried A0 but got the error "cannot connect to the mashup datasource".
The data is also stored on an Azure Server (SQL database).
Remark: Some other reports also connect through the same gateway to "SSAS Cubes" (SQL Server Analysis Services Database")
However, this should have nothing to do with it as the gateway service should be able to handle both connections. (https://powerbi.microsoft.com/en-us/gateway/)
Any ideas?
Still sometimes the "Mashup data source" error.
Any ideas?
Hi @gillesaugustus,
Actually, your issue may caused by many factors such as network environment as I mentioned before and the status of the the gateway.
If you still need help, I'll suggest you create a support ticket to get the further help if you have pro license.
Best Regards,
Cherry
Hi @gillesaugustus,
Actually, the gateway runs on the computer where you install it, so ensure that you install on a computer that is always on. For better performance and reliability, we recommend that the computer is on a wired network, rather than a wireless one.
For your sceanrio, are you sure your server is always online? Please have a check what is status of your A3 Azure server when the gateway offline.
Best Regards,
Cherry
Hi @v-piga-msft,
The computer on which the gateway service is installed was on at the time of the failed refresh. In fact, the pc is always running.
This morning a new error appeared "Invalid connection credentials":
Report refreshed at 7h00:
Report refreshed at 7h30:
Report refreshed at 8h00:
Report refreshed at 8h30:
Hi @gillesaugustus,
Sometimes this issue may also be caused if the network environment is not good.
You could monitor the network or we need to export the gateway log to ananlyze the specific reason.
In addition, you also could update the credential and try again.
Best Regards,
Cherry
We have found the "Invalid credentials" issue.
I will monitor the next days for the original issue.
Kr.,
Gilles