Answered

Flow not connecting to server share?

(0) Share

Report

Posted on by Community Power Pla...

Hello all,

I have data gateway installed on server 'X'. Trying to copy files from share on server 'Y' to SP 365. I'm running the flow from my laptop. Error seems to indicate it cannot access the server files, hoping someone can help as I'm new to this and unsure what my next step should be.

Here is my File System connector (which does reference the data gateway I have installed):

Here is the flow. Click on the file picker icon returns the Error shown. Normal or not?

Here is the result of my test run:

The full error is below:

{
"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: 56430166-6d05-495e-9c94-7dce2fdd13c7",
"source": "filesystem-eus2.azconn-eus2.p.azurewebsites.net"
}

Would much appreciate any assistance.

Thanks,

Jeff

All responses (2)

Answers (1)

Verified answer

v-yamao-msft on at

Like (0)

Report

Re: Flow not connecting to server share?

Hi @Anonymous ,

Please make sure you created the connection to File system successfully.

The following doc could be a reference for you:

https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-using-file-connector

Best regards,

Mabel
Brad_Groux 4,556 on at

Like (0)

Report
Re: Flow not connecting to server share?

This is almost certainly a routing or port issue. Please review the Troubleshooting the On-premises data gateway documentation, and also review the Port requirements and the Firewall and proxy documentation and insure that your proxy or firewall allows access over those ports.
Please review both hardware and software firewalls, including the Windows Firewall on the server. Finally, the Tools for troubleshooting section covers collecting logs and Fiddler tracing.
Windows Server's services use different ports than Power BI. Power BI works specifically over port 80 or port 443, and if you'll notice the data gateway port requirements are far more than port 80 and 443:
*.servicebus.windows.net 5671-5672 Used for Advanced Message Queuing Protocol (AMQP). *.servicebus.windows.net 443, 9350-9354 Used by listeners on Service Bus Relay over TCP (requires 443 for access control token acquisition).
For most firewalls, port 80 and 443 are open because they are the HTTP/S ports, however the ports listed above would not be open by default.
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!