cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BegeNCSU
Advocate II
Advocate II

Intermittent Error on Populate a Microsoft Word Template

I've built this flow several months ago that has been working reliably for most users until this morning. The flow is triggered from a PowerApps which then executes a stored procedure in SQL and then takes that data and populates a Word Template (there's a lot more going on there but that's the short version). It's at this step where I get the error message:

{
  "status"400,
  "message""There was an error accessing the file. Please try again or select a different file.\r\nclientRequestId: aa5c4803-1e45-444a-bd98-6cdd599a95e9",
  "error": {
    "message""There was an error accessing the file. Please try again or select a different file."
  },
  "source""wordonlinebusiness-wus.azconn-wus-01.p.azurewebsites.net"
}
 
What's strange is that there are a few users that are not admins but are able to run the flow without any issues. And the users that are having issues were able to run this same process as recently as last week.
 
Could this be tied to a user setting? Perhaps something related to MFA?
EDIT: Another variation I'm seeing in on a different step where the output of the Populate a Word Template is used to Create a File in SharePoint. On that step, the error message is as follows:
{
  "status"401,
  "message""Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and sharepointonline is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: sharepointonlinecertificatev2. Correlation Id=7349c940-694e-48a5-88ea-a137fc06868e, UTC TimeStamp=11/29/2021 8:02:00 PM, Error: Failed to acquire token from AAD: {\"error\":\"interaction_required\",\"error_description\":\"AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '00000003-0000-0000-c000-000000000000'.\\r\\nTrace ID: d26d294f-0960-4c5a-b202-b3684c8b9d01\\r\\nCorrelation ID: 2b5ce48f-2b49-418b-b3ce-6c48496f9b60\\r\\nTimestamp: 2021-11-29 20:02:00Z\",\"error_codes\":[50076],\"timestamp\":\"2021-11-29 20:02:00Z\",\"trace_id\":\"d26d294f-0960-4c5a-b202-b3684c8b9d01\",\"correlation_id\":\"2b5ce48f-2b49-418b-b3ce-6c48496f9b60\",\"error_uri\":\"https://login.windows.net/error?code=50076\",\"suberror\":\"basic_action\"}']"
}
 
1 ACCEPTED SOLUTION

Accepted Solutions
BegeNCSU
Advocate II
Advocate II

Thank you @v-bofeng-msft  for your help. I'm not able to use the Run Only Users as this is triggered by a PowerApp button. Through some more testing on our end we discovered it was related to a recent change in our Multi Factor Authentication (MFA) which explains why it was only affecting some of the users. As the token expires and they are forced to reauthenticate, users are now able to run the process without issue.

 

For testing purposes in case others run across this issue, having the user try to open the PowerApp and run the flow while in private/incognito mode let us narrow down that the issue had to deal with MFA.

View solution in original post

2 REPLIES 2
v-bofeng-msft
Community Support
Community Support

Hi @BegeNCSU :

4XX errors are usually due to authorization issues, I have two solutions for your reference:

Solution1:Share the template file with your users.

Solution2:Let users use your credentials to use this action.For example:

1\my flow

vbofengmsft_0-1638411723872.png

2\Add all users as run-only users

vbofengmsft_1-1638411761875.png

vbofengmsft_2-1638411813587.png

All users will use designated credentials to access Word Online

In addition ,if the problem can not be solved,please consider creating a support ticket.

Best Regards,

Bof

 

BegeNCSU
Advocate II
Advocate II

Thank you @v-bofeng-msft  for your help. I'm not able to use the Run Only Users as this is triggered by a PowerApp button. Through some more testing on our end we discovered it was related to a recent change in our Multi Factor Authentication (MFA) which explains why it was only affecting some of the users. As the token expires and they are forced to reauthenticate, users are now able to run the process without issue.

 

For testing purposes in case others run across this issue, having the user try to open the PowerApp and run the flow while in private/incognito mode let us narrow down that the issue had to deal with MFA.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Users online (2,270)