Error codes for cloud computer connections

Root cause

A kernel dump (Core Dump) on the cloud computer caused the connection to fail or disconnect unexpectedly.

Solution

Restart the cloud computer and reconnect.

Root cause

A network anomaly on the cloud computer interrupted the connection between the cloud environment and the management console.

Solution

Restart the cloud computer and reconnect.

Root cause

The cloud computer's CPU utilization is too high, causing a connection timeout.

Solution

1. Reconnect to the cloud computer.

2. If reconnection fails, restart the cloud computer and reconnect after the restart completes.

Root cause

The system disk usage on the cloud computer is too high, causing a connection timeout.

Solution

1. Reconnect to the cloud computer.

2. If reconnection fails, restart the cloud computer and reconnect after the restart completes.

3. If restarting does not help, contact your IT administrator to expand the system disk. Increase the disk capacity.

Root cause

The memory usage on the cloud computer is too high, causing a connection timeout.

Solution

1. Reconnect to the cloud computer.

2. If reconnection fails, restart the cloud computer and reconnect after the restart completes.

Root cause

The control system or cloud computer initiated a shutdown, restart, or logoff, terminating the connection.

Solution

1. If the cloud computer is in the stopped state, start it and reconnect.

2. The administrator can send any remote command from the Elastic Desktop Service (EDS) Enterprise console to the cloud computer and check the results. Send remote commands.

   • If results are returned, reconnect to the cloud computer.

   • If no results are returned, restart the cloud computer and reconnect.

Root cause

A service request timed out, terminating the connection.

Solution

1. Choose one of the following actions:

   • If you have no unsaved data on the cloud computer, restart the cloud computer and reconnect.

   • If you have unsaved data, wait a moment and then reconnect.

2. Verify that your on-premises network can reach the required ports (Port requirements). If not, contact your enterprise administrator to open them.

Root cause

An on-premises network exception terminated the connection.

Solution

1. Wait briefly, then reconnect.

2. Verify that your on-premises network can reach the required ports (Port requirements). If not, contact your enterprise administrator to open them.

Root cause

The on-premises device disconnected from the on-premises network during hibernation hours. The cloud computer connection was terminated.

Solution

Ensure the on-premises device has network connectivity, then reconnect.

Root cause

A process exception occurred on a core WUYING Terminal client component, terminating the connection.

Solution

1. Choose one of the following actions:

   • If you have no unsaved data on the cloud computer, restart the cloud computer and reconnect.

   • If you have unsaved data, wait a moment and then reconnect.

2. For a Windows cloud computer, have the administrator send the following PowerShell command from the console, then reconnect (Send remote commands).

   taskkill /im spmonitor.exe -f

3. Verify that your on-premises network can reach the required ports (Port requirements). If not, contact your enterprise administrator to open them.

Root cause

High CPU or memory usage on the cloud computer terminated the connection.

Solution

1. If you have no unsaved data on the cloud computer, restart it and reconnect.

2. For a Windows cloud computer, have the administrator send the following PowerShell commands from the console to identify high-resource processes (Send remote commands).

   • Query the top 20 processes by CPU usage:

     Get-Process | Sort-Object CPU -Descending | Select-Object -First 20 | Format-Table Name, CPU -AutoSize

   • Query the top 20 processes by memory usage:

     Get-Process | Sort-Object WorkingSet -Descending | Select-Object -First 20 | Format-Table Id, Name, WorkingSet -AutoSize

3. Send the following command to terminate the offending process. Replace <ProcessName.exe> with the actual process name from the query results.

   taskkill /im <ProcessName.exe> -f

4. Reconnect to the cloud computer.

Root cause

High CPU or memory usage on the local device running WUYING Terminal terminated the connection.

Solution

1. Restart the client and reconnect to the cloud computer.

2. Update WUYING Terminal to the latest version (Update the client) and reconnect.

3. If the issue persists, restart the on-premises device, then log on and reconnect.

Root cause

An exception occurred when the client connected to the streaming gateway. The cloud computer connection failed or was terminated.

Solution

Verify that your on-premises network can reach the required ports (Port requirements). If not, contact your enterprise administrator to open them.

Root cause

The streaming gateway could not detect the asp-server.

Solution

Check whether a firewall or VPN software is enabled on the cloud computer. If either is enabled, disable it and reconnect.

Root cause

Port 5912 listener was not enabled on the cloud computer, preventing the streaming gateway from detecting the asp-server.

Solution

Restart the cloud computer and reconnect.

Root cause

An HTTP proxy was configured on the client. The cloud computer connection failed or was terminated.

Solution

Disable the HTTP proxy on the client and reconnect.

Root cause

A streaming protocol exception occurred on the cloud computer.

Solution

Restart the cloud computer and reconnect.

Root cause

A client runtime exception terminated the connection.

Solution

1. Restart the client and reconnect to the cloud computer.

2. Update WUYING Terminal to the latest version (Update the client) and reconnect.