Below are some of the common reasons for the Manager failing to start:
The Manager Java process is already running. This can be checked by opening Windows Task Manager and looking for a java.exe with Memory foot print of hundreds of MB. Alternatively, install sysinternals' Process Explorer from HTTP://TECHNET.MICROSOFT.COM/EN-US/SYSINTERNALS/BB896653 to locate the java process. If found, as indicated in the following image, it should be removed.
Check if Manager Java process is already running.png "GUID-6A42C5FF-4868-4142-8F85-5846579A542B-low.png")
In the command prompt, navigate to
%programfiles%\Trellix\IPS Manager\App\binand runtms.batmanually. Then check for below conditions.One of the TCP ports that Manager binds to is in use. Use
netstat -nabto list out all ports in use. These netstat options also identify the executable that is binding to the port and the executable should be stopped.Check netstats.png "GUID-B98B5F93-0A33-40EB-9355-6631F96E48CF-low.png")
Check whether the logged user on the server has permissions to launch Trellix IPS Manager service. This can be found by right clicking on the service, selecting Properties and then Log On tab. So, if the logged user doesn't have permission to run local service, the Manager does not start.
Check user permissions.png "GUID-1FD98BBE-533A-4554-B64E-03D04CC13101-low.png")
The server does not have enough RAM. The
tms.batfile has a -Xmx<MaxHeap> setting in MB specifying Java heap in MB that needs to be allocated to the process. If the server does not have that much RAM, then process will not start.Sometimes, especially on 32-bit machines, when there are instances of heap exhaustion, you may try to increase the maximum heap setting to a larger volume assuming to be having full 2000MB available. However stack space and native libraries share memory in the same 2000MB space and java heap cannot be higher than 1170MB. So, ensure that -Xmx setting is not greater than 1170MB if it is a 32 bit machine.
The process fails to start with a classloader exception such as ClassNotFound. This typically indicates issues with the Manager installation. A fresh installation or upgrade as appropriate should resolve the issue.