TQ Server in MS-Windows

In a single machine installation, TQ Server is automatically started by TQ Client or TQ Admin and no special installation process occurs for TQ Server itself.

In multi-machine installations, (usually) just one machine has TQ Server installed. In the MS-Windows environment TQ Server is installed as a service so that it starts automatically at boot time and cannot accidentally be stopped while the machine is running. The install program will both install the service and start it before the installation completes, so the Administrator does not need to explicitly start the service. The service is set to "Automatic" so that it will start automatically if the PC is rebooted.

The administrator can start and stop the service at any time (through the Services application in the Administrative Tools section of Control Panel), but while the service is stopped, none of the client machines will be able to run TQ Client or TQ Admin.

TQ Server uses information from the TQ.Properties file to determine how it should run, and also some registry entries created during the installation process.

TQServer in Windows 98 and Windows ME
On these two variants of Windows, the service mechanism is not quite the same as in more recent versions of Windows. However, the installer will set up the registry to run a program called TQDaemon98.exe when the PC boots. This application will launch TQ Server and shut it down when the PC is shutdown.

If you need to stop TQ Server without rebooting the PC, type in

    TQDaemon98.exe stop

at a DOS prompt while in the install folder. TQ Server can be started again by running TQDaemon98.exe (without any command line argument) again.

How TQServer reports events and problems
TQServer will interact with the desktop to indicate problems, but only at start up in the case that it detects a severe error. In addition, it uses two mechanisms to provide information. The first is MS-Windows specific and is created in the MS-WIndows specific part of the TQ Server code. Messages created by this part of the code appear in the application log accessed by the MS-Windows Event Viewer. If the service appears to fail, this should be the first place to go to find out about errors.

The second mechanism used to indicate problems is from the machine independent part of the code. Messages created in this part of the code appear in a log file (TQServer.log) which will be in the 'data' sub-folder assigned to the data folder specified during the installation process. The log file is not normally operational, but is enabled through an entry in the tq.properties file. The entry in the file is normally "debug.logging=false". The entry should be changed to "debug.logging=true" to cause the file to be created. After any issues have been resolved, change the entry back to "debug.logging=false" as the logging operational simply keeps adding to the log file and it will just keep growing in size.