Unanswered

Issues Retrieving Files from File System

(0) Share

Report

Posted on by Avery_Kirkham

I'm having an issue retrieving a PDF from an on-premises file share using the File System connector.

I've been able to get it to work on a separate file share, but for whatever reason it's failing to find the file on the N drive.

The file definitely exists in the specified location, I've confirmed the service account has access to it, the on-premises gateway is still running, and there were no issues in setting up the connection used to access it.

Any suggestions as to a part of the process I might have missed?

The specific error can be seen below:

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (0)

yashkamdar 1,044 on at

Like (0)

Report

Hello Team,

Can you please share a screenshot of how exactly you are trying to fetch the PDF file.

Honestly in most cases it is a glitch and by removing the connection and creating a fresh connection it would work (in most cases not all).

That being said your error says "Check the request parameters to make sure the path exists" which means that the request to fetch the file is not correct or getting corrupted.

So three things to try here-

1. Create a fresh connection (same old steps like establishing the gateway connection by logging in with the credentials) and create a simple brand new flow to check if you can retrieve the PDF.

2. Share across a screenshot of the action that you have configured for fetching the file which might give me additional insights just in case something is not correctly configured.

3. Add another file to the exact same drive on the file share and see if that file is getting fetched, just to isolate the issue that this is happening with only that specific PDF or all other files.

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!

Was this reply helpful? Yes No
Avery_Kirkham 2 on at

Like (0)

Report

Hey, thanks for the response, unfortunately still having the issue.
The action being used is as follows:

Normally it pulls the file path directly from PowerApps, but the filenames have the same issue regardless.
I've confirmed directly on the fileshare that the file exists.
The connection uses the N:\ drive as the root folder, if that helps.

Was this reply helpful? Yes No
Amanthaper 441 on at

Like (0)

Report

Hi @Avery_Kirkham,
I've found mapped drive letters to be funky to use. Try using the UNC path instead of the mapped drive letter in your connection. Right-click above the mapped drive\folder and you should see the UNC path.
------------------------------------------------------------------------------------------------------
If my post helps you with your problem or answers your question, please mark it Solved or Answered. This helps anyone with similar challenges. If you like my response, please give it a Thumbs Up.
------------------------------------------------------------------------------------------------------

Was this reply helpful? Yes No
yashkamdar 1,044 on at

Like (0)

Report

Hello Team,

@Amanthaper has an interesting idea. Please do give that a try and if that also doesnt help then as a last resort you will need to raise a ticket with the Support team.

You can do that from here - https://us.flow.microsoft.com/en-us/support/

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!

Was this reply helpful? Yes No