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

[SachinG31]

Hello All,

I am trying to connect file system Action using my credentials since i have access to this folder. but every time i run flow it show below error

"The credentials for this connection do not have access to '', please try using a different location or account." . I have checked my credentials even re created the flow. but nothing is working.

 i tried everything , Checking domain username, delete and creating new connection , Even i tried with Admin Account but the error is same. 

few days back it was working fine , then i shifted my gateway from my local computer to server after that it stopped. Please advise below is my flow.

[ekarim2020 · Accepted solution]

I've not used the File System connector or the on-premise gateway before, but this looks like an authentication issue. After setting up the on-premise data gateway on my local computer I created a simple flow to list files on my local computer (C:\FileSystemConnector).  The connection settings I would need to use will be my organisation's AD user login credentials (domain\username) - if this was an AD domain joined computer - and I was logged on with my AD username and password. However, I am using the on-premise data gateway on my personal computer which is not AD joined - so I used my local credentials for the File System connection.

I used the whoami command at the command prompt to get the local computer name and logged in username. I put those details into the connection settings:

If you login to your computer using a Microsoft account (outlook.com, live.com etc) you can also enter those details. See also: Microsoft Power Automate: Invalid Connection Credentials

If the credentials are incorrect, I see:

Hope this helps.

Ellis

[SachinG31 · Accepted solution]

hello @ekarim2020 , First of all i would really appreciate your efforts and time you took to beautifully explained this issue , As per your test and explanation i tried something ,  and that worked for me finally after struggling one week.

I have create a new gateway on my local system from where i am accessing the folder , so i believe if you are using file system connection you can only use the gateway which is installed in your local system , i dont know why this dependency is only on file system connection , but that's how it worked for me.

Thank you so much again for the help and contribution to the community🙂  

[swami_natha]

Could you please help in this scenario. Action 'List of files in a folder' is working for Local drive path, but not working in Share drive network folder. Getting error as 'The credentials for this connection do not have access to '/', please try using a different location or account.'
In above specified action, Root folder is given as for e.g. '\\abcdef123.emea.corp.net\PDFdocuments\'
Folder is updated as '/'
Credentials used to connect to shared network drive are correct as I manually tried it. Same credentials updated for connection. On-premises gateway is established properly. Unable to find any solution so far.
Could you please check what could be the issue?

[Veblitz]

Hi All,

I installed onpremise gateway and it's ready for online but I don't know it's not displaying in Power Automate flow when I try to create a connection under file transfer trigger.

Kindly help.

[Tobee]

hi

I had the same problems with the 'Create File' flow form the 'File System' connectors (" no access" and "the flow creating a wrong path with double \\ and / instead of single \). No 'work-around' worked.

In my case, the problem was that the user account on the PC onto which I wanted to copy files from Sharepoint did not have access rights to a folder created and used by the gateway. The access was protected by Windows as default. I had to actively open that folder:

C:\Windows\ServiceProfiles\PBIEgwService

Then it worked.

Of course all the rest that is commented here needs to be correct as well (user credetnials incl domain etc).

enjoy!

[Lerelle_B]

I had the same problem when my password expired and had to be reset.

What I had to do was go to my connections and update the Username (Domain\Username) and the new password.

Even though the connection said it was connected prior to updating with the new password it wasn't.