VMware Horizon Community
RotoVegas
Contributor
Contributor
Jump to solution

Error: No Machines In The Desktop Pool Are Responsive

We're running a floating pool on VMware View 4.6 and we had an issue with users not being able to login this morning.

The error in View Administrator was:

Unable to launch from pool <pool> for user <user>: No machines in the destop pool are responsive.

We could find nothing wrong with the virtual machines themselves. We could ping and connect to them. We restarted the VIEW servers and then the View Administrator server as well but we still had the issue.

We then noticed five virtual machines catagorised as problem desktops in the desktop inventory screen in View Administrator. The reason given for each was the error "already used".

We decided to delete these problem desktops and as soon as we did provisioning started and new virtual machines were created. All users can now login and everything seems fine again.

Has anyone had this issue before and more importantly how can we prevent it from happening again?

Thank you for your help.

RotoVegas.

0 Kudos
1 Solution

Accepted Solutions
mittim12
Immortal
Immortal
Jump to solution

Have you seen this KB before, http://kb.vmware.com/kb/1000590?  I believe there is an issue when your using power on and off policie to start VM's where a VM with the already used status is counted as a power on machine.   The problem is no one can utilize this machine when it has an already used flag so people start getting errors when trying to connect. 

View solution in original post

0 Kudos
2 Replies
VMmatty
Virtuoso
Virtuoso
Jump to solution

Moved this thread to the View forum where you should get better visibility for your issue.

Matt

http://www.thelowercasew.com

Matt | http://www.thelowercasew.com | @mattliebowitz
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

Have you seen this KB before, http://kb.vmware.com/kb/1000590?  I believe there is an issue when your using power on and off policie to start VM's where a VM with the already used status is counted as a power on machine.   The problem is no one can utilize this machine when it has an already used flag so people start getting errors when trying to connect. 

0 Kudos