"This app is not authorized to access this service. Try reopening the app" Error started suddenly

(0) Share

Report

Posted on by AllanMartins

106

Hi all,

We have a PowerApp (Flow/Sharepoint/SQL) running for over 2 months, no problems, but today, for no reason, a Flow is triggered from the PowerApp, the following message is displayed:

The service returned an error: SQL-Insert!Run: This app is not authorized to access this service. Try reopening the app and ensure all connections have been resolved - .

As SQL-Insert is the name for the Flow which is basically:

PowerApp (Trigger) -> Compose ("@formatDateTime(utcnow(), 'g')") -> SQL Insert (ComposeResult, UserName from PowerApp)

(1 trigger, 2 simple steps)

On-Prem gateway services has been restarted, all working without problems. Also, I did checked the permissions on:

Gateway

Connection/Service

PowerApp

And it is set for all corporate users to "Use" - nothing changed from the past month...

Nothing was changed, I tried recreating the Flow, reassigning its permission to the flow, and even, removing and adding all permissions to all services again... no results... any idea?

Categories:

General topics

All responses (5)

Answers (1)

Sort by

AllanMartins 106 on at

Like
a
(0)

Report
Copy link

Link copied!

Here is an update: I have managed to move all data from the SQL to a Sharepoint List, so I could manage it without the Flow, but part of the process is another Flow that sends "Approval Emails", and now that the Data problem is solved, I receive the alert for the Email Flow. I have added the permission to all users to use all the connections, but it simply doesnt work.... any idea? Was there any change from yesterday to today?

thank you,
v-yamao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi AllanMartins,

Are you still having the issue on your side?

I create a flow according to your description, the flow is configured looks like below. When I click the button to run the flow, the flow runs succeed.

I am not sure if this is a temporary issue. Please try it on your side and if you are still having this issue, please feel free reply.

Best regards,

Mabel Mao
Verified answer

AllanMartins 106 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @v-yamao-msft, I tried that and the problem persists.

I have recreated the connection to all the services, and the problem happens the same way.

We were able to workaround this problem by:
- saving the already created App to my computer (local)
- creating a new user account;
- assign a PowerApps/Flow license;
- reconnect to all services;
- open the App from the computer, but using the new account
- recreate all the connections - just like I already tried, but using that same (old) account
- Save and Publish the App

Ta-da!

It worked.

Is there a way I can pull out logs from the PowerApps/Services to troubleshoot?
v-yamao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi AllanMartins,

Thanks for sharing with us the workaround, and I am glad to hear that the workaround works for you.

It seems that we don’t have a way to pull out logs from the PowerApps. I guess that you could consider to use Fiddler Trace to monitor the actions.

Best regards,
Mabel Mao
Community Power Pla... Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

@AllanMartins wrote:

Hi @v-yamao-msft, I tried that and the problem persists.

I have recreated the connection to all the services, and the problem happens the same way.

We were able to workaround this problem by:
- saving the already created App to my computer (local)
- creating a new user account;
- assign a PowerApps/Flow license;
- reconnect to all services;
- open the App from the computer, but using the new account
- recreate all the connections - just like I already tried, but using that same (old) account
- Save and Publish the App

Ta-da!

It worked.

Is there a way I can pull out logs from the PowerApps/Services to troubleshoot?

I was encountering this very same app not authorized error however got it solved using your method. Thank you so much for the solution @AllanMartins. I appreciate it 🙂