VMware Horizon Community
exabay1
Contributor
Contributor

VDM Error the desktop has failed to open.

This desktop is currently not available.

In the admin console it show it in a "ready" state.

Direct Connect to virtual desktop: No

Desktop ID Display Name VirtualCenter Server Type Entitled Enabled Virtual Machines Active Sessions

ExabayVDI ExabayVDI ExabayVDI 10.1.100.101 (dave) Individual 1 0

Its part of the same domain as VDM, the external is set to the correct address.

I get the follow error in the event log: POOL_EMPTY:Pool:cn

But the client is there and it works fine from the ESX server.

Reply
0 Kudos
32 Replies
brekus
Enthusiast
Enthusiast

Try rebooting the VM or re-installing the agent. Also make sure that the VDM connection server and VM can use name resolution to contact eachother.

Reply
0 Kudos
mittim12
Immortal
Immortal

You may also want to verify there is no type of firewall blocking the client. We had a case where Symantec was blocking us from logging in using the VDM client and we received the error message about the desktop failing to open.

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

Reply
0 Kudos
exabay1
Contributor
Contributor

Nope that didn't do it. I did find a problem in DNS, fixed it. But it didn't solve the issue.

Reply
0 Kudos
exabay1
Contributor
Contributor

My firewall is off, and I turned of McAfee. Still no luck.

Reply
0 Kudos
mittim12
Immortal
Immortal

Are you able to bring up a RDP connection and connect to the VM?

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

Reply
0 Kudos
exabay1
Contributor
Contributor

Yes I can access them with RDP, no problem. I've verified the remote control options on the desktop and also in Active Directory.

Reply
0 Kudos
exabay1
Contributor
Contributor

Also, if I pause the desktop and then open a session with the VDM client. And then select the button to connect. I can see the desktop go from "pause" to "power on", but after it is powered all the way on, the vdm client will come back and say the desktop failed to open.

Reply
0 Kudos
mittim12
Immortal
Immortal

Is there anything of significance in the VDM log files of both the connecting machine and VM? Log files can be found at the following location

C:\users\All Users\VMware\VDM\logs

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

Reply
0 Kudos
exabay1
Contributor
Contributor

Here is what I get if I'm logged on to VDM and all the desktops are powered on: (pool isn't empty)* *

13:45:59,262 INFO POOL_EMPTY:Pool:cn=exd,ou=server groups,dc=vdi,dc=vmware,dc=int;USER:EXABAY\dave;USERSID:S-1-5-21-3172209103-183625690-48788887-1111;

I cleared out the log, then logged in and tried opening a session. Here is the log entry I got: (Settings, all clients in the pool where paused)

13:30:07,838 INFO BROKER_LOGON:USER:EXABAY\dave;USERSID:S-1-5-21-3172209103-183625690-48788887-1111;

13:30:07,838 INFO Creating new PortalContext

13:30:07,838 INFO Initialising new PortalContext

13:30:07,869 INFO Type = CapAbsent

13:30:07,884 INFO Type = CapAbsent

13:30:19,932 INFO Tunnel (re)connection for capID = AA717DB343B7D01EE5B4283FF29DF522

13:30:19,947 INFO New tunnel for session starting: AA717DB343B7D01EE5B4283FF29DF522

13:30:19,978 INFO (AA717DB343B7D01EE5B4283FF29DF522) Client capabilities: C-BASE

13:30:19,978 INFO (AA717DB343B7D01EE5B4283FF29DF522) Starting session for capID AA717DB343B7D01EE5B4283FF29DF522

13:30:19,978 INFO (AA717DB343B7D01EE5B4283FF29DF522) Portal authenticated session started (local authentication): userDN=cn=s-1-5-21-3172209103-183625690-48788887-1111,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int

13:30:19,978 INFO (AA717DB343B7D01EE5B4283FF29DF522) Session authentication completed: userID = dave

13:30:19,978 INFO (AA717DB343B7D01EE5B4283FF29DF522) Session will time out after: 36000s, at Wed Mar 19 23:30:19 CDT 2008

13:30:49,995 INFO Pool cn=3097b073-5e45-43df-81ed-126558dfa322,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Starting VM /Exabay/vm/ExabayVD1/ExabayXPDesktop/EXD3

13:30:50,370 INFO VM requires powering on/resuming, will start

13:31:02,714 INFO Pool cn=3097b073-5e45-43df-81ed-126558dfa322,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Started VM /Exabay/vm/ExabayVD1/ExabayXPDesktop/EXD3 successfully

13:36:00,016 INFO getSessionForApplication - user CN=S-1-5-21-3172209103-183625690-48788887-1111,CN=ForeignSecurityPrincipals,DC=vdi,DC=vmware,DC=int has 0 sessions to analyze.

13:36:00,032 ERROR No servers responded

13:36:00,032 INFO SERVERS_NOT_RESPONDING:Pool:CN=EXD,OU=Applications,DC=vdi,DC=vmware,DC=int;USER:EXABAY\dave;USERDN:CN=S-1-5-21-3172209103-183625690-48788887-1111,CN=ForeignSecurityPrincipals,DC=vdi,DC=vmware,DC=int;

Reply
0 Kudos
exabay1
Contributor
Contributor

Screen shot attached of VDM inventory

Reply
0 Kudos
mittim12
Immortal
Immortal

Ok so your Desktop is called EXD... Did you assign a virtual machine to this desktop? Is it showing up under the virtual machine tab? You have entittled the desktop to the user you are trying to connect as? There are no active sessions to that desktop listed when you are trying to connect?

Reply
0 Kudos
exabay1
Contributor
Contributor

Did you assign a virtual machine to this desktop? yes

Is it showing up under the virtual machine tab? yes

You have entittled the desktop to the user you are trying to connect as? yes

There are no active sessions to that desktop listed when you are trying to connect? correct. no sessions running.

Reply
0 Kudos
exabay1
Contributor
Contributor

I've also setup another VDM with its own "individual" desktop. Same issue.

Reply
0 Kudos
jerel
Contributor
Contributor

I had this same problem, what I did was remove the entitlement for the user I'm trying to login as and then readd them. This has seemed to fix the problem with me. I hope it fixes your issue as well. Good luck!

Jerel

Reply
0 Kudos
exabay1
Contributor
Contributor

Nope that didn't fix it either. I even tried a different user.

Reply
0 Kudos
mofabio
Contributor
Contributor

I have the same problem :smileyshocked:

Reply
0 Kudos
mittim12
Immortal
Immortal

The only way I have been able to create this POOL_EMPTY message is to login to the VM, stop the VDM service, and then try to connect through the VDM client. In my opinion this points to some type of VDM agent problem on the VM.

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

Reply
0 Kudos
AlexStern
Contributor
Contributor

Hello,

I am having exactly the same issue. Everything was done as per user manual but still getting mesage "VDM Error the desktop has failed to open"

If you found some way to fix it please let me know

Thank you

Alex

Reply
0 Kudos
exabay1
Contributor
Contributor

still stuck on this problem.

Reply
0 Kudos