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
I cant find any option to configure Standard Data Gateway other than email id
Ah, sorry - that is fine (and will work with MFA). This step is not actually required for the gateway to function.
I was thinking of the gateway service (which is crucial to be running) that usually should run under the default service login.
You are getting an error 400 which might be pointing to a resource mismatch on your data source. Can you create another connection against a different SQL data source and see if you can reproduce the issue?
I tried connecting the different data base creating an entirely different report then published it but all in vain then I tried publishing it on a different workspace it didn't work
I think the error I am recieving could be related to SQL Server Browser - Please see below that SQL Server Browser is running with "Local Service", is it the right configuration for Data Gateway Connection ?
Also, I noticed that on SQL Server Folder We don't have any permission for user "PgiEgwService" - Can this be an issue
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.