Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,551 questions
Data Gateway Issue after SQL Auth Password Change
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 40%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Hilary Stoupa
26
Reputation points
I have several logic apps that use an on-prem data gateway for SQL data. They have been running without issue for a couple of years. They are set up to use SQL Authentication. We changed the password of the SQL Auth account, and now I'm getting bad gateway errors on my SQL connections.
I've tried:
- Opening the API connection and updating the credentials to the correct password - this appears to make no difference. I still get a bad gateway error
- Updating the data gateway to the latest version. This appears to make no difference.
- Creating a new connection in my logic app - when I select the data gateway and enter the correct SQL Auth credentials, I get a bad gateway error
- Changing the password for the SQL Auth user back to the prior password - this appears to make no difference.
- Connecting to the same data gateway from Power Apps. I can connect to my database successfully from Power Apps using the same data gateway.
What can / should I try next? I'm perplexed.
Azure Logic Apps
{count} votes
-
Hilary Stoupa 26 Reputation points
2023-01-03T22:57:51.523+00:00 Here's a sample error creating a new connection, in case someone can lookup the GUID from the message: Please check your account info and/or permissions and try again. Details: BadGateway More diagnostic information: x-ms-client-request-id is 'F7CA700B-AA3D-49CA-AE40-6E8B3622BF34'.
-
MayankBargali-MSFT 70,941 Reputation points Moderator2023-01-19T06:11:00.61+00:00 @Hilary Stoupa Apology for the delay and inconvenience due to this issue. Once you have updated the credential again it should refresh on the next runs. There may be a few minutes delay in case the credentials are cached but you should observe this issue post sometime. I believe the issue might have already been resolved for you but in case if it is not then please let me know. In case if you have the repro then either you can create the support ticket with us so we can review the logs at our end to know the root cause of the issue/or issue at the connector end. If you don't have the support plan then please let me know.
Sign in to comment
Sign in to answer