Announcements
Hello People,
All of a sudden I started to get the below error message in Powerapps editor:
But I can access the database from the Database Management studio. Any comments?
Thanks,
Omi
@omi18
If this is On-Prem SQL - For PowerApps to access SQL it must go through a Data Gateway. Check the status of that gateway.
If this is Azure SQL, check your connector in your app and see if there is an authentication issue with it. Perhaps retry entering creds into it.
I hope this is helpful for you.
Hi @RandyHayes ,
Yes, the On-Premises gate is up and running.
It's showing a new version is available - when was the last time you updated the Gateway?
We just updated the Gateway. But didn't fix the error.
Best,
Hello,
Any suggestions people? All live apps have stopped working. 🙄
Sorry for delay...wasn't on over the weekend.
Couple of questions:
1) Is this universal? Do you have other apps that use this Gateway that are experiencing the same issue? Can you create a test app that utilizes the connection and validate if it works or not?
2) Have any credentials changed on the SQL?
3) Have you explored the Gateway Manager to see if there are any issues shown for that Gateway?
@RandyHayes, No problem.
Yes, All apps using the same connector having a problem. I did a test app and it is working for a new app. Even we tried using a new connector. No luck.
Nothing is changed from the SQL side.
Yes, In gateway Manager Portal it shows: same gateway cluster is online.
So the key take-away here is that you say a new test app is working.
This indicates that the connection information for the original app is either using the wrong connector or it has a stale connector in it (this would assume cred changes though...).
Have you tried to pull the connector out of your app and add it back in? Unfortunately, this would be done by removing the datasources and adding back in.
Another little test to try...in the non-working app, try to add another datasource through your existing connection. See if that datasource exhibits the same error. If it doesn't then this points to the above remedy even more.
@RandyHayes,
I did remove the connector and while connecting back below error popped up.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 409 Super User 2026 Season 2
Mohsin Ali 328
WarrenBelz 252 Most Valuable Professional
