Network-aware programs must deal with the case where the remote side has not responded to a message after a certain amount of time. Timeout is the term used to describe how much time a program will wait before giving up. While MOVEit Transfer allows some of its timeouts to be configured, others are fixed values. This document details some of the most commonly encountered MOVEit Transfer timeouts.

Web Interface and HTTPS Machine Interface

The MOVEit Transfer web interface and its HTTPS machine interface (used by MOVEit Automation, MOVEit Transfer API, MOVEit EZ, MOVEit Xfer, and so on.) both use the same session timeout.

The value of this timeout can be changed by a Microsoft .NET configuration file called Web.config, which is located in the webroot of the MOVEit Transfer website (for example, C:\MOVEitDMZ\wwwroot). Using Notepad or any other text editor, set the timeout attribute of the sessionState node in this file to set the timeout. This timeout is expressed in minutes. The default value is 20 minutes.

<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />

You will not need to restart the server or any services after making a change to this value. The new value will apply to any new sessions.

MOVEit Transfer file transfer operations will automatically change the session timeout or individual sessions to a longer value during transfers to allow slow transfers to complete. The session timeout is reset to the shorter value (by default, 20 minutes) when a transfer is complete. The length of the long timeout can be configured the MaxSessionTimeoutMinutes registry key. Consult the System Reference for more information.

FTP Interface

One FTP timeout exposed to administrators is a value which allows them to control how long to wait for additional FTP commands from a still-connected-but-inactive FTP control connection before disconnecting. This timeout is expressed in seconds. Unless you create an alternate value in the Window Server registry, MOVEit Transfer will use the default value for this setting.

HKEY_LOCAL_MACHINE\SOFTWARE\Standard Networks\siLock\siLockFTPServer\IdleTimeout

Type: REG_DWORD

Default: 600 (seconds)

You will not need to restart the server or any services after making a change to this value. The new value will apply to any new sessions.

SSH Interface

The SSH timeout determines connection close for connected-but-inactive SSH sessions. This timeout is expressed in seconds.

Default: 600 (seconds).

HKEY_LOCAL_MACHINE\SOFTWARE\Standard Networks\siLock\SSHServer\IdleTimeoutSecs

You will not need to restart the server or any services after making a change to this value. The new value will apply to any new sessions.

Email Client

The timeout used by the client that sends all of the MOVEit Transfer notifications is available in the MOVEit Transfer Config utility. By default, the email timeout is 30 seconds.

If you encounter ANY sort of timeout issues on a regular basis, we recommended you enable the local SMTP server and use it as queue and buffer against transient mail delivery problems.

RADIUS and LDAP Clients

These timeouts are configurable by administrators from the Web Interface. See the related RADIUS and LDAP sections for complete information.

Custom Report Timeouts

You can now limit resources utilized by long running, inelegant, and inefficient SQL leveraged for custom reports. The CustomReportRunCommandTimeout registry value takes a value in minutes that limits processing for a custom report query. MOVEit Transfer halts the query when it reaches this time threshold, reports a warning, and puts the query (as configured) in a 'stand-by' or non-runnable state. (It can be re-run after the report configuration is reviewed).

HKEY_LOCAL_MACHINE\SOFTWARE\Standard
                Networks\siLock\CustomReportRunCommandTimeout

Registry Value Defined for CustomReportRunCommandTimeout (one-minute timeout threshold shown)