Wait until it is running or reboot from administration console.ĭesktop is not ready for connection (currently in maintenance mode). If problem persists, please contact your Administrator. The DaaS Agent should come up when the desktop comes up (within a few minutes).ĭesktop is not ready for connection (may be shutting down or rebooting). Reboot the desktop if the problem persists and console access is too long. If problem persists, please contact your Administrator.ĭaaS Agent is reported as offline. There might be a warning or error in the desktone.log file related to ViewClientServlet.ĭata Horizon Client or Agent returned XML which could not be read by the DaaS platform.ĭesktop is not ready for connection (DaaS Agent may be starting up). Unable to parse error from Authentication Error Response due to interrupted communication between the Horizon Client, Tenant and View Agent Connect. Error Details: Desktop Agent Communication Error Once the refresh completes, users will be able to log into their desktop.Įrror communicating with desktop. This means that desktops are being destroyed and recreated based on a new or altered Gold Pattern. Unable to allocate a desktop - pool refresh is in progress. The timeout is based on a policy () set at the service provider, but may be overridden by a setting in the administration console. Session has Expired, Please Restart Horizon Client to Connect The View Agent failed the login request sent. The Error Details portion of the message provides information needed by customer support to troubleshoot the connection problem. The following table lists the most common error messages users can receive and the causes when using the using the Horizon Client to connect to their desktop. The exception to look for will mention the ViewClientServlet. If a user receives Error 500 in the Horizon Client, look in the tenant log and make a note of the exception before contacting support. This sections describes error messages that users can encounter during desktop connections.
0 kommentar(er)
