Limagito File Mover Software Blog and Filemover News

06 Jul
Python within Limagito File Mover running as a windows service
Python within Limagito File Mover running as a windows service
In version v2025.7.6.0 we added a ‘Global Python’ setup option.
One of the reasons we did this is by default we’ll use the latest registered Python version. The issue is that when you are using the File Mover as a Windows service and the ‘Logon As’ user of the File Mover service is not able to read the registry settings of the latest registered Python version then we’ll be not able to initialise the Global Python engine. To prevent this issue, it is a good ideae to register it for all users when installing the Python Distribution. Another option is to adjust the Global Python setup and use “Select Specific Version’ as Distribution Type.
Default Distribution Type: Latest Registered Version
Destination Python Setup, click F9 to execute Script
Error message: Global Engine not available
So the File Mover Service was not able to find the Python Distribution using the registry information
To solve this we added the following Distribution Type:
Distribution Type: “Select Specific version”
Set Python DLL Name
Set Python Version
Set Python DLL Path (in the screenshot we used the 64bit version of Python)
Destination Python Setup, click <F9> to execute Script
Info message: Global Engine available, RegVersion: 3.13 – DLLName: python313.dll
So the File Mover Service was able to find the Python Distribution correctly
The Remote tool has an option to read the “Engine Log'” of the File Mover service. This will give you some information about the status of the Global Python Engine.
If you need any help with this ‘python windows service’ error, please let us know.
Best Regards,
Limagito Team
#python #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Python python
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
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.
Be sure to read the following blog article about using our new Python option with Limagito File Mover installed as a Windows Service: link
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