E9.2 FTP Receive error: "Unable to receive file: <filename> Error: Error normalizing new path!"

[DaveWagoner]

Hi folks, another head scratcher. Here's the long and short of it. Any ideas?

1) List ftp directory contents, generate a dataset
2) Loop over the dataset, pull file from ftp and deposit into temp directory. The file has name in pattern "word1_word2_word3.dta.2024_08_27_11_10_00"
3) The process creates an empty file of the name I specify in said temp directory, but then errors out with the error "Unable to receive file: <filename> Error: Error normalizing new path!"

Here's the component that is erroring:

This shows my attempts in my temp dir, all failed whether I changed the destination file name or not:

 

[DaveWagoner]

I have had zero luck searching on this specific error. It's not in common java library documentation nor does it seem to exist on oracle support (unless I missed something).

 

[Kevin Long]

Hi @DaveWagoner,

I ran your error through ChatGPT (I couldn't resist) and received the following advice:

The error message “Error normalizing new path” in an FTP client typically suggests that there is an issue with the file path or directory structure. This error can occur due to a few reasons:

1. Invalid Characters: The file path or file name might contain invalid or unsupported characters that the FTP client can’t process.
2. Directory Structure: The target directory path might not exist, or there might be issues with permissions, causing the FTP client to fail when trying to normalize (i.e., interpret) the path.
3. Path Length: If the file path is too long, the client might struggle to handle it correctly.
4. Symbolic Links: If there are symbolic links (symlinks) involved, the FTP client might have trouble resolving them.
5. Permissions: There could be permission issues on the server side, preventing the FTP client from accessing the specified path.

Troubleshooting Steps:

1. Check the File Name and Path:
• Ensure there are no invalid characters or spaces in the file name or path.
• Simplify the path, if possible, to see if it resolves the issue.
2. Verify Directory Structure:
• Check if the directory exists on the server and that the path is correct.
• Make sure you have the appropriate permissions to access the directory.
3. Try a Different Path:
• Test with a shorter path or a different directory to see if the problem persists.
4. Check FTP Client Settings:
• Some FTP clients allow you to adjust settings related to path normalization. Check if there’s an option to disable strict path checking or similar features.
5. Server Logs:
• If you have access, check the server logs for any related error messages that might provide more details.

With all that out of the way, how are you retrieving your file names from the ftp server? Any chance that you might have a cr and/or lf character on the file name? If you manually key the name in, does it work? Can you use a test a smaller file name on the ftp server and see if that works?

Kevin

 

[DaveWagoner]

That's fantastic, it did not occur to me to run the msg across chatGPT

We do not have control over the remote FTP, nor do we have option to change source information or filename structure

I'm getting dir contents through another ftp connector:


It gets me a very tidy array that I'm iterating over


If I try anything other than the value in "name", I get a simple "file not found" error from the server. So I know I'm querying the server for a file that exists at the correct dir.

 

[Kevin Long]

Hmm, your ftp connector looks a little different from my ftp connector. I wonder if the paint hasn't quite dried yet on that one. Maybe bounce this off Oracle Support.

 

[MFreitag]

Can we replace JDEList with ChatGPT already?

That's fantastic, it did not occur to me to run the msg across chatGPT

Only a matter of time until somebody will register a ChatGPT Bot on these forums...

PS: What's your session at this year's INFOCUS about again?