File System not connecting

[Anonymous]

Hi,

I'm trying to create a flow to save specific email attachments into a network drive, but can't seem to get 'File System' to successfully connect to a file path.

I've set up a 'File System' connection, and put "[domain]\[user]" as my username, along with password and gateway.   I've verified the gateway connects successfully in the on-premises app.  However, every time I try to navigate the folder path in File System, it throws the following error:

"The dynamic invocation request failed with error: { "status": 403, "message": "The credentials for this connection do not have access to '', please try using a different location or account.\r\nclientRequestId: 79ce29a8-84e1-410a-885e-27e6-500f7b78", "error": { "message": "The credentials for this connection do not have access to '', please try using a different location or account." }, "source": "filesystem-eus.azconn-eus-01.p.azurewebsites.net" }"

I've tried all iterations of user and domain (which seems to be a common issue), and tried using a local drive instead of a network drive, but all result in the same error.  Any ideas on how best to debug next?

Really appreciate any help!

Best,

Chris

[v-litu-msft]

Hi @Anonymous,

Are you input the correct domain/username?

You could find your computer name via reading this document:

How to Find Your Computer Name | Information Technology | Drexel University

If the domain is "Atest.com", the domain put in the file system connection should be "Atest".

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi Lin Tu,

Thank you for the fast response! 

I can confirm I've tried this, also with many other varieties (user name vs machine name, "\" vs. "/", domain with and without ".org") but still get an error.

Are there other checks I can perform to verify compatibility?

Best,

Chris

[Kagantuya]

Hello Lin Tu,

I encountered status error 403 these days. In my case, it was because the account which I used to create the flow was not the same as the one I register the gateway. If this is the case, you have to reinstall the gateway and register the gateway using your flow account or vise versa.

Hope this would help

[SG_10]

If you are using any organization ID so try to give full ID with .com

example:   abc.com\username for me it worked.

[saikishoretayi]

Exact same error, we are testing with some test .txt file.

{

  "status": 403,

  "message": "The credentials for this connection do not have access to 'test.txt', please try using a different location or account.\r\nclientRequestId: 2ce95e0c-5ea5-4533-9df6-bcdddadcc51a",

  "error": {

    "message": "The credentials for this connection do not have access to 'test.txt', please try using a different location or account."

  },

  "source": "filesystem-cus.azconn-cus-001.p.azurewebsites.net"

}

[Wanjalanco]

Did anyone ever have an answer to this question? It is 2023, and I am having exactly the issue.

[Luckiestneda]

I had the same issue,

Try this:

Create a new connection for the file system. Remember when you are using the credentials for the connection use Domain\Username not any email.

It worked for me

[MuYongzhi]

Try to add your account to [Remote Desktop Users] group, this works for my case