Build Engine not starting correctly and requests abandoned

I am using the RTC build system toolkit to create ant scripts that interact with RTC. To make that run, I am using build engines running in a VM so they work as an agent in the VM and I can trigger the ant scripts from RTC client (using a build definition pointing to that build engine).

The problem that I have is that I am not able o correctly start the build engine in some VMs. I have two VMs were the build engine runs fine, with no problem and other two were the Build Engine doesn't start correctly. When I run the command to start the build engine from windows prompt, it freezes and nothing happens(instead of the common message saying that it is running and accepting requests). On RTC client I see the build engine status as idle giving me the impression that it is running. But when I try to run a build definition on that build engine, it starts to run and is immediately abandoned indicating that there is a problem in the Build Engine. I am suspecting that there is a network problem between the VM and the RTC server because our servers and network are configured with high restrictive permissions (any necessary access must be explicitly requested). But I can access for example the RTC Web Client using a web browser. The two VMs that are working fine are old ones and in the past I needed to make some privileged network permissions for the IP of those vms, I just don t know what are exactly the necessary permissions needed. Maybe the RTC build system toolkit (jbe) access RTC through some specific port or protocol that is currently blocked on our network. I am not sure if this is the problem but I couldn t find what is the difference between the working VMs and the failing ones. Also there is no log from the build engine the indicates clearly what is the problem (at least I don't if jbe generates some kind of log ).

This is the command that I run to start the build engine
jbe -repository https:/myrtcserver.com:9443/jazz -userId myuser -passwordFile mypassfile -engineId MyEngineId


And this is the error that I receive when I start a build definition in that build engine and is is immediately abandoned.

This build has been automatically abandoned by the build engine 'MyBuildEngine'.
This can happen if the build engine stops while it is processing a build, or if it fails to communicate with the server (e.g. due to the server crashing, or a network break).
As a result, the build is left in the in-progress state.

Such builds are automatically abandoned for the following reasons:
1. When the build engine is restarted, new builds will be processed, however the old builds would otherwise remain in the in-progress state indefinitely.
2. As a result the build engine would appear as busy when it is not.


Anyone have any idea ? I appreciate any help, this is blocking a big continuous integration project and we may skip using RTC if I don't solve this problem.