We experience instability on our Power BI Enterprise Gateways. Our users/ customers are reporting frequently refresh errors in powerBI reports which we have shared with them.
99% of our reports connect live to SSAS tabulars on premise.
Our gateways are 'not ready to go' then, they also display a error message:
Not all gateway instance within this cluster are connected. Please find more details below about specific errors for each gateway instance.
Gateway on endpoint '<ii>sb://wabi-north-europe-relay36.servicebus.windows.net/aa123dd1-1234-1234-be12-e123b12345a1/</ii>' is unreachable. (id has been edited by me, dont know if sharing the original one can cause security issues)
What does this mean? Is it our installed, fully updated and running gatewaysoftware which can not connect to the powerbi service?
Is the gateway software not able to connect to the on premisse ssas tabulars? Or both or something else?
Hope you can provide me with some more info.
Kind regards,
Detlev
HI @detlev,
According to your error message, it seems like your gateway is offline, please check your device who host gateway client and gateway service if they are not running.
Regards,
Xiaoxin Sheng
Gateway service is running. But restarting it solves the issue temporarily. It might be a netwerk glitch which causes the running services not be able to connect to the powerBI service and doesn't reconnect for what ever reason.
I was seeing this same issue at a specific time in my environment. This same issue was occurring at the same time every day and it turned out to be our firewall was scheduled to reboot at this same time during the day.
@detlev, are the times of failure the same time every day? or repeatable? Do you notice a patern? This might help to identify the cause. I also setup a 3rd party monitor that runs every minute to check the service is running so I will get text message notification if the service is down. Of course in my case the service was always running.
I kind of think it happens after a "faulty" restart of the windows gatewayservice. Sometimes after a server reboot , sometimes after a scheduled restart of the service. After those moments the windows service seems to have started and runs fine. But the connection between on prem sources and the powerbi service is instabile, resulting in end user refresh errors and gateway datasource errors in de gateway interface.
I extracted 5 different types of errors in the last few weeks on different moments of the day. Perhaps related. Perhaps not.
Does any one have a gateway error message bible to explain these and find causes?
A)
1A7C6F2D [DM.GatewayCore] ServiceEndpoint Connection status: Offline, LastError: 'System.ServiceModel.CommunicationException: The connection to the connect service was lost. ---> Microsoft.ServiceBus.ConnectionLostException: The connection to the connect service was lost.
B)
4412CF75 [DM.GatewayCore] ServiceEndpoint Connection status: Offline, LastError: 'Microsoft.ServiceBus.AuthorizationFailedException: Generic: InvalidSignature: The token has an invalid signature. ---> Microsoft.ServiceBus.Messaging.Amqp.AmqpException: InvalidSignature: The token has an invalid signature.
C)
67D6C462 [DM.GatewayCore] ServiceEndpoint Connection status: Offline, LastError: 'System.TimeoutException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
D)
6A0EB925 [DM.GatewayCore] ServiceEndpoint Connection status: Offline, LastError: 'System.ServiceModel.EndpointNotFoundException: No such host is known ---> System.Net.Sockets.SocketException: No such host is known
E)
116B0F83 [DM.GatewayCore] ServiceEndpoint Connection status: Offline, LastError: 'System.ServiceModel.CommunicationException: No such host is known ---> System.IO.IOException: No such host is known ---> System.Net.Sockets.SocketException: No such host is known
Hi @detlev,
I think you might want to look further into the logs to find more information what is acutally going on in your scenario describe in the post.
You can find more detailed information about your issue from the details in the link below. I would suggest looking into the Gateway logs for further details.
Troubleshooting the on-premises data gateway
Hope this is a good starting point!
I read it before posting my issue . 😉 No answers on that page.
Join us for a free, hands-on Microsoft workshop led by women trainers for women where you will learn how to build a Dashboard in a Day!