Error Archives - File transfer tool from Limagito

04 Jul
SFTP error FXP_OPENDIR when connecting
SFTP error FXP_OPENDIR when connecting
Q: Hey guys, we’re receiving this error with our SFTP connection to the MOVEIT Cloud. Have you heard anything on this? Also, we did update to the latest version (v2025.6.8.0) to see if it works better.
OpenDir(2797ms):
SshVersion: SSH-2.0-MOVEit Transfer SFTP
    SftpVersion: 3
    IdleTimeoutMs: 60000
    openDir(2797ms):
      path: /Home/
      Sent FXP_OPENDIR
      readSftpPacket(2797ms):
        maxToReceive: 16
        Connection closed by peer.
        passiveClose:
          Passive socket closing complete.
        –passiveClose
        sshRawPacket: Socket connection closed.
        sshReadMessage: Socket connection closed.
        Socket connection lost, channel closed.
      –readSftpPacket
      Failed to read expected SFTP packet.
      Failed to receive response to FXP_OPENDIR, disconnecting…
    –openDir
    Failed.
–OpenDir

Limagito: We don’t have any other open tickets regarding this issue so it is a bit strange. What we did in the meantime: we added an extra (third) SFTP code Vendor – SC. We are still doing tests but it is already available in our latest v2025 version.
Reply: I found the root cause of the error. MoveIT only allows a login to have one session open at a time. We were trying to run the jobs concurrently and that what was causing the issue. Once I made them run sequentially, the issue stopped.

If you need any help with this ‘SFTP error FXP_OPENDIR’ error, please let us know.
Best Regards,
Limagito Team
#sftp #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Error SFTP
01 Jun
The system cannot find the path specified
Q: The system cannot find the path specified question. Filemover is doing a great job for us with SharePoint, I just have a few questions. I notice that the log is showing errors and it seems to be related to files/folders that fall outside the date range we want.
I understand why it is not coping them, but I don’t understand why it is throwing errors.
Example:
5/14/2025 12:12:59 PM Search Files Error at Path E:\ALG-SHARE\Public\General_FACILITIES\Corporate Documents\XXXXXXX XX XXXXXX XXXX, XXX XXX XXXXXX XXXX XXXXXXXXXX XXXXXXXX XXXXXXXXX XXXX\FYI 12-31-17\Other\XXXXXX XXXX – Closing Documents XXXXXX\XXXXXX XXXX – Purchase Documents – Closing XXXXXX\Closing Documents – XX XXXX – XXXXXXX XXXXXXXXXX\: The system cannot find the path specified
The path is actually there and filemover sees it, it just writes that error to the log and skips over the path. Please let us know if you need to do a zoom call. Thank you as always.
A: Could you please prefix your current Source path with \\?\
So instead of E:\YourCurrentPath >> \\?\E:\YourCurrentPath
Some other examples:
Local Drive folder
C:\PathThatIsVeryLong\ => \\?\C:\PathThatIsVeryLong\
Network Drive Folder:
\\ServerName\PathThatIsVeryLong\ => \\?\UNC\ServerName\PathThatIsVeryLong\
For a share folder (\\ServerName\PathThatIsVeryLong\), we could use \\?\UNC\ServerName\PathThatIsVeryLong\ where “ServerName” is the name of the computer and “PathThatIsVeryLong” is the name of the shared folder.
Please have a look at: filenames-longer-256-characters
If you need any help with this option, please let us know.
Best Regards,
Limagito Team
#managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Error cannot, specified
20 Oct
Problem copying a file due to a folder tree that is too long
Problem copying a file due to a folder tree that is too long
Q: I’m contacting you because we’re experiencing a problem when retrieving and copying a file stored on AWS (bucket) via LimagitoX v2023.5.12.0 (screenshot attached). The problem seems to be linked to the length of the folder tree containing the file. In fact, when we test with a shorter tree path, the file is copied successfully. Unfortunately, according to AWS, it is not possible to modify the path length of the tree structure.
To give you more information on the problem, I’ve attached two log files:
Log_OK_SrvLimagitoX.Ruleld : short tree path with which the copy works.
Log_KO_SrvLimagitoX.Ruleld: tree path imposed by AWS that generates the error (which doesn’t work).
A: We found some renaming errors in the log file.
2024-04-26 15:26:18 AMS_BI_AMAZON_TEST_S3_VGO [AWSS3GET] Rename Exception Error: Rename C:\Users\Admin_Limagito\AppData\Local\Temp\LimagitoX\LimagitoX.740\aps-download-publisher-11111111-5ce6-49d8-8037-111111111\versionId=c36c10e4-d59c-4f20-82f4-111111111111\executionDate=20240426\part-00000-111111111111111111111111111111111111.c000.csv.tmpdwnld To C:\Users\Admin_Limagito\AppData\Local\Temp\LimagitoX\LimagitoX.740\aps-download-publisher-11111111-5ce6-49d8-8037-111111111111\versionId=c36c10e4-d59c-4f20-82f4-111111111111\executionDate=20240426\part-00000-111111111111111111111111111111111111.c000.csv Error
When downloading files from AWSS3, we first store the stream of data we are downloading locally on the system. The same counts for all non-Windows folders as source, like AZURE, SFTP, FTP, … . During the download, the file has a temporary extension (.tmpdwnld). After a successful download, the file will be renamed to its original extension. The problem here is that Windows doesn’t like very long path + filenames, please check: link.
Solution: Please update to the latest build first (v2024.10.17.0 or higher)
Could you please open the Advanced option of this AWSS3 Rule:
Please add \\%\ as prefix to your ‘Temporary Directory’ setup. Please, always keep the temporary folder on the local system where the file mover is installed!
If you need any help with this “folder tree that is too long” question, please let us know.
Best Regards,
Limagito Team
#managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Error max path, max_path, maxpath, too long

1 2 3 4 … 10 →

Contact Us Now

Error

SFTP error FXP_OPENDIR when connecting

The system cannot find the path specified

Problem copying a file due to a folder tree that is too long

SEARCH

CATEGORIES

ARCHIVES

TAGS

DISCOVER OUR SITE