Unanswered

File System through on-premise gateway to file share on non-domain computer

(0) Share

Report

Posted on by shakudu

So i've been at this for a while now but i cannot get it working.

I can access the share from my gateway PC using unc-path \\desktop\share using credentials with no pc name or workgroup in the username.

When using the connector in a flow i get the following error message:

The dynamic invocation request failed with error: { "status": 400, "message": "The requested action could not be completed. Check your request parameters to make sure the path '' exists on your file system.\r\nclientRequestId: e0e66bd3-2529-30fc-5c1f-3429a6230f12", "error": { "message": "The requested action could not be completed. Check your request parameters to make sure the path '' exists on your file system." }, "source": "filesystem-we.azconn-we-002.p.azurewebsites.net" }.

Connector is set up with the unc path and username as mentioned (using any other combination, like with desktop\user fails with an other error message than this one.

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

Pstork1 68,717 Most Valuable Professional on at

Like (0)

Report

1) Make sure you use you work or school account when registering the On-Premises Gateway

2) On the PC go to a Command Prompt and type Whoami. That will return the account you should use to create your connection through the gateway. Use Windows Auth and the UNC name of the sharedrive you are trying to list.

Using a different ID between setting up the gateway and setting up the connection is what usually causes me the issue. The gateway is installed with the Office 365 account and the connection through the gateway is created with the local account. That's what works for me.

Was this reply helpful? Yes No
shakudu 32 on at

Like (0)

Report

Gateway is installed with my work account. Whoami on the other computer with the files gives me the PC name and username that i've already used to configure the connector.

When i type username with computername (e.g. desktop\user) i get this error message instead:
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: e03348e0-24d7-4402-a2ce-40327311a458", "error": { "message": "The credentials for this connection do not have access to '', please try using a different location or account." }, "source": "filesystem-we.azconn-we-002.p.azurewebsites.net" }.

Was this reply helpful? Yes No
Pstork1 68,717 Most Valuable Professional on at

Like (0)

Report

I'm not sure what to tell you. That is the combination that works on my standalone non-domain laptop.

Was this reply helpful? Yes No