- #Please wait verifying login information software
- #Please wait verifying login information password
- #Please wait verifying login information Offline
If problem persists, please contact your Administrator. This error occurs if the DaaS platform cannot parse the XML, the session-id key returned in the XML is null, or if the key is malformed. The Allocator Service is indicating the current session is using a non-compatible protocol. Please log off previous session and try again. Unable to Connect to Desktop (current connected protocol incompatible). All desktops in pool are currently in use.ĭynamic pool has no desktops that are available to the user. Unable to Allocate Desktop, No Desktops Available.
#Please wait verifying login information password
User name or password are invalid for the given domain. Login Failure: Unknown user name or bad password. The DaaS platform cannot associate the tenant with any Domain. There is no Domain information logged in the database. Error Details: Unable to retrieve Tenant Domain information The IP address is listed only if it is known. The IP address can be null if the DaaS Agent is in the middle of logging in or the VM is starting up.
#Please wait verifying login information Offline
Possible reasons include: Domain controller is offline the Fabric node had failures general tenant problems.
#Please wait verifying login information software
Error Details: Unable to lookup user GUID using credentialsĪn exception was raised by the Horizon DaaS software during a GUID lookup. A session exists with a GUID different from the current user. Error Details: Desktop Already in Allocated State.Īnother user has been allocated this desktop. Desktop has been allocated to a different user. Try checking the state of the machine and the tenant system to see if there are other issues. This is a generic message from the Allocator Service. If problem persists, please contact your Administratorĭesktop Unavailable. See troubleshooting/solution on VMware tools. Error Details: VMware Tools is not installed Error Details: VMware Tools is not running Reboot machine or check service "View Agent Connect" through RDP (User Portal) if possible. Make sure that the View Agent is installed and that the firewall ports are open (4172, 32111, 443). The DaaS Agent has reported that the View Agent service is not running or listening on the require ports. This can also occur during dynamic pool refresh. If problem persists, please contact your Administrator.ĭomain rejoin maintenance is occurring for a dynamic desktop. Wait until it is running or reboot from administration console.ĭesktop is not ready for connection (currently in maintenance mode). 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.