Instant Clone Error (missing)

[Super6VCA]

Starting to have more and more of this error.  Started with 1 pool now is happening to more of them.  Sometimes i can just try to RECOVER the desktop and that works and sometimes NO.  Sometimes i can REMOVE the desktop and let it rebuild but sometimes NO.  Then i need to use VIEWADMIN to clean up the ADAM DB and that is getting old.  Is there an underlying issue that is causing this adn is there anything i can do about it??  This is what the admin console says about the current ones

feb 19, 2018 1:40:36 PM CST: Pool cn=876614a1-f21e-4a46-a951-865d935a0500,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Unable to stop VM /Omaha/vm/ViewMWN/CLINIC-ROAMING/MWNROAM-6 - Client received SOAP Fault from server: The object has already been deleted or has not been completely created Please see the server log to find more detail regarding exact cause of the failure.

Any help or suggestions are appreciated.  Thanks

[sjesse]

Outside of the patch has anyone seen a workaround to prevent this. I have small desktop pools, 15-20 max desktops, and I had a large percentage of them go missing this morning.

[jo_strasser]

Hi,

sorry, there is no permanent workaround available for this issue.

The only workaround to get your environment up and running normally again is to shutdown all your connection servers and power it on at the same time.

This forces a resync of the internal LDS database and your environment will work normally again.

The root cause of this issue is a stucking communication between vCenter and the Horizon Connection Servers.

The best way to get stable is requesting the H-patch via VMware Support and installing it (open a PR via Support).

Cheers, JO

[sjesse]

Thanks, I'm aware of that and have done that before for this issue, I was just hoping a shorter workaround was discovered. Thank you for all the updates I've been following this too see what you guys found

[jonathanjabez]

Followed this KB to fix the issue in our case:

https://kb.vmware.com/s/article/2147129

[gustavocpw]

hi all, I'm having the same problem on my envoriment. vCenter 6.4 + Horizon 7.4.

Recompose operations stuck on missing VM, and new pools stuck on "VM Folder missing". After servers reboot, everything is fine.

To get the hot path, the only way is openning a case with support?

tks!

[anpucci]

Hi gustavocpw, I would suggest you to wait few mor days for the GA release of Horizon 7.5, this because the "patched version" is not production tested. Also with a single update you get new features as well.

Try to keep-on with Connection Server reboot.

If you want to open an SR with VMware, our hotfix version is VMware-viewconnectionserver-x86_64-7.4.0-8215536

Regards

[gustavocpw]

Updating my case here...

Horizon 7.5 was released few days ago. After update my servers, the problem was solved, no more reboots needed to clean "missing vms"!

tks everyone

[giuuscaa]

Hi there

Just for information. We got the same problem on our system. I solved the issue by deleting the ADSI entry on all connection server.

Just follow those steps:

Deleting the virtual machine from vCenter Server

Note: If you run the SviConfig RemoveSviClone command to remove linked clone data, the virtual machine is removed from vCenter Server. You can skip this task.

To delete the virtual machine from vCenter Server:

1. Log in to vCenter Server using the vSphere Client.
2. Right-click the linked clone virtual machine and click Delete from Disk.

Removing the virtual machine from the ADAM database

These steps are only applicable if the virtual machine has not been deleted from vCenter Server:Find the virtual machine's GUID stored in ADAM:

1. Log in to the culprit virtual machine using the vSphere Client Console or directly using Windows Remote Desktop Protocol (RDP).
2. Open the Windows registry, and go to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Node Manager\Server DN.
3. Record the cn=<GUID>.

If the virtual machine has already been deleted from vCenter Server:

1. Log in to the machine hosting your VMware View Connection Server through the VMware Infrastructure Client or Microsoft RDP.
2. Open the ADAM Active Directory Service Interfaces Editor.
   
   
   • In a Windows 2003 Server, click Start > Programs > ADAM > ADAM ADSI Edit.
   • In a Windows 2008 Server, c lick Start > All Programs >Administrator Tools > ADSI Edit.
     
     
3. Right-click ADAM ADSI Edit and click Connect to.
4. Ensure that the Select or type a domain or server option is selected and the destination points to localhost.
5. Select Distinguished Name (DN) or naming context and type dc=vdi, dc=vmware, dc=int.
6. Locate the GUID of the virtual machine.
   
   To locate the GUID of the virtual machine:
   
   
   1. Right-click the Connection DC=vdi,dc=vmware,dc=int [localhost] , and click New > Query.
   2. Under Root of Search, click Browse.. and select the Servers organizational unit.
   3. Click OK.
   4. In the Query String, paste this search string:
      
      (&(objectClass=pae-VM)(pae-displayname=<Virtual Machine name>))
      
      Where <Virtual Machine name> is the name of the virtual machine for which you are trying to locate the GUID. You may use * or ? as wildcards to match multiple desktops.
      
      
   5. Click OK to create the query.
   6. Click the query in the left pane. The virtual machines that match the search are be displayed in the right pane.
      
      
7. Record the GUID in cn=<GUID>.
8. T ake a complete backup of ADAM and Composer database. For more information, see Performing an end-to-end backup and restore for View Manager 3.x/4.x (1008046).

Delete the pae-VM object from the ADAM database:

1. Open the ADAM Active Directory Service Interfaces Editor.
   • In a Windows 2003 Server, click Start > Programs > ADAM > ADAM ADSI Edit.
   • In a Windows 2008 Server, c lick Start > All Programs > Administrator Tools > ADSI Edit.
     
     
2. Right-click ADAM ADSI Edit and click Connect to.
3. Choose Distinguished name (DN) or naming context and type dc=vdi, dc=vmware, dc=int.
4. Locate the OU=SERVERS container.
5. Locate the corresponding virtual machine's GUID (from above) in the list which can be sorted in ascending or descending order, choose Properties and check the pae-DisplayName Attribute to verify the corresponding linked clone virtual machine object.
6. Delete the pae-VM object.

BR Giulio