The TcpSubServer DLQ log file includes measurements of how long calls take and it is a very useful file for troubleshooting purposes. 

Activating DLQ Logging

When a server is initialized for the first time, we typically recommend that you turn on DLQ logging. Here are the steps to do this:

  • Stop the main server and slave server(s), if applicable. (see Stopping and Starting a SystemWeaver Server)
  • In the server directory, open the swServer.ini.
  • Add a line for DLQ logging (DLQ=True):
  • If you wish to have the files stored in a different location than the server executables, add a line for DLQDirectory and enter the path to that location.
  • Save your changes.
  • Restart the server(s).


When DLQ logging is turned on, a DLQ file will generate in the location of the TcpSubServer executable unless otherwise configured. Each time the server is stopped and restarted, a new DLQ file is created and will be named something like this example:


Maintaining DLQ Log Files

The dlq files can become quite large especially if the server is not restarted in a very long time. If the size becomes an issue, you can move or delete a DLQ file. However, if the file is the one currently being written to by the server, you must first stop the server before moving or deleting it. When you restart the server, a new file will generate. If there are multiple DLQ files saved, you can always delete older file versions at any time.  

Sending a Copy to Systemite Support

This file is useful for troubleshooting purposes and decoding the information contained in it will require that you contact Systemite. If Systemite requests this file for troubleshooting purposes, make a copy of the dlq file that covers the time period in question, compress it, and upload the copy to SystemiteNAS. For a brief explanation of the file's content, see Explanation of Server Log Files.

Turning off DLQ Logging

To turn off DLQ logging, open the swServer.ini in a text editor and change the setting to DLQ=False. The new setting will not apply until the server is restarted. See Stopping and Starting a SystemWeaver Server.