A single user is stuck on "your app needs permission to use : SQLserver"

[a-anscac]

Hi all,

I have a PowerApp that is used by many colleagues and works fine, except for one single person who is unable to access it.

He is stuck at the screen that asks to grant permissions ("your app needs permission to use : SQLserver") and the Allow button is greyed out (screenshot below).

He already tried to:

• log out and log in
• use other browsers
• use powerapps mobile

Any advice? Is there any internal support I can reach out to?

Thanks!

[yashag2255]

Hi @a-anscac 

Can you please confirm that the user has access to SQL server? The user must have appropriate roles to establish this connection and retrieve/update data on the data source. 

If you would like to contact the support team, you can raise a ticket on: https://admin.powerplatform.microsoft.com/support

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[timl]

Hi @a-anscac 

If your app uses an on-premise SQL Server database, a likely cause of this problem is that the user doesn't hasn't been assigned a P1/P2 license.

To diagnose whether or not this is a licensing problem, I would click the cog icon > Plans menu item for a user that is able to access the database. Next, ask the user that experiences the problem to do the same. Is there any difference between the plans that are assigned to the user?

[a-anscac]

Hi @timl,

I checked the plans. Both me, another user who can access the app and the user who cannot are seeing the same plans that also appear in your screenshot:

- PowerApps for Office365

- PowerApps Trial

The app connects to a database that is hosted on Azure. The app sharing is set to a group, and the Data Permissions shows: SQL Server - Implicitly Shared.

I also made sure that the user is into that group/distribution list.

Any other advice?

[v-yutliu-msft]

Hi @a-anscac ,

I suggest you check your SQL whether allow users to write/read.

What's more, not only you need to share the app, but also they need to recreate connection with SQL.

You could check here to see whether your connection is share successfully:

Best regards,

[a-anscac]

When I open the connections page it gets stuck on loading and the console is full of errors. I tried in Edge and Chrome.

Do you know if tech support can check this kind of things for me? 

[timl]

Hi @a-anscac 

I would recommend that you raise a support issue via the 'create support ticket' button at the bottom of this page.

https://powerapps.microsoft.com/en-us/support/

They should be able to see all your license details and be able to more easily find the cause of the problem.

[GregCoopman]

Yes, I struggled with this error all last week and could not publish, and therefore could not Export the latest changes to the app.  Prior to the error I probably Published 10 times over a 2 week span of constant developing on the app.  Anyways, after racking my brain and searching for answers with no avail, I realized that the problem started after I started using Power Automate Flows, but it was not the flows that caused the problem, it was that I changed Environments on my PowerApp to use the same environment as the Flow environment and that is when the problems seem to occur.  When I went back to original environment that I initially created my SQL Connections with for the app, the "Permission" errors went away. This is my experience, I then re-added my changes to the last good saved app backup files from when I worked in the good environment, and things are working fine now.  I do not understand exactly the details of why, but that is how I was able to get around the problem and I hope this can help someone out there,  because it took me at least several days to figure this out.

[BHS_KI]

I got the same trouble with Microsoft 😁 - now I can smile again. But took me many days. 

Reason for my problem was a conversation from not-environment to environment. I think Microsoft could not really handle the connector already established in the app. I have deleted any connections and removed data in the app. Afterwards reconnected again. And finally it worked.