How to check TightVNC Server for Live Streaming and Remote Control issues?

How can the TighVNC Server settings be examined on a robot machine to troubleshoot issues related to Live Streaming and the Remote Control Orchestrator feature?

Issue Description:
Users encountering problems with the Live Streaming and Remote Control feature may experience various issues, such as crashes, abnormal data streaming, and difficulties controlling a remote server. If facing these or any other problems, collecting the TighVNC Server logs is crucial to the issue resolution.


How to generate logs in the TighVNC Server?

  1. Display the "hidden icons" in the Windows OS Task Bar and click the TightVNC Server icon to open the application
1
  1. Navigate to the Administration Section
    1. Within the TightVNC Server interface, locate the "Administration" section.
    2. Configure Logging Settings:
      1. Find the "Logging" section
      2. Customize the log verbosity and the destination log path. By default, the log verbosity is set to 0 (logs disabled), and the path is mapped to C:\Users\YourRobotUser\AppData\Roaming\TightVNC
      3. Set the log verbosity to 6 or 7; this level contains relevant information about the connection. If requested by the UiPath Support team, increase the verbosity to 10.
2.jpg
  1. Check and send the generated log file to the UiPath Support team. This log file helps identify issues related to the TightVNC server connection.


Additional Information:
When installing TightVNC Server, the Prerequisites for Windows Robots UiPath documentation says "Make sure that the Register TightVNC Server as a system service option (under TightVNC Service configuration) is not selected".
Note that in UiPath implementation, the VNC server is not installed as a Windows service because each user spins up their own type of VNC instance, contrary to the typical server installation.
​​​​​​​