cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
New Member

File Name Spaces Causing 404 Error

I'm getting a 404 error for several of my FTP to Azure connections.

I found that the error only occurs if the FTP file name has a space (i.e. 'Folder 1' will error out but 'Folder1' will not),
When I select the FTP file in Flow, it appears as 'Folder%201' to account for the space, which I believe is what's causing the issue.
Tried manually inputting the folder name, but this does not work either.
Any thoughts?

3 REPLIES 3
Highlighted
Community Support
Community Support

Hi @j_t0418,

 

Microsoft Flow would add the %20 to replace the space in the file name is because space is not allowed to use under OData operations.

And I think this should not have any effect if the name is operated within the flow.

Would you please share more information about the Azure Action here?

 

For the 404 error, could you please share a screenshot of the error message under the flow running details?

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted

Thank you for the quick response back.

I am using the 'FTP Server to AzureBlob' template. The Azure target is Azure Blob-Create file, which copies the FTP file into an exisitng Azure Blob folder.

 

Here is a link to a screenshot of the failure summary:

 https://photos.app.goo.gl/tgvcQtCJPoxkxqy72

 

Here are the full Outputs i'm receiving:

Headers:
{ "Pragma": "no-cache", "x-ms-request-id": "3bd532b8-c5a8-4b31-b831-8c1ff498a9ab", "Timing-Allow-Origin": "*", "Cache-Control": "no-cache", "Date": "Thu, 27 Jul 2017 13:01:30 GMT", "Set-Cookie": "ARRAffinity=4b6db488261a8c12d3d5c0f847a79a8b4734c8890fc42488d77e2c7dc37c5f37;Path=/;HttpOnly;Domain=ftpconnectionprovider-westus.tip0-westus.p.azurewebsites.net", "Server": "Microsoft-IIS/8.0,Microsoft-HTTPAPI/2.0", "X-AspNet-Version": "4.0.30319", "X-Powered-By": "ASP.NET", "Content-Length": "283", "Content-Type": "application/json; charset=utf-8", "Expires": "-1" }

Body:
{ "status": 404, "message": "The requested action could not be completed as the specified resource (file/folder) does not exist or is busy.\r\nclientRequestId: 3bd532b8-c5a8-4b31-b831-8c1ff498a9ab", "source": "ftpconnectionprovider-westus.tip0-westus.p.azurewebsites.net" }
Highlighted

Hi @j_t0418

 

Just wondering if you ever solved this, I am currently getting the same error (on ocassion). The logic app creates the blob and then I have it create a file via FTP as the last step.  This seems to fail every 3rd or 4th file.

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Solution Authors
Users online (10,507)