Forum Discussion
On-premises data gateway-Network Request Returned Unexpected Error-Configuration client returned nul
"our sql server on which the on-premises data gateway resides"
There's your first big mistake. Gateway cluster members are extremely resource hungry. It is highly advisable not to have anything else run on that machine, especially not something like SQL server that will compete for the RAM and disk speed.
Have you considered downgrading to 68.15 for testing?
- Anonymous5 years agoNot applicable
Thanks Ibendlin,
Downgrading to the previous release did not do anything. We simply can't use the Gateway Configurator anymore. You are right about having the gateway on the same mahcine as SQL Server, the gateway is going to be installed on another vm.
What do you mean by "first big mistake"? Are you able to deduct other problems by the log? If so, please let me know so we can make sure our next install is appropriate.
Regards