On-premises data gateway update results in "The gateway is either offline or could not be reached"

[davidrothwell]

I just upgraded my on-premises data gateway to v14.16.6524.1 and it is now unreachable. It was functioning without issue before the upgrade.

The gateway is either offline or could not be reached.

Activity ID:	0f2788a1-08ed-4215-9f15-983ef90f550c
Request ID:	6ed5cfc8-4304-a531-9821-a953964fd4ec
Cluster URI:	https://wabi-west-us-redirect.analysis.windows.net
Status code:	400
Error Code:	DM_GWPipeline_Client_GatewayUnreachable
Time:	Wed Dec 13 2017 11:44:41 GMT-0800 (Pacific Standard Time)
Version:	13.0.3419.168

On the gateway itself, if gives a message that it is configured correctly but is unreachable due to local network connectivity problems. The Network status says connected ("check to see if your gateway can reach outside your network).

I can't imagine it is firewall or proxy issues as it was working fine before updating.

Has anyone else experienced this with the gateway update? Any suggestions?

Thanks

[v-yulgu-msft]

Hi @davidrothwell,

What is the status of gateway?

Have you tried to restart your gateway for a test?

Regards,

Yuliana Gu

[davidrothwell · Accepted solution]

Hi Yuliana,

I didn't get a screenshot, but where yours says "The gateway is online and ready to be used" mine said "The gateway is configured correctly but is unreachable due to local network connectivity problems."

I ended up cleaning it out and rebuilding it from scratch and it was working fine, so no further investigation is necessary for now. A colleague of mine originally set up the gateway so I wonder if there was some clash with user accounts.

Thanks

[v-yulgu-msft]

Hi @davidrothwell,

Glad to hear that you have resolved problem by yourself. Would you please kindly mark your sharing solution as an answer so that it can help others having similar concern check the problem?

Thanks,

Yuliana Gu