Forum Discussion
Data Gateway Personal Mode | Failed to Update Data Source Credentials | Status Code 400
On a Windows Server you should set up the Enterprise/Standard gateway, not the Personal Gateway.
Check your Proxy settings and make sure the gateway can successfully communicate with the Azure backend.
This has been resolved - It was actually a Network Issue pertains to NAT Loopback.
The network I have been working on does not support NAT Loopback - Data Gateway and SQL Server was installed on same network servers and I have been trying to connect the Data Gateway with SQL Server using Public IP rather than local IP - As I mentioned NAT Loopback was not enabled therefore Data Gateway was not able to access the SQL Server with Public IP. When it was setup using Local IP, it worked
Moreover, It is working with Personal Gateway too
These two settings should not have an impact.
Do you have the option of uninstalling and reinstalling the gateway software? You would choose the "Recover a gateway" option when you launch the admin tool. This is also a great opportunity to test your recovery key.
Tried uninstalling and installing the gateway several times - tried recovering the existing gateway and it was successful but still the same error occurs everytime on Power BI Service
In logs of data gateway there is a file FailedFileNames.txt
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\GatewayErrors20220916.000000000.log,
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\GatewayInfo20220916.000000000.log,
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\GatewayNetwork20220916.000000000.log,
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\SapAdapter20220916.000000000.log,
C:\Users\chms03\AppData\Local\Microsoft\On-premises data gateway\GatewayConfigurator20220916.000000000.log
Opening the first file GatewayErrors20220916.000000000.log
I can see this error
" A network-related or instance-specific error occurred.."
This has been resolved - It was actually a Network Issue pertains to NAT Loopback.
The network I have been working on does not support NAT Loopback - Data Gateway and SQL Server was installed on same network servers and I have been trying to connect the Data Gateway with SQL Server using Public IP rather than local IP - As I mentioned NAT Loopback was not enabled therefore Data Gateway was not able to access the SQL Server with Public IP. When it was setup using Local IP, it worked
Moreover, It is working with Personal Gateway too