I have a shared application in Powerapps using 2 different SQL connections hosted by 2 different On-Premise gateways. Multiple users are using the App without issue -- everyone has the same share permissions (shared with app, gateways and connections). For both SQL Server connections, a service account is used to connect.
Only one of the users sees this error when attempting to open the App:
The user sees this error for one SQL Server but not the other. Clicking "Ask for access" sends an email to me with links that take me to the "Share" page for the connections -- but he's already in the list!
I've triple checked all permissions - they are the same as other users who are not experiencing this issue. I'm not sure what else I have control of to try to fix this issue -- what am I missing?
With a PowerApp in this particular configuration, you may encounter permission issues if new On-Premise gateways are added after the initial share gesture is performed.
The quickest thing to try is to unshare and reshare the PowerApp with the user who is having access issues. This will force the service to refresh all of the gateway and connection permissions on-demand.
Edit: After re-reading the comment thread with Reza, this may not be a foolproof fix. I think it's still worth trying, however.