CRRDG1119E Debug Secure Daemon failed to start because port port_number is
invalid or is in use.
The Debug Secure Daemon runs in
the background and listens for incoming debug connections. If another
instance of the product is already running on this machine then the
port is likely already in use. You can change the port in the workbench
preferences.
Explanation
The Debug Daemon was unable to start on the secured
port specified in the preferences because the port was invalid or
the port was in use by another instance of the product.
System action
The Debug Secure Daemon does not start, and incoming
sessions are not allowed.
User response
Ensure that the port is valid and no other applications
are listening on the specified port. Alternately, select a different
port for the daemon. Check the workspace log for any related messages.