Limagito File Mover Software Blog and Filemover News

04 Jul
SFTP error FXP_OPENDIR when connecting
SFTP error FXP_OPENDIR when connecting
Q: Hey guys, we’re still 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
29 Jun
How to use Python within Limagito File Mover
How to use Python within Limagito File Mover
In version v2025.6.29.0 we added a Python as Destination option. This is the first build so we know it still needs fine-tuning. Please tell us what you think and if you find any issues please let us know. Also, Python feature requests are welcome.
32-bit versions of Limagito File Mover will only work with 32-versions of Python
64-bit versions of Limagito File Mover will only work with 64-bit versions of Python.
Our File Mover will use the default registered version of Python
We did our testing with Python v3.13
You can download a Python distribution from here: link
We’ve added quite some Rule related Var, they always tart with ps (PythonScript):
Readable within Python (case sensitive):
String Var
psFileName
psFilePath
psFileDir
psFileSubDir
psFileSubDirFirst
psFileSubDirLast
psFilePath
psFileSubPath
psFileSubPathFirst
psFileSubPathLast
psSourcePath
psFileChecksum
psDestinationID
psRuleTempPath
psExitCode
psVSA
psVSB
psVSC
psVSD
psVSE
psRFD
psRFN
psRFW
psRFP
psQDC
psQSC
psQST
psFSO
psSTR
psDTR
psFCA
psFCB
psFCC
psFCD
psFCE
psLRT
psLCI
Integer
psDeleteAfterCopy
psDirectionID
psRuleID
Int64
psFileSize
psCounter
psTotalFiles
psTotalFilesSrcError
psTotalFilesDstError
psTotalControlSrcError
psTotalControlDstError
psCurrentFiles
psCurrentFilesSrcError
psCurrentFilesDstError
psCurrentControlSrcError
psCurrentControlDstError
psVIA
psVIB
psVIC
psVID
psVIE
DateTime as Float
psFileDateTime
psFileADateTime
psFileCDateTime
psFileMDateTime
Writeable within Python (case sensitive):
String
psVSA
psVSB
psVSC
psVSD
psVSE
psRFP
psRFN
psFCA
psFCB
psFCC
psFCD
psFCE
Integer
psExitCode
Int64
psVIA
psVIB
psVIC
psVID
psVIE
psTotalFiles
psTotalFilesSrcError
psTotalFilesDstError
psTotalControlSrcError
psTotalControlDstError
psCurrentFiles
psCurrentFilesSrcError
psCurrentFilesDstError
psCurrentControlSrcError
psCurrentControlDstError

In the following example we added two Python Destinations to a Rule:
First Python as Destination show some information about the two Var we will be using: psFileName and psFilePath
Second Python as Destination will use a file we found in the source to copy it to a Destination
RunTime Log Result:
If you need any help with this new ‘Python within Limagito’ option, please let us know.
Best Regards,
Limagito Team
#python #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Python python
08 Jun
New subdirectory parameter option added to limagito file mover
New subdirectory parameter option added
We recently added a new directory parameter option :?=?: > :BeginIndex=EndIndex:
It will split any var which contains a backslash and can be used for example with our %SFS Var = Source File Subfolder(s).
For example if %SFS would contain “Bak\BakSub\UNIT_1_4.1.2025”. The result of the split would be:
Index 1: Bak
Index 2: BakSub
Index 3: UNIT_1_4.1.2025
When you set the BeginIndex to 0 (zero) then we’ll start at the highest Index. Some examples:
%SFS:0=1:
0 > start at the highest index
1 > use the last subfolder part only
Result would be: UNIT_1_4.1.2025
%SFS:2=3:
2 > start at index 2
3 > End at index 3
Result would be: BakSub\UNIT_1_4.1.2025
Many combinations are possible. Please check the following blog article where we used this new parameter option.
– File renaming setup when you have multiple levels of subfolders and you only need the parent subfolder name:
%SFS:0=1:
0 > start at the end of the subfolders(s) Var %SFS > %SFS = Source File Subfolder(s)
1 > use the last subfolder part only
RegEx: (.*)\.(.*)
Replacement: %SFS:0=1:.\2
If you need any help with this ‘subdirectory parameter option’ option, please let us know.
Best Regards,
Limagito Team
#managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Parameters Rename %SFS:?=?:, subdirectory

1 2 3 4 … 154 →

Contact Us Now

File Mover Blog

SFTP error FXP_OPENDIR when connecting

How to use Python within Limagito File Mover

New subdirectory parameter option added to limagito file mover

SEARCH

CATEGORIES

ARCHIVES

TAGS

DISCOVER OUR SITE