Forum Discussion
Data Gateway Personal Mode | Failed to Update Data Source Credentials | Status Code 400
- 4 years ago
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.
- Anonymous3 years ago
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
Standard Data Gateway installed and is up and running on my Power BI Service
But still I am unable to update my database crendentials and getting below error
Please note that
- SQL Server is on Port 8004
- Data Gateway is configured using official domain Id which requires MFA for logins
- lbendlin3 years agoSuper User
Data Gateway is configured using official domain Idwhat made you choose that? Using the default service login is the safest and most robust option.
- Anonymous3 years agoNot applicable
I cant find any option to configure Standard Data Gateway other than email id
- lbendlin3 years agoSuper User
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?