Forum Discussion
On-premises data gateway-Network Request Returned Unexpected Error-Configuration client returned nul
Many thanks for sharing Ibendlin! I will follow-up on the solution we will have used to solve our situation.
A quick follow-up on our situation. We opened a ticket with Microsoft and last Thursday, two technicians spent an hour reviewing the server config, network access and grabbibg our logs file for further analysis. No solution found, the gateway can't be configure anymore on that server. If Microsoft finds a solution, I will update this thread.
Meanwhile, we configure a new gateway on a new vm and did the takeover. Works flawlessly:
https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-migrate
Important lesson learned from our problem is that we will never have a single gateway server from now on. Always have at least two in a cluster, as described in lbendlin troubleshooting guide:
"A single gateway machine poses a risk for your operations. It can become inaccessible on the network, it can lock up, or it can be powered down (especially if you chose to install the gateway on your personal laptop).
A much better alternative is to create a cluster of gateway member that act as one gateway"