Troubleshooting "Cannot Determine Frame Size or a Corrupted Frame Was Received" Error

News Knowledge Base
1

After upgrading the Robot, the user encountered the error message "Cannot determine the frame size or a corrupted frame was received" when attempting to sign in from UiPath Assistant and UiPath Studio. However, access to Orchestrator was successful on the same machine. What could be the potential causes and solutions for this error?

Issue Description

Users may encounter a specific SSL (Secure Sockets Layer) connection error in UiPath, indicated by the error message "Cannot determine the frame size or a corrupted frame was received." It generally arises due to issues with network security certificates or firewall settings.

Cause

The cause of this error is usually one of the following:

  • Network connection issues
  • Incorrect system date and time
  • Firewall preventing the program from communicating
  • Outdated software or drivers
  • Using VPN or proxy

Resolution Steps

Follow these steps to resolve the encountered issue:

1. Check your Network and Internet connection:

  • Ensure that your Internet connection is working fine.
  • Test the connectivity by browsing UiPath Orchestrator site on the Robot machine.

3. Verify your firewall settings:

  • Make sure your firewall (for example: Zscaler) is not preventing the UiPath program from accessing the Internet.
  • You may need to add UiPath as an exception on your firewall settings.

5. Disable VPN or proxy (if any):

  • Some network issues might arise because of VPN or proxy servers.
  • Try disabling your VPN or proxy and then check to see if the problem persists.

6. Adjust TLS version:

  • Some network issues might arise because of VPN or proxy servers.
    • Open Registry Editor (type regedit in search).
    • Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
    • Add a new key named TLS 1.2 or TLS 1.3
    • Inside these keys, create Server and Client keys.
    • Inside Server and Client, create a DWORD (32-bit) named Enabled with value 1
  • Try disabling your VPN or proxy, and then check to see if the problem persists.
    • Follow the same steps as above, but set the Enabled DWORD value to 0 under TLS 1.0 and TLS 1.1 keys.
    • Finally, restart your system for changes to take effect.

7. Check Environment Variables for any unwanted proxy configurations:

  • Navigate to the Environment Variables setting on your machine as shown below.

kb-0EMPa00000FreDC.jpg1762×756 286 KB

  • Look for and eliminate the outdated proxy variables such as https_proxy, http_proxy, and no_proxy.
  • Restart your machine to ensure changes are well-incorporated.