To begin, please see the links below for our debug logging instructions. Following these steps will help to gather the information needed for MOVEit Technical Support to investigate the issue: 
How do I enable and capture All Debug logs in MOVEit Transfer(DMZ)?
How do I enable and capture system-wide All Debug logs in MOVEit Automation(Central)?
How to gather task specific All Debug logs for MOVEit Automation

If investigating a crash related to MOVEit Automation, please also see these crash-specific instructions in these articles as well: 
Information needed to diagnose MOVEit Automation application crashes

This article specifically has instructions to collect Crash Dumps.

For a SQL report of tasks that ran at the time of the crash, see: Determining what caused MOVEit Automation(Central) to crash? 

There is also an article devoted to Best Practices for Contacting MOVEit Support, which will help to identify additional debugging logs that are available, and help to prepare when submitting a new tech support case. 

It is also often requested to look at the Windows Event Viewer on the MOVEit Automation or MOVEit Transfer server. The Event Viewer can be opened from the start menu by typing Event Viewer into the search bar. In the Event Viewer, expand the Windows Logs folder and review logs under Application and System. Note any errors around the time that the issue occurred in the MOVEit application. These logging pieces may provide more information about the Windows Services MOVEit relies on which can specify a resolution to the issue. 

 

Many organizations ask if there is a way to examine debug logs for systems from several days prior to calling in, and if there is a way these log files are saved off somewhere. In general, all logging files for MOVEit Automation or Transfer retain five logs worth of data from the system processing. So if the logging level is set to All Debug in either application, and the maximum log file size is set to 100MB, that means the log will write at that verbose level until the most recent log reaches that maximum size. When it reaches that size, it will start a new log file with the extension ".log." The old log file will overwrite the existing log file with extension ".OL1" which will overwrite the next oldest log file with extension ".OL2," and so on for ".OL3" and ".OL4." The maximum number of logs is five sets of logs for each log type, and there is not an option to change this. 

Typically, the standard debug logging tools are oriented to help with troubleshooting when processes fail or when there is an error. The debug logs are intended to display the account of the process the task went through so we can identify where it went wrong. When submitting a case, provide a screenshot of the location of the error for reference, and also please type out the error description and code number. Having these error details will be helpful so the tech support engineer can search for documented resolutions to the issue. If not actively troubleshooting an error or issue, other features are better suited to provide an account of what occurred in the system.

MOVEit Transfer 
The Logs file on the Transfer server contains many sets of logs which each serve a purpose. In most cases, the DMZ_Web, SftpServer (legacy SSH logs stored in DMZ_SSH), and DMZ_FTP logs will be most helpful for the technical team to troubleshoot issues. The DMZ_Web log will contain much of the information present in the legacy SSH and the FTP logs as well (especially regarding user authentication). The remaining log files in the Logs folder relate to the specific automated tasks that occur behind the scenes to maintain Transfer (e.g. GarbageCollection or EmailNotify), which are triggered from the task scheduler. 

Here is a summary of what the different log levels include:

• Nothing: no logs are written to disk
• Catastrophic Errors: only sever errors are written to the log file
• Consistency Errors: logs error affecting the consistency of application data
• User Errors: logs user errors that are encountered in the application
• Success: includes some successful events
• Some Debug: logs a variety of useful debug messages and database queries
• All Debug: logs all debugging messages and a breakdown of database queries

 If the Transfer Checker utility is run and returns an error, the technical services team will likely investigate a debug log that results from this general system check log if the utility fails at a certain point. The log file will be named MIDMZCheck.log and it is usually located in a folder path similar to:
C:\Program Files\MOVEit\MOVEitTransfer\

In normal operation, the logging level should be kept at (Web) User Errors and (FTP, SSH) Connect Messages.
The Flush after every write should be disabled. When debugging a problem, the debug level should be elevated, and All Debug is generally recommended. 

The folder path location where the Logs file can be found is located in the Config Utility > Paths > Logs field. The location for this path can use a remote share to store the Logs, and when using the remote share this will sign on with the credentials indicated in the "Advanced" button.  Administrators can move the files to the remote location or back local to the server by updating this path. For more information, please see this documentation:

System Internals - Remote Filesystem - https://docs.progress.com/bundle/moveit-transfer-web-admin-help-2025/page/System-Internals-Remote-Filesystem.html

MOVEit Cloud 
MOVEit Cloud provides the benefit that we are able to examine the logs for organizations internally with some additional filtering features. When contacting MOVEit Tech Support with an issue related to Cloud, please provide some specific information about the issue or failure to assist with filtering logs based on the error or user impacted. In most cases, the following details would be the most helpful:  1) Username or email, 2) IP Address or Hostname, 3) Filename, 4) Folder name, and 5) Error description.

MOVEit Automation 
In Automation, the task specific logs in the task details while working in the Web Admin show logs for the past 5 task runs by default. On the server, these are located in a path similar to this typically:
C:\ProgramData\Ipswitch\Automation\Logs\<task_id>\log_x.txt.

Each time the task runs, the new run replaces the oldest run displayed in the task details and the file in this location. Each of these logs are specific to the individual runs of the tasks and are not oriented for more than one run, because we try to keep them as a highly contained account of what the task encountered when we are troubleshooting task failures.

For administrators interested in how to log more than one task run in the same logs, this is possible with the "Save to Disk" option in the Automation Admin Console (retired as of version 16.1 (2024.1)) when a filter is set for the task. The Save To Disk option will write a file adding updates once it is set initially, and it will continue to write until the Save to Disk is turned off or the filter is cleared. This option allows administrators to name the log file and designate a location where it will save through the folder browser. The caveat to this is that it is reactive, so it will not contain logs for past data or runs that occurred before the setting was turned on.

For system level debug logging, those logs are stored in the MOVEitC.* log files in the install directory (ex: \Program Files\MOVEit\MOVEit Automation\). Here is a summary of what the different log levels include:

• Internal Errors: internal system errors
• Task/File Errors: errors relating to task runs and file transfers
• Task/File Warnings: warnings relating to task runs and file transfers
• Task Completions: information on task statuses and whether they are succeeding/failing/completing with no transfers
• File Completions: information on individual files that are getting transferred and their statuses
• Some Debug: system configuration updates, basic task run activity (how many files were found, how it was triggered and when)
• More Debug: dmz notifier status, actively scanned hosts, more detailed task run history (database queries, what filenames specifically matched the file mask)
• All Debug: tasks being considered by the scheduler and why they are running (or why not), most detailed task activity (breakdown of database queries, detailed cache directory activity)

If looking for data reporting outside of the debugging features, consider Automation's Reporting features (REPORTS - https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/REPORTS.html). To save off a hard file of certain accounts of the task runs, the SQL server can be queried directly. The Documentation about the Database Schema will assist with designing Custom Reports that call data from the SQL database (Schema - https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/Schema.html). Custom Reports can help with identifying more about Automation's configuration outside of the Task run events that mark different processes in the system. 

Legacy Failover 
There are two types of information related to Failover that may need to be examined, which are data from the replication of the primary node to the secondary node and data regarding a failover event. Replication of data is logged to the system-wide debug logs on your MOVEit Automation server that is acting as the secondary node. For more information on these log files, see the second link at the top of this page. Data from failover events are recorded to their own log file called micfail.log which is located in your Automation install directory (ex: \Program Files\MOVEit\MOVEit Automation\).