The scenario is this: You have a local system and a remote system. Both use Windows. You set up for remote debugging following the same process as before: on the test side in Visual Studio the Enterprise servers (regions) on the remote system are brought up in the display. The expected regions are seen and are set for dynamic debugging. The project on your local system is then associated to one of those regions. A debugging session is initiated, but it never starts. You may see a box that says “Connection Pending, Waiting for debug connection". The box never goes away. On the remote server side at least something tried to happen as an animproxy entry is created and seen in Enterprise Server. However the connection is not fully established.

What more is needed now to set up remote debugging under SEE 6.0 SP2 WS2 HF5?

On the local system you need to set the environment variable CCITCP2 with the IP Address (not the hostname) of the remote Server Enterprise system. This can be done system-wide or be set in a region definition. That environment variable needs to be set so that the devenv (Visual Studio) process picks it up.

Setting this environment variable globally can be done using Start -> Control Panel -> System -> Advanced System settings. To set it from a command prompt, set CCITCP2={IP Address}; next start devenv from the same command prompt.

On the remote machine also ensure that port 86 is open for both UDP and TCP inbound traffic. The programs cobremotedaemon, cobdebugengineproxy (and cobdebugengineprozy64 for 64-bit) which are found in the product install’s base/bin directory need to be allowed access through the firewall. Ensure that those processes are running as well.

Support Incident 2652962