Operating system actions failing recently. About 50%

[martinav]

I am getting this issue about 50% of the time.  Thus, it cant be a authentication issue if it is working sometimes.  Please advise on this error.

Flow error in the Delete File action:

{

"status": 403,

"message": "The credentials for this connection do not have access to '\\\\Company.com\\Public\\Current Drawings', please try using a different location or account.\r\nclientRequestId: 1eaeece4-d042-4786-aedf-22eb953ab2a5",

"source": "filesystem-ncus.azconn-ncus.p.azurewebsites.net"

}

Session ID: 0829b69a-81d8-40b1-af3d-a549a7768b14
PowerApps 3.19043.15

This makes no sense at all.  If it works sometimes, it should work always.  This has been working for 2 months without an error.  Errors started last week, about the time the new updates to PA were released.  

[Brad_Groux]

As this is a local gateway connector the authentication issues likely lies on the system side, not the Flow side. If the authentication is failing, something on the system is probably causing it. You should look into the system logs and compare the timeframes when it is failing to see if there is a reason or correlation for it.

The authentication error you are receiving is a failure to authenticate via Active Directory, and those authentication errors can be caused by many things. Including timeout, stale tokens, bad replication, token bloat, site topology, DNS errors and more - it is up to your environment variables.  

You could also try re-installing the gateway on the system, and re-authenticating the connection to Flow. 

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!

[martinav]

I have reconnected the connections.  Also, you think this to be the case even when it works part of the time?  

This is one of about 4 things that started going awry when the last update of PA was rolled out.  I just dont see how that relates.  This was iron clad for many weeks prior to last week.  

[v-zhos-msft]

Hi @martinav ,

Could you please share a screenshot of your flow's configuration?

I think the cause of this issue is that the files are locked somrtimes when you want to delete the files.

Best Regards,

Community Support Team _ Zhongys

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[martinav]

I understand the issue regarding a "locked" file.  However, these are not files that are being edited.  Additionally, when the flow fails, I go right into the folder where it is located and delete it manually with no issue.  I have never received an error doing it manually.  Additionally, the creds on the gateway are the SAME as the creds on my PC, because its actually the exact same AD login for both.  

The delete action is one of several file system actions in this flow.  The delete action is the only one that has failed in every case.

@Brad_Groux  asked for my flow "configuration".  I'm not quite sure what he meant by that...  But, here is more of tha actions:

[Brad_Groux]

---

@martinav wrote:

@Brad_Groux  asked for my flow "configuration".  I'm not quite sure what he meant by that...  But, here is more of tha actions:

---

Thanks for the screenshot, that's what I meant - although "expanded" steps generally help as well. With that said, the Action Failed: Action failed. No dependent actions succeeded. error is usually one related to permissions. 

I realize that the credentials you are using are the same as your user credentials, but when was the last time you "refreshed" the gateway within Flow? I'd suggest refreshing the connection as the first course of action:

I know this sounds silly, but stale connector credentials are the cause of many headaches and are the easiest thing to check at the start of troubleshooting. You should also check the permissions at the folder level, and make sure that the account has full read/write permissions for that folder.

One thing that could also be an issue, is a UAC or security prompt for the folder - so if you get a UAC prompt when you delete files manually in that folder, that would likely cause the Flow delete to fail as well. UAC is usually on by default for manipulation of root and system folders. 

Finally, I'd fully verify that your environment meets all of the requirements for the Data Gateway Connector, specifically I'd review the required ports, installation and configuration documentation, and the on-premise Data Gateway Connector in-depth documentation.

To me this looks like a either a firewall/port issue, or a permissions issue.

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!

[martinav]

Thanks for the reply.  The Action Failed: Action failed. No dependent actions succeeded.  Is the result of the FS Delete action failing, thus leaving both legs (dependants) of the condition unsatisfied, thus the flow terminates.  

Not only have I refreshed the Gateway, I had my admin upgrade it.  I had no idea that was something that actually required maintenance updates, since there has never been mention of that in the forums that I have seen, nor any messages with regards to having an old version on the gateway.  It was from May 2018!  I am quite surprised because not even MS staff reccomended this as an item to check, even with many issues I've posted over the last year that include server errors that involved gateway flows and other activity.

Additionally, there are 6 prior on-prem gateway calls in this flow that work great.  Its always the delete.  

This did lead me to another theory.  It may be possible that the file is open in a PDF viewer on another user's machine.  I am wondering if that is locking the file to not allow it to be deleted.  I'm working with my admin to see if we can have permissions changed that would either allow for the forced delete, or have users unable to lock files from that directory.  They shouldnt be able to edit anything in there anyway.

I'll keep posting until I find the root cause.