EFT Hangs When Running Script that Contains Configuration Changes

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT v6.0 and later

DISCUSSION

If you are running a Custom Command consisting of a script that makes configuration changes to EFT (meaning it instantiates EFT’s SFTPCOMInterface.dll), AND if you select the Stop Processing check box under the Action, you run the chance of creating a deadlock that will result in a hung EFT, until the command times out (assuming a timeout was configured for the command).

Globalscape recommends that you use one of the following workarounds:

• Do not select the Stop Processing check box, which allows the Command to run asynchronously, and greatly reduces or even eliminates the chance of deadlock.

-OR-

• Run the Command from a Timer or Folder Monitor rule, rather than as a trigger related to other configuration or internal changes in EFT (such as account created, IP banned, etc.).