WUYING Terminal:Error codes for cloud computer connections

Root cause

The cloud computer experienced a kernel dump (Core Dump) event, which caused the connection to fail or be unexpectedly terminated.

Solution

Restart the cloud computer. Once the restart is complete, try connecting again.

Root cause

A network anomaly occurred on the cloud computer, interrupting the connection between the cloud environment and the management console.

Solution

Restart the cloud computer. Once the restart is complete, try connecting again.

Root cause

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

Solution

1. Try to reconnect to the cloud computer.

2. If that fails, restart the cloud computer and try connecting again after the restart is complete.

Root cause

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

Solution

1. Try to reconnect to the cloud computer.

2. If the previous step fails, restart the cloud computer and try connecting again after it has finished restarting.

3. If the restart also fails to resolve the issue, contact your IT administrator to expand the system disk. For detailed instructions, see Increase the disk capacity.

Root cause

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

Solution

1. Try to reconnect to the cloud computer.

2. If that fails, restart the cloud computer and try connecting again after the restart is complete.

Root cause

The control system or cloud computer initiated operations such as shutdown, restart, or logoff. As a result, the cloud computer connection was terminated.

Solution

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

2. The administrator can send any remote command to the cloud computer from the Elastic Desktop Service (EDS) Enterprise console and observe the results. For more information, see Send remote commands.

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

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

Root cause

A service request timed out. As a result, the cloud computer connection was terminated.

Solution

1. Perform one of the following operations based on your business requirements:

   • If there is no data that needs to be saved in the cloud computer, restart the cloud computer and then reconnect to the cloud computer.

   • If there is data that needs to be saved in the cloud computer, wait for a moment and then reconnect to the cloud computer.

2. Check whether your on-premises network can connect to the ports required by the cloud computer. For more information about the ports, see Port requirements. If your on-premises network cannot connect to the ports required by the cloud computer, contact your enterprise administrator to open the ports.

Root cause

An exception occurred on the on-premises network. As a result, the cloud computer connection was terminated.

Solution

1. Wait for a moment and then reconnect to the cloud computer.

2. Check whether your on-premises network can connect to the ports required by the cloud computer. For more information about the ports, see Port requirements. If your on-premises network cannot connect to the ports required by the cloud computer, contact your enterprise administrator to open the ports.

Root cause

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

Solution

Make sure that the on-premises device is connected to the on-premises network and then reconnect to the cloud computer.

Root cause

A process exception occurred on a core Alibaba Cloud Workspace client. As a result, the cloud computer connection was terminated.

Solution

1. Perform one of the following operations based on your business requirements:

   • If there is no data that needs to be saved in the cloud computer, restart the cloud computer and then reconnect to the cloud computer.

   • If there is data that needs to be saved in the cloud computer, wait for a moment and then reconnect to the cloud computer.

2. For a Windows cloud computer, reconnect to the cloud computer after the administrator sends the following PowerShell command to the cloud computer from the console. For more information, see Send remote commands.

   taskkill /im spmonitor.exe -f

3. Check whether your on-premises network can connect to the ports required by the cloud computer. For more information about the ports, see Port requirements. If your on-premises network cannot connect to the ports required by the cloud computer, contact your enterprise administrator to open the ports.

Root cause

The CPU usage or memory usage of the cloud computer was high. As a result, the cloud computer connection was terminated.

Solution

1. If there is no data that needs to be saved in the cloud computer, restart the cloud computer and then reconnect to the cloud computer.

2. For a Windows cloud computer, the administrator can send the following PowerShell commands to the cloud computer from the console to query processes with high resource usage. For more information, see Send remote commands.

   • Query the top 20 processes with the highest CPU usage

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

   • Query the top 20 processes with the highest memory usage

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

3. The administrator can continue to send the following command to the cloud computer from the console to terminate the related processes. Replace <ProcessName.exe> with the actual process name that you queried.

   taskkill /im <ProcessName.exe> -f

4. Reconnect to the cloud computer.

Root cause

The CPU usage or memory usage of the on-premises device running the Alibaba Cloud Workspace client was high. As a result, the cloud computer connection was terminated.

Solution

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

2. Update the client to the latest version and then reconnect to the cloud computer. For more information, see Update the client.

3. If the issue persists, restart the on-premises device running the client, and then log on to the client again and reconnect to the cloud computer.

Root cause

An exception occurred when the client connected to the streaming gateway. As a result, the cloud computer connection failed or was terminated.

Solution

Check whether your on-premises network can connect to the ports required by the cloud computer. For more information about the ports, see Port requirements. If your on-premises network cannot connect to the ports required by the cloud computer, contact your enterprise administrator to open the ports.

Root cause

The streaming gateway failed to detect the asp-server. As a result, the cloud computer connection failed or was terminated.

Solution

Check whether a firewall or VPN software is enabled in the cloud computer. If enabled, disable it and then reconnect to the cloud computer.

Root cause

The 5912 listener port was not enabled in the cloud computer. As a result, the streaming gateway failed to detect the asp-server and the cloud computer connection failed or was terminated.

Solution

Restart the cloud computer and reconnect to the cloud computer.

Root cause

An HTTP proxy was configured on the client. As a result, the cloud computer connection failed or was terminated.

Solution

Disable the HTTP proxy on the client and then reconnect to the cloud computer.

Root cause

An exception occurred on the streaming protocol in the cloud computer. As a result, the cloud computer connection failed or was terminated.

Solution

Restart the cloud computer and reconnect to the cloud computer.

Root cause

An exception occurred during the running of the client. As a result, the cloud computer connection failed or was terminated.

Solution

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

2. Update the client to the latest version and then reconnect to the cloud computer. For more information, see Update the client.